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

[All] spec edits, please have a look

From: Felix Sasaki <fsasaki@w3.org>
Date: Fri, 23 Nov 2012 17:06:04 +0100
Message-ID: <50AF9EEC.7030903@w3.org>
To: "public-multilingualweb-lt@w3.org" <public-multilingualweb-lt@w3.org>
Hi all,

I did the following edits to the spec, summarized in one mail so that 
people don't need so many threads. Below is also a question related to 
toolsRef, please check.

- Added this sentence to the provenance section:
"In HTML5 the standoff markup MUST be stored inside a script element 
with its id attribute that MUST be set to the same value as the xml:id 
attribute of the provenanceRecords element it contains.": add this note 
to provenance too. Add a related section after sec. 7.5.

- Made the similar sentence we have for lq-issue a normal, that is 
normative paragraph. "Notes" are only informative text, they MUST NOT 
contain normative wording.

- Also provenance: I implemented the comments from Pablo (thanks a lot 
for these) at

- Again for provenance: separated the definitions of information from 
the attribute definitions, like in the lq-issues section. See the table at
The benefit is that a lot of definitions are given only once, and the 
section overall gets shorter.

- Finally (?) for provenance: the definition of provRef and 
provRefPointer still said that the IRIs must point to an RDF based 
provenance record. However, we had said in a note
"The specification does not define the format of external provenance 
data, but it is recommended that an open provenance or change logging 
format be used, e.g. the W3C provenance data model [PROV-DM]."
So I removed the normative reference to the provenance data model from 
the "Reference to external provenance descriptions" row at

- Added a list of data category identifiers to
This closes action-312. I also changed the examples that have toolRefs 
so that they use the adequate identifiers.
At Yves: Your changes to the toolsRef section described at

look fine to me.

- A question: we say for toolsRef e.g. in the mt-confidence section
"Any node selected by the MT Confidence data category MUST be contained 
in an element with the toolsRef (or in HTML5, its-tools-ref) attribute 
specified for the MT Confidence data category. "
But what about global rules? See e.g. example
Here, how do the assure that the above MUST statement is true?

- Action-317: added
to make the xml:id requirement for standoff in HTML5 clear.


Received on Friday, 23 November 2012 16:06:30 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:08:24 UTC