Github user afs commented on the issue:
https://github.com/apache/jena/pull/237
Yes - I was agreeing with the approach of a collation function and it being
app-decided not fixed by the nature of the data.
If it can be done without to be hardwired in to `NodeValue.compare` and
overloading themeaning of `NodeValueString` I think we will be better placed
long term.
`NodeValueString` says "// A plain string, with no language tag, or an
xsd:string." and it seems likely this assumption is used elsewhere. I think
sneaking in something to `NodeValueString` may have effects elsewhere as it
violates the assumption of `NodeValueString` (e.g. equality).
`NodeValueSortKey`, and a new value space `VSPACE_SORTKEY`, which only is
useful in `ORDER BY` (and `makeNode` is an exception) means we can say "only
for sorting". `arq:collation` then stops being usable as a general function.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
