time-prov: Drop subproperty axiom that leads to datatype conflict #1429
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The file time-prov.ttl provides a non-normative alignment between OWL-Time and PROV-O. One of the included suggestions is an alignment of the `time:inXSDDateTimeStamp` with the currently-deprecated property `time:inXSDDateTime`. This patch drops that suggested alignment, for two reasons: 1. Entailment, in both RDFS and OWL semantics, would cause any usage of `time:inXSDDateTimeStamp` to induce usage of `time:inXSDDateTime` in the graph, which could raise OWL warnings about usage of a deprecated property. 2. A triple `X time:inXSDDateTimeStamp Y` would be required by the range of `time:inXSDDateTimeStamp` to have Y bear the datatype `xsd:dateTimeStamp`. Entailment, in both RDFS and OWL semantics, would induce a triple `X time:inXSDDateTime Y`, with the same subject and object as in the original triple. The literal `Y` would have an incompatible datatype with the range of the induced `time:inXSDDateTime` triple, because a second datatype could not be assigned to it per RDF design. This contribution is made only by myself, and is not being made by the National Institute of Standards and Technology or any other organization. References: * https://www.w3.org/TR/2022/CRD-owl-time-20221115/#time:inXSDDateTime Signed-off-by: Alex Nelson <[email protected]>
|
The XML Schema Datatypes rec specifies that Also see #1421 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The file time-prov.ttl provides a non-normative alignment between OWL-Time and PROV-O. One of the included suggestions is an alignment of the
time:inXSDDateTimeStampwith the currently-deprecated propertytime:inXSDDateTime.This patch drops that suggested alignment, for two reasons:
time:inXSDDateTimeStampto induce usage oftime:inXSDDateTimein the graph, which could raise OWL warnings about usage of a deprecated property.X time:inXSDDateTimeStamp Ywould be required by the range oftime:inXSDDateTimeStampto have Y bear the datatypexsd:dateTimeStamp. Entailment, in both RDFS and OWL semantics, would induce a tripleX time:inXSDDateTime Y, with the same subject and object as in the original triple. The literalYwould have an incompatible datatype with the range of the inducedtime:inXSDDateTimetriple, because a second datatype could not be assigned to it per RDF design.This contribution is made only by myself, and is not being made by the National Institute of Standards and Technology or any other organization.