Skip to content

Language tags #168

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.

Sign up for GitHub

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

Merged
merged 10 commits into from
Oct 14, 2019
Merged

Language tags #168

Show file tree
Hide file tree
Changes from 8 commits
Commits
Show all changes
10 commits
Select commit Hold shift + click to select a range
918e34f
Remove requirement to normalize language tags to lower case, but note…
gkellogg Oct 12, 2019
2f1d6fa
Notes about normalizing language tags, issuing warnings when not well…
gkellogg Oct 13, 2019
d3897ed
Relocate some compact tests to preserve test ordering.
gkellogg Oct 13, 2019
9e28eb4
Add a test for term selection where case of language does not match.
gkellogg Oct 13, 2019
284630a
Add a test for term selection where case of language does not match.
gkellogg Oct 13, 2019
d4d47d2
Apply suggestions from @rubensworks code review
gkellogg Oct 14, 2019
0d45563
Revert language about handling invalid language tags.
gkellogg Oct 14, 2019
4f7ebfe
Fix minor wording around well-formed.
gkellogg Oct 14, 2019
92b7d98
Tweak to Value Compaction to do case-insensitive comparision of langu…
gkellogg Oct 14, 2019
1c62284
Fix some awkwardness in wording when considering `@language` in Expan…
gkellogg Oct 14, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions common/terms.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -113,8 +113,9 @@
consists of a string and a non-empty language tag
as defined by [[BCP47]].
The <dfn data-cite="RDF11-CONCEPTS#dfn-language-tag">language tag</dfn> MUST be well-formed
according to <a data-cite="BCP47#section-2.2.9">section 2.2.9 Classes of Conformance</a> of [[BCP47]],
and is normalized to lowercase.</dd>
according to <a data-cite="BCP47#section-2.2.9">section 2.2.9 Classes of Conformance</a> of [[BCP47]].
<span class="changed note">Processors MAY normalize <a>language tags</a> to lowercase.</span>
</dd>
<dt><dfn data-cite="LINKED-DATA" data-no-xref="" class="preserve">Linked Data</dfn></dt><dd>
A set of documents, each containing a representation of a <a>linked data graph</a> or <a>dataset</a>.</dd>
<dt><dfn data-cite="RDF11-CONCEPTS#dfn-rdf-graph" data-lt="linked data graph|graph" class="preserve">RDF graph</dfn></dt><dd>
Expand Down
109 changes: 75 additions & 34 deletions index.html
View file
Open in desktop

Large diffs are not rendered by default.

1 change: 1 addition & 0 deletions tests/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,6 +59,7 @@ JSON-LD Object comparison compares JSON objects, arrays, and values recursively
* JSON objects are compared member by member without regard to the ordering of members within the object. Each member must have a corresponding member in the object being compared to. Values are compared recursively.
* JSON arrays are generally compared without regard to order (the lone exception being if the referencing key is `@list`). Each item within the array must be equivalent to an item in the array being compared to by using the comparison algorithm recursively. For values of `@list`, the order of these items is significant.
* JSON values are compared using strict equality.
* Values of `@language`, and other places where language tags may be used are specified in lowercase in the test results. Implementations should either normalize language tags for testing purposes, or compare language tags in a case-independent way.

Note that some tests require re-expansion and comparison, as list values may exist as values of properties that have `@container: @list` and the comparison algorithm will not consider ordering significant.

Expand Down
Loading