ITS Specification comments

Hi Felix, Christian,

Here are some comments on the specifications 
I have not read yet after section 3, and I've somewhat skipped the sections 3.1 and 3.2 (I'll look at Felix's comments for those two
sections).


---1:

Document status, at the 6th paragraph there is still "instructions can be found at TODO". TODO needs to be done.


---2: 

A) Para above example 1: "examples, the text " I think the comma is to be removed.

B) Same paragraph. It says "the text in bold face [...] shows the parts that need to be localized". But there are no bold not
brackets in any of the examples.


---3:

Section 1.3. second paragraph. This describes the the selection mechanism in general, but use the case for translate. It's fine, but
maybe a short phrase could make it clearer? So the reader doesn't think selection is just for translate. Maybe something like:

"Selection mechanisms (example with translatability): Content authors need ..."

Or

"Selection mechanisms (illustrated with the translatability data category): Content authors need ..."

Or something similar (I'm don't think my re-wording is very good).


---4:

[Ed. note: Here we could say s.t. like "this is similar to CSS". Any ideas?]

No idea. I think having a reference to CSS may help some, but may also confuse people a little if it's not worded very carefully. I
don't feel strongly either way...


---5:

Ease of integration, first bullet:

"...as possible assures easy..."
Maybe :
"...as possible ensures easy..."(?)


---6:

Ease of integration bullets. Maybe the two last need to be sentences to match the first one (not sure what the English rules are).
For example:

Change

"No dependence on technologies which are yet to be developed"

To

"ITS has no dependence on technologies which are yet to be developed."

And 

"Fit with existing work in the W3C architecture (e.g. use of XPath [XPath 1.0] as a selection mechansim)"

To

"ITS fits with existing work in the W3C architecture (e.g. use of XPath [XPath 1.0] as a selection mechansim)."


---7:

In the whole document we use sometimes "Relax NG" and sometimes "RELAX NG". We must pick the correct notation (I don't know which is
it) and use only that one (and the same in the techniques).


---8:

Example 4: Should we have an s at implementation is "Data categories and their implementation"?


---9:

Section 2.4, first paragraph: "The term [Definition: selection encompasses ..."

Should be: "[Definition: The term selection encompasses ..."


---10:

Section 3. and 3.1: It look strange to have a normative section immediately followed by a non-normative one. Maybe a better way to
do this? Mabye each 3.N sub-section should have normative/non-normative? And nothing at the 3. level?
...not sure.


---11:

Section 3.1 second para: "the "style" attribute and the "style" element" I think there are XMPSPec markup for att and element
instead to use quotes.

---12:

Example 14: there are still examples of the translateSelector.

I'm also not sure about "A selection of parts of an document or schema is always made for a single data category."

What does it mean exactly? That I can't do this:
<its:documentRule its:term="yes" its:termSelector="//trg:term"
 its:translate="no" its:translateSelector="//trg:tem"/>

Why?

I'm wondering if we need the section 3.3 at all.


---13:

Section 3.4, second bullet: " with a datacategory attribute. The " a space is missing after 'data'.
Same is the next bullet... Maybe that is on purpose? If so it looks strange to not have a space. If it refers to the Markup
declaration should it be "datacats" then? (or 'datacategory' used in the Markup declaration.
Note that the same link has a space in first para of section 3.4.2.


---14:

Examples 17 and 18 are the same so are the bullets.


---15:

Section 3.4.2. numbered list:

"To avoid a conflict with rule 2., the usage of default namespaces in the XPath expressions must be avoided."


---16:

Example 24:

"</dlentry> […]" should be "</dlentry> [...]"

"Et voila !</ph> The last rule wins</p>"
should be 
"Et voilą !</ph> The last rule wins.</p>"
(accent and period missing)


That's all for now.

Cheers,
-yves

Received on Wednesday, 8 February 2006 18:19:33 UTC