<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<br><div><div>On 13 Mar 2009, at 16:19, David Singer wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><p style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" style="font: 12.0px Helvetica">Can we drop this topic?<span class="Apple-converted-space"> </span>Apart from suggesting</font></p> <p style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" style="font: 12.0px Helvetica">a) that the fully delimited date format be required (extended format);</font></p> <p style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" style="font: 12.0px Helvetica">b) that year 0000 and before be allowed;</font></p> <p style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" style="font: 12.0px Helvetica">c) that parsing the body text as 8601 may be dangerous if it's notated the same way but not (possibly proleptic) Gregorian;</font></p> <p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; min-height: 14.0px"><br></p> </blockquote></div>I agree, with the addition of time periods denoted by two datetimes seperated by a / eg. 1914/1918. This would bring HTML5 in line with existing authorship practices in use in TEI. Authors will be able to encode any historical date be it Julian, Roman, Mayan, Chinese etc by continuing to do what they're already accustomed to doing - publishing the machine readable date as a proleptic Gregorian date.<div><br></div><div>The proposed schemes for alternative calendars seem like a red herring to me, since noone in practice encodes machine readable versions of alternative calendars when digitising a text.</div><div><br></div><div>Regards</div><div>Jim</div><div><br><div> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; "><span class="Apple-style-span" style="border-collapse: separate; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; -webkit-text-decorations-in-effect: none; text-indent: 0px; -webkit-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><div>Jim O'Donnell</div><div><a href="mailto:jim@eatyourgreens.org.uk">jim@eatyourgreens.org.uk</a></div><div><a href="http://eatyourgreens.org.uk">http://eatyourgreens.org.uk</a></div><div><a href="http://flickr.com/photos/eatyourgreens">http://flickr.com/photos/eatyourgreens</a></div><div><a href="http://twitter.com/pekingspring">http://twitter.com/pekingspring</a></div><div><br class="khtml-block-placeholder"></div><br class="Apple-interchange-newline"></span></span><br class="Apple-interchange-newline"> </div><br></div></body></html>