> There has been some discussion of whether OWL can use XSD's new datatype > dateTime with required timezone, because our notion of equality derives > from the timeline for time, not the XSD 7-value internal data structure > for xsd:dateTime. However, our notion of equality *is* the notion of > equality used in XSD for dateTime values with a required timezone, and > thus retains compatibility with XSD. > > I propose that we resolve ISSUE-138 by staying with owl:dateTime in the > next round of publication but to put in a note saying that this datatype > is to be considered xsd:dateTime with a required timezone and that we > will move to the new XSD name for this datatype as soon as it is > determined. Isn't the next publication expected to be Last Call? Do you have any indication how long it will talk to have this determination? -- SandroReceived on Monday, 13 October 2008 17:30:43 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 13 October 2008 17:30:44 GMT