W3C home > Mailing lists > Public > public-i18n-its@w3.org > April to June 2006

Comments on Conformance section (part 2)

From: Yves Savourel <yves@opentag.com>
Date: Sat, 1 Apr 2006 19:56:40 -0700
To: "Felix Sasaki" <fsasaki@w3.org>, "Christian Lieske" <christian.lieske@sap.com>
Cc: <public-i18n-its@w3.org>
Message-ID: <001c01c65601$1186f0d0$0300a8c0@Breizh>

Hi Felix, Christian, all,

Here are more notes on the specifoications:


===1: Paragraph 1 of section 4.2:

I would replace "Description: processing expectations ..." by "Description: The processing expectations ..."

I would replace "existing or new schema" by just "schema" (everywhere!)



===2: Paragraph 2 of section 4.2:

I would replace "...type: the processing ..." by "...type: The processing ..." 

I would replace "In addition to selection related processing expectation, an additional set of expecations is described for the ruby
data category and directionality data category, by normatively referencing external specifications."

By

"In addition, a set of processing expecations specific to the ruby data category and the directionality data category, refers to
external specifications."


===3: Paragraph 3 of section 4.2:

I would replace "...product:. Processing..." by "...product: Processing..." (delete the .)

I would replace "...which needs to process the nodes (element and attribute nodes) which are captured by a data category for
internationalization and localization."

By

...which needs to process for internationalization or localization the element or attribute nodes captured by a data category."


===4: Clauses of section 4.2:

A) A space is missing in clause 2-1: -> "oneselection"

B) Clause 2-3 and 2-1 seems contradictory: It seems one one cannot both support only one type of selection and take "Section 5.2:
Precedence between Selections" into account as a whole.

Maybe saying: "2-3: If an application claims to process ITS markup for a given data category, it must take the precedence
definitions for selections defined in Section 5.2: Precedence between Selections into account, for the type of selection it
processes." (?)

===5: paragraph 2 after the clauses:

I would replace:

""Applications" which are conform to the clauses above can be for example ITS markup..."

By:

"Applications which are conform to the clauses above can be, for example: ITS markup..."

(removing quotes, adding comman, and colon)

Typo: "They only common..." should be "Their only common..."


===6: Last paragraph of section 4.2:

I wonder if this paragraph is not more confusing than helping. It just repeats what some of the clauses say. I would think of
dropping it.

Layout: the paragraphs below the "Examples" parts in both section 4.1 and 4.2 are indented. I assume it's by design. But it looks a
bit strange since the first paragraph in each case is not indented.


===7: Second bullet of section 5.1:

"...attributes , which..." should be:
"...attributes, which..."


===8: Section 5.1.1, Title and first paragrap:

Shouldn't 'based' be capitalized in "Global, Rule-based Selection"?
(not sure, just a question).

"more rule elements . " should be:
"more rule elements. "

"an locInfoPointer attribute can be used.." should be:
"an its:locInfoPointer attribute can be used."

In "using the rules element" 'rules' should be bolded/linked to ist definition.

In "a mandatory select attribute." 'select' should be 'selector' and bolded/linked to the selector definition (like in other
paragarphs). Same for its:locInfo, its:locInfoPointer, translate, etc.

Paragraph under the editor note: The link for 'selector' is broken.

I would rewrite: 
"with "/", that is, it..." by:
"with "/". That is, it..."


=== 9: Example 8:

It look strange to mix delcaration for TEI and DocBook in the same rules element.
I would rewrite it:

<!-- Definitions for TEI -->
<its:rules xmlns="http://www.w3.org/2005/11/its">
 <its:ns its:prefix="tei" its:uri="http://www.tei-c.org/ns/1.0"/>
 <termRule its:selector="//tei:term"/>
</its:rules>

<!-- Definitions for DocBook -->
<its:rules xmlns="http://www.w3.org/2005/11/its">
 <termRule its:selector="//qterm"/>
</its:rules>

About the note just below example 8:

"...element is motivated by [Schematron] and compliant..." Is *motivated* the right word? It's inspired, based-on, but motivated?...
Maybe our English native speakers can have this worded differently?


Paragraph: "Having its-global as the entry point of the schema serves as a wrapper schema for an external rules file." 

What is a "wrapper schema"? This sentence does not seem to add useful info. I would drop it (but maybe I just don't understand it).

Questions about "Instance Document":

- is it "Instance Document" or "Document Instance"? (searching on the W3C web site I see 615 occurences of "document instance" and
343 for "instance document". And I can't quite see the difference.

- Do we need to say that all the time? Didn't we use this as opposed to "schema document"? But now the distinction is gone. Why do
we keep saying it? Wouldn't just using "document" be better?


===9: paragraph 2 of section 5.1.1:

I would drop the first sentence: "Attributes which add information to the selected nodes are available for each data category. "
because that is what the paragraph just above already says.

I would split the first paragraph after "For example" and make the end one example, and the second paragraph a second example.

===10: Example 9:

"its:translate="no" at the head element means that the textual content of this element, including child elements and attributes,
should not be translated. its:translate="yes" at the body element means that the textual content of this element, including child
elements, but excluding attributes should be translated."

Wow... This is wrong.
Since when the default selection changes depending on the value of its:translate???
The fact the attributes are not translatable is not because of the selection for translate, but because the translate selection does
not affect their default state at all. its:translate has no effect on attributes, whether it's its:translate yes or no.

I would re-phrase this with something like:

"its:translate="no" at the head element means that the textual content of this element, including child elements, should not be
translated. its:translate="yes" at the body element means that the textual content of this element, including child elements, should
be translated. Attribute values of the selected elements or their children's are not affected by (a local?) its:translate. By
default they are not translatable."

===11: paragraph below example 9:

"The span element " span should be bolded/linked to its definition.


That's all for now.
-yves
Received on Sunday, 2 April 2006 02:56:59 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:43:07 UTC