-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
should Concepts include information about REQUIRED datatypes #122
Comments
This seems to be covered by section 1.8? It refers to RDF Semantics for entailment regimes. Then in "RDF Semantics", RDF entailment is built on Simple entailment
and that's before datatypes RDF Semantics section "5 Simple Interpretations" change note:
(The "next section" seems to mean section 7, not 5.1 or 6) RDF Concepts needs to explain what a datatype is, and about lexical form and values, which it does. Requirements for entailment should be with the entailment content, which is in RDF Semantics. |
But then why is there a RECOMMENDED in Concepts at all? It appears that something should be done. |
Link to the text please. |
First paragraph of https://www.w3.org/TR/rdf12-concepts/#xsd-datatypes |
That is before "recognized datatype" is introduced. RECOMMENDED == SHOULD. It is giving good practice - use certain XSD datatypes, which are RDF-compatible, and not different vocabularies for numbers, dates etc for interoperability reasons. |
RDF-Semantics does not reference RDF-Concepts for "recognized datatypes". It has its own definition dfn-recognized. |
See also #60. |
Semantics states that support of several datatypes is REQUIRED for RDF entailment but Concepts does not have any analogue of this requirement. I think that Concepts should discuss what is needed for RDF entailment.
The text was updated successfully, but these errors were encountered: