- From: Simon Cox via GitHub <sysbot+gh@w3.org>
- Date: Fri, 30 Jun 2023 02:00:00 +0000
- To: public-sdwig@w3.org
The main problem is caused by the fact that PROV uses `xsd:dateTime`, while in OWL-Time we preferred `xsd:dateTimeStamp` and thus deprecated `time:inXSDDateTime` in favour of `time:inXSDDateTimeStamp`. The motives for doing this are sound in principle - OWL-Time _should_ be modeling best practice, which is to make the timezone information mandatory. But the rest of the world (specifically PROV-O) has not necessarily caught up. Furthermore, while `time:inXSDDateTime` is formally marked `rdf:type owl:DeprecatedProperty` and `owl:deprecated true`, these are merely annotations. What real effect do they have on applications? The background problem - which we can't solve here - is that dependencies between standards and their revisions are not synchronised. The original OWL-Time was a W3C Note published in 2006. PROV-O came out in 2013. The Rec version of OWL-Time was released in 2017 (the Candidate Rec dated 2022 merely adds the IANA clause). The Rec preserved everything from the 2006 version in service of backward compatibility, but marked a few things 'deprecated' where we judged that best practice had moved on. (Frankly a clean re-design would have junked a whole lot of fluff, particularly around encoding of temporal position such as we are dealing with here, but we had to accommodate the fact that it was already a widely known 'ontology', and avoid making breaking changes.) So how does that play out? We thought that marking some resources 'deprecated' but not actually removing them was the right thing to do. So `time:inXSDDateTime` is formally marked `rdf:type owl:DeprecatedProperty` and `owl:deprecated true`. But these are merely annotations. So what effect do they have on applications? And in what environments? The process of developing and formalising 'standards' involves many compromises and quite a few judgment calls. You are proposing a minor change to a non-normative artefact, and frankly you may be the only person that has tried to actually use it 'in anger' ;-) But we must be aware of process and precedent here. -- GitHub Notification of comment by dr-shorthair Please view or discuss this issue at https://github.com/w3c/sdw/issues/1421#issuecomment-1614010059 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 30 June 2023 02:00:02 UTC