-
Notifications
You must be signed in to change notification settings - Fork 8
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
Normalize literals? #15
Comments
@gkellogg - Thanks for pointing this out. Even taking XSD as an example, not all systems provide complete coverage for XSD and so don't normalize for all datatypes. And some systems don't faithfully preserve all datatypes (xsd:positiveInteger vs xsd:integer). And if we choose some datatypes and not others, (e.g. XSD integers but not XSD duration), the impact on supporting systems may be significant because they don't support such choices. Implementing RDC would need changes lower down which is an impedance to adoption. The algorithm could be defined on RDF terms, and two graphs that differ by non-canonical syntactic form are different. A graph may have both
Two triples. Another case is trailing zeroes in decimals and doubles - sometimes used to informally indicate precision. Often it's not what most users expect (but not all users). Parameters to the algorithm will need to be propagated with the results (#11). |
I propose that we close this,, and remove the discussion from the spec. It is flawed, as @afs noted. |
I think there needs to be some statement along the lines of (but not necessarily exactly), "Literals are not normalized, for a number of reasons (possibly with a link to this issue, or a brief summary of some of those reasons). For purposes of RCH, literals with different syntactic representations but the same semantic representations are not merged, and two graphs differing only in the syntactic representation of one or more literals may produce different sets of blank node identifiers." |
... with a note explaining why literals are not normalized. Fixes #15.
... with a note explaining why literals are not normalized. Fixes #15.
The CG spec has the following issue:
While this may be possible for certainly well-known datatypes (e.g., XSD), datasets may use literals with datatypes
from vocabularies with no defined normalization, or even L2V operation.
The text was updated successfully, but these errors were encountered: