Re: Fwd: I-D Action: draft-msporny-d-langtag-ext-00.txt
"Gordon P. Hemsley" <[email protected]> Mon, 27 May 2019 20:11:11 -0400
| Newsgroups | gmane.ietf.languages |
|---|---|
| Message-ID | <[email protected]> |
On 5/27/19 4:23 PM, Manu Sporny wrote: > On 5/27/19 3:40 PM, Gordon P. Hemsley wrote: >> To jump on the bandwagon of pointing to places where this has already >> been handled, CSS has whole specification for writing modes from a >> presentational perspective: >> >> https://www.w3.org/TR/css-writing-modes-3/ > > I fail to see how that helps express these concepts in a unified way > across JSON, JSON-LD, RDF, and CBOR (to name a subset of the syntaxes > that we're concerned about). I mean, it is helpful to see the options... > it's not helpful in that none of those options or design patterns exist > for the syntaxes previously mentioned. Unifying "JSON, JSON-LD, RDF, and CBOR" is not my concern. My concern is that numerous people who work with languages, localization, and internationalization on a daily basis have already considered these issues, and they are not as simple as a layperson may believe. It would be wise for groups who do not work directly with languages, writing systems, or locales on a daily basis to heed the advice and prior work of experts before endeavoring to standardize something that would affect those people. This is not a standard one can throw together in haste. > Here's some background, Gordon: > > https://github.com/w3c/rdf-dir-literal/issues/3#issuecomment-496004819 > > .... and why we're having this discussion: > > https://github.com/w3c/rdf-dir-literal/issues/3#issuecomment-496006350 > > .... and what the current proposed spec text in the Verifiable > Credentials Data Model specification regarding i18n states: > > https://pr-preview.s3.amazonaws.com/w3c/vc-data-model/pull/641.html#internationalization-considerations > > -- manu > My original e-mail was meant to be informational, but now that I have reviewed the links that you have included in multiple replies, I am further convinced that the existing work, the listed requirements, and the ramifications of the proposed solutions have not been sufficiently considered. -- Gordon P. Hemsley [email protected] http://gphemsley.org/