W3C home > Mailing lists > Public > www-international@w3.org > July to September 2017

Comment on Requirements for Language and Direction Metadata in Data Formats (Editor's Draft 17 July 2017)

From: Najib Tounsi <ntounsi@gmail.com>
Date: Mon, 24 Jul 2017 15:14:04 +0100
To: www-international@w3.org, "Phillips, Addison" <addison@lab126.com>
Message-ID: <1f4fb8ac-cbaf-62d4-5c5e-978c69b9124f@emi.ac.ma>

Here are some few comments on the document.

- Producer and consumer are used in a well defined way (section2). These 
terms are encountered two times earlier in §1.1, and even if the context 
is clear, I think it's better to indicate there that these words will be 
well defined later (section 2 in this case).

- §1.1, 2nd paragraph after the JSON example,
"[..] For each of the fields containing natural language text [..] there 
will be a language attribute and base direction stored as metadata [..]
  "These *data fields* are used in a variety of ways [..]
I understand "These *metadata* are used ...". The wording "data fields" 
may create an ambiguity with the JSON fields containing text.
Besides, you say "the data structure provides no place to store these 
[i.e. metadata]."

- Last paragraph before §1.2

"They [producer and consumer] may have other considerations, such as 
field length, that are affected by the insertion of additional 
*controls* or markup".
Or (among "other considerations") the fact that those controls may use 
different escape sequence, e.g. &lrm; instead of \u200e.
(Your example : "authors": [ "\u200eHerman Melville" ], // contains LRM 
as first character)

Received on Monday, 24 July 2017 14:11:10 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:41:12 UTC