-
Notifications
You must be signed in to change notification settings - Fork 0
Revise RDFterm-equal and function sameTerm. Rename RDFterm-equal to sameValue. #194
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
Conversation
It has editor's notes in the text, in a lurid colour, for further changes. These can be seen in the preview. The diff isn't very useful except to show the changes are only in one area of the document. |
a7ec54a
to
5555e41
Compare
There are still 4 "editors notes" for work to be done - one of them is waiting on w3c/rdf-concepts#154. |
Okay, I will work on a PR for w3c/rdf-concepts#154 right away (as PR w3c/rdf-concepts#158 is merged now). |
The PR for w3c/rdf-concepts#154 is ready; see: w3c/rdf-concepts#161 |
7d51235
to
156b28f
Compare
f4990ef
to
e305cf3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for pushing this and for answering all my nitpicks.
I am still not convinced that the special case for NaN is worth it while sameValue is kept as only a way to define =
but it's not a big deal (my bold assumption is that we will never expose sameValue directly).
Bold. 😄 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just some minor suggestions. Looks good to me in general!
Andy, sorry for having been quiet in this PR recently. I have an important deadline tomorrow and will be able to come back to this PR only later this week. |
If appropriate, we can proceed by raising subsequent issues so that merge can proceed. (for the merge, I will squash commits so we have a commit for the long term record) |
This looks good to me with one exception: the special handling for "NaN" in §17.4.2.2 sameValue. The content in §17.4.2.2 seems reasonable, and the rationale provided in the following NOTE section is good. However, I'm not sure how you'd ever get into Since this is value-specific, we can't simply add a new row to the operator mapping table, but I think something needs to be done to ensure handling of NaN values ends up using |
Handling There is lots of discussion up-thread so I'll try not repeat that all. Identity isn't equality for NaNs. https://www.w3.org/TR/xmlschema11-2/#equality "NaN"^^xsd:double is not a consistent point-extension of the number value space R -- it's not an algebraic group under In a graph matching, two uses of "NaN"^^double" are the same term. Everywhere else, [RDF Concept 5. Datatypes] https://www.w3.org/TR/rdf12-concepts/#section-Datatypes So there is choice here. We don't need If RDF ever becomes value-centric, including the pattern of reading data and canonicalizing numbers on input, |
Sorry. I hadn't been able to follow all the discussion in the thread. Just to be clear - since |
Currently, no - sameValue is not exposed as a callable function.
Yes.
Anything to do with NaNs is confusing in the details. Intuitions mislead. |
Agreed. My concern is more around the fact that the document is defining behavior that can't ever be used, though (so not really about NaNs… could be about anything). I'm happy to let this get merged, but it strikes me as really strange to be adding definitions that can't possibly be used/observed in a SPARQL system. Obviously it would be different if |
Issue #201 for whether |
Squashed authoring, editing and review commits. |
</li> | ||
<li>If <code>term1</code> and <code>term2</code> are both | ||
<a data-cite="RDF12-CONCEPTS#dfn-literal">literals</a> | ||
and the SPARQL processor can determine that their the values are equal, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and the SPARQL processor can determine that their the values are equal, | |
and the SPARQL processor can determine that their values are equal, |
</li> | ||
<li>If <code>term1</code> and <code>term2</code> are both | ||
<a data-cite="RDF12-CONCEPTS#dfn-literal">literals</a> | ||
and the SPARQL processor can determine the values can not be equal, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and the SPARQL processor can determine the values can not be equal, | |
and the SPARQL processor can determine that their values cannot be equal, |
can determine that the values of these literals are equal or are not equal. | ||
If the SPARQL processor can not be sure, it returns `error`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can determine that the values of these literals are equal or are not equal. | |
If the SPARQL processor can not be sure, it returns `error`. | |
can determine that the values of these literals are equal or are not equal, respectively. | |
If the SPARQL processor cannot be sure, it returns `error`. |
This closes #187.
This closes #25.
Changes:
RDFterm-equal
assameValue
sameTerm
,sameValue
sameValue
(see Refining RDFTerm-equals #187)Preview | Diff