Github user stain commented on the issue:
https://github.com/apache/commons-rdf/pull/30
This pull request returns `getLanguageTag()` in whatever case the
underlying platform does (e.g. I think RDF4J and JSONLD-Java preserves casing,
while Jena and Simple converts to lowercase.
I think it is only in `.equals()` and `.hashCode()` we need case
insensitivity.
There's arguments both ways if we should provide a consistent view across
the implementations (e.g. always lowercase); or if we should provide a
consistency with what the underlying implementation does (e.g. if it is
preserves casing for presentation purposes).
Commons RDF don't have any value handling mechanisms now for say
converting`"13.37"^^xsd:float` to a Java float `13.37f` (without going through
the underlying implementations and related methods); or determining value
equality, so I think it is not too weird if Commons RDF doesn't do anything
clever about language tags either (beyond spec compliance).
But if someone were to add a Common RDF API for such literal value
handling, it could be natural to also add "utils" methods for presenting or
parsing language tags (e.g. `isLanguageTagEqual("en-us", "en-US")` as well as
hierarchical comparisons, something like `isSameLanguageTagFamily("en-us",
"en-GB")`
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
