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

Clarification proposal for the term "validation" #29

Merged
merged 2 commits into from Oct 6, 2020

Conversation

fsasaki
Copy link
Collaborator

@fsasaki fsasaki commented Oct 4, 2020

This should help implementers who want to create language tag validators. With the input from last telco, the picture may be more complex than this simple edit proposal - let's discuss.


Preview | Diff

@fsasaki fsasaki requested review from aphillips and r12a October 4, 2020 06:23
index.html Outdated
@@ -128,7 +128,7 @@ <h3>Languages and Language Tags</h3>

<p class="definition"><dfn data-lt="well-formed|well-formed language tag|well-formed language tags">Well-formed language tag</dfn>. A language tag that follows the grammar defined in [[BCP47]]. That is, it is structurally correct, consisting of ASCII letters and digit <a>subtags</a> of the prescribed length, separated by hyphens.</p>

<p class="definition"><dfn data-lt="valid|valid language tag|valid language tags">Valid language tag</dfn>. A language tag that is <a>well-formed</a> and has also been checked to ensure that each of the subtags appears in the <a>IANA Language Subtag Registry</a>.</p>
<p class="definition"><dfn data-lt="valid|valid language tag|valid language tags">Valid language tag</dfn>. A language tag that is <a>well-formed</a> and has also been checked to ensure that each of the subtags appears in the <a>IANA Language Subtag Registry</a> and that the <a href="https://tools.ietf.org/html/bcp47#section-2.2.9">conformance criteria for a valid language tag</a> from [[BCP47]] apply.</p>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is a good idea, but reading back through the conformance critieria (which do add a couple of minor checks--no repeat variants and no repeat extensions), it would be better to do this in reverse, i.e. something like:

A language tag that is well-formed and which also conforms to the additional conformance requirements in [BCP47], notably that each of the subtags appears in the IANA Language Subtag Registry.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, that makes sense - done.

@aphillips aphillips merged commit 22873da into w3c:gh-pages Oct 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants