W3C home > Mailing lists > Public > public-dxwg-wg@w3.org > September 2019

Re: [dxwg] [I18N] References to ISO-639 vs. BCP47 (#959)

From: Addison Phillips via GitHub <sysbot+gh@w3.org>
Date: Thu, 26 Sep 2019 23:40:18 +0000
To: public-dxwg-wg@w3.org
Message-ID: <issue_comment.created-535724656-1569541217-sysbot+gh@w3.org>
I'm a little confused by the outcome. I think the situation is necessarily confusing. For example, the purl.org link on the RDF property `dct:language` in the draft takes you to a page that outright references RFC4646 (a version of BCP47), but the range in the document has normative `SHOULD` language for both the use of ISO 639-1/2 and normative `SHOULD` (which is actually much weaker than BCP47) for using the `-1` code when both a `-1` and `-2` code exists. 

I realize the desire for URLs, particularly resolvable ones, for valid language tags remains an issue for some users/implementations and that is something that hasn't been solved for BCP47 yet. It's something I will take an action item to pursue separately in the I18N WG. 

The key problem here is that BCP47 language tags are widely used in Web-based specifications, making specs that don't support them a potential interoperability risk. Of course, the reverse is also true (that the sudden appearance of language tags could also be a problem). I do think it would be better if DCAT could insert at least some health warning or consider some guidance to at least call out the potential for change in this area so that implementers are not surprised if later the range restrictions are relaxed.

GitHub Notification of comment by aphillips
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/959#issuecomment-535724656 using your GitHub account
Received on Thursday, 26 September 2019 23:40:19 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:42:21 UTC