Skip to content
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

Literal equality and language tags #100

Open
iherman opened this issue Oct 21, 2024 · 0 comments
Open

Literal equality and language tags #100

iherman opened this issue Oct 21, 2024 · 0 comments
Labels
needs discussion Proposed for discussion in an upcoming meeting spec:editorial Minor issue or proposed change in the specification (markup, typo, informative text)

Comments

@iherman
Copy link
Member

iherman commented Oct 21, 2024

The last paragraph of Section §3.3 Literals says

Literal term equality: Two literals are term-equal (the same RDF literal) if and only if the two lexical forms, the two datatype IRIs, the two language tags (if any), and the two base directions (if any) compare equal, using case sensitive matching 

But the third bullet point at the beginning of the section says:

The language tag MUST be well-formed according to section 2.2.9 of [BCP47], and MUST be treated consistently, that is, in a case insensitive manner.

The two statements seem to contradict one another on the language tags: they are to be compared in a case-insensitive manner...

@iherman iherman added the spec:editorial Minor issue or proposed change in the specification (markup, typo, informative text) label Oct 21, 2024
@gkellogg gkellogg added the needs discussion Proposed for discussion in an upcoming meeting label Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs discussion Proposed for discussion in an upcoming meeting spec:editorial Minor issue or proposed change in the specification (markup, typo, informative text)
Projects
None yet
Development

No branches or pull requests

2 participants