Skip to content

Commit

Permalink
Remove suggestion to format language tags based on BCP47 rules and fo…
Browse files Browse the repository at this point in the history
…r comparing language tags after normalizing to lower case.
  • Loading branch information
gkellogg committed Jul 27, 2023
1 parent 2c1bbb2 commit c45d947
Showing 1 changed file with 2 additions and 3 deletions.
5 changes: 2 additions & 3 deletions spec/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -700,8 +700,7 @@ <h2>Literals</h2>
<p>A literal is a <dfn>language-tagged string</dfn> if the third element
is present and the fourth element is not present.
Lexical representations of language tags MAY be converted
to lower case or formatted according to the recommendation for formatting language tags
as described in <a data-cite="BCP47#section-2.1.1">section 2.1.1</a> of [[BCP47]].
to lower case.

This comment has been minimized.

Copy link
@afs

afs Jul 28, 2023

Contributor

I believe the original text (RDF 1.1) was discussing the transformation a parser might apply - or a rewrite of one graph into another - not a change in place.

The value of language tags is always treated as being in lower case.</p>

<p>A literal is a <dfn id="dfn-dir-lang-string">directional language-tagged string</dfn>
Expand Down Expand Up @@ -758,7 +757,7 @@ <h2>Literals</h2>
Two literals are term-equal (the same <a>RDF literal</a>)
if and only if the two <a>lexical forms</a>,
the two <a>datatype IRIs</a>,
the two <a>language tags</a> (if any) normalized to lower case, and
the two <a>language tags</a> (if any), and
the two <a>base directions</a> (if any),
all compare equal, character by character.
Thus, two literals can have the same value
Expand Down

0 comments on commit c45d947

Please sign in to comment.