W3C home > Mailing lists > Public > public-multilingualweb-lt@w3.org > November 2012

Further changes, please check (Re: [Agenda] MLW-LT call 26 November, 4 p.m. UTC)

From: Felix Sasaki <fsasaki@w3.org>
Date: Sun, 25 Nov 2012 12:06:43 +0100
Message-ID: <50B1FBC3.9080707@w3.org>
To: public-multilingualweb-lt@w3.org
Hi Yves, Jirka (wrt to your reply to the agenda mail), all,

thanks for checking, Yves, I updated the pointer list

I also did action-313 and checked the data category overview table at

During checking I removed the links to the old location of the test 
suite and added links to examples (global, local, without saying "xml or 
html") within the spec.
In the table I removed the default for storage size 
"storageEncoding="UTF-8"". A default in this table means: the value is 
given even if no ITS local markup or global rule is used. That is not 
the case for "storageEncoding": the default is only given if there is 
"storageSize" (or globally also "storageSizePointer") attribute.

I saw in sec 3.7 that this list
"The attributes href, locNoteRef and termInfoRef which contain resource 
identifiers MUST allow the usage of Internationalized Resource 
Identifiers (IRIs, [RFC 3987] or its successor) to ease the adoption of 
ITS in international application scenarios."
needs to be updated.
And this note too, potentially: "The ITS schemas in Appendix E: Schemas 
for ITS are not normative."

Other changes:
- made sure that "0 to 1" now always says "0 to 1 (inclusive)".

- Auto generated a list of elements and attributes, see
The list currently is wrong, e.g. missing a lot of attributes from 
HTML5. We need to check it manually or replace it with Shauns' table.

- checked the "gi" and "attr" elements. For the co-editors, these *must* 
only be used for ITS markup. For "gi" and "attr" I also created a 
styling (without linking) - these end up in HTML as
<code class="its-elem-markup">
<code class="its-attr-markup"
All, if you have a better idea for styling than
*.its-elem-markup {
    color: red;

*.its-attr-markup {
 color: red;
please let me know or change the css right away :)

Also for co-editors, for nested list in ODD, it is necessary to follow 
this pattern:
That is, you need a "p" element before opening the nested list. 
Otherwise, the generated HTML is invalid.



Am 24.11.12 15:31, schrieb Yves Savourel:
> Hi Felix,
>> action-308 update list of pointer attributes done,
>> see http://www.w3.org/International/multilingualweb/lt/drafts/its20/its20.html#pointer-attributes-list
> I see all Localization Quality Issue pointers in that list, but based on action 303, only locQualityIssuesRefPointer should remain.
> Shall I update the specification?
> -yves
Received on Sunday, 25 November 2012 11:07:04 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:31:58 UTC