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

Change log ITS tagset draft

From: Felix Sasaki <fsasaki@w3.org>
Date: Tue, 14 Feb 2006 19:53:46 +0900
Message-ID: <43F1B6BA.7080004@w3.org>
To: public-i18n-its@w3.org
Hi all,

this is my first round of change implementations. It encompasses
proposals from Yves at
http://lists.w3.org/Archives/Public/public-i18n-its/2006JanMar/0137.html
. Look for "FS>" below. Please have a rough look on this, to see if you
are happy with it :)


---1:

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

FS> Will create s.t. about this until tomorrow.

---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.

FS> Fixed


---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).

FS> How about "Selection mechanisms, here exemplified via the
translatability data category"?

---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...

FS> We now mention CSS in sec. 4, see
http://www.w3.org/International/its/itstagset/itstagset.html#selection ,
I think that's o.k. . So I'll delete that ed. note.


---5:

Ease of integration, first bullet:

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

FS> done.


---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)."

FS> done.

---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).

FS> I choose "RELAX NG", which is used within the RELAX NG specification.


---8:

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

FS> Good question. I would rather say "A data category and its
implementations".

---9:

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

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

FS> Done.

---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.

FS> I have put 3.1 as a separate section.


---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.

FS> Yes, I have changed that.

---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.

FS> I deleted the section, it seems to me useless, too.

---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.

FS> that was not on purpose, I have changed that.

---14:

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

FS> they are now different, one for an RELAX NG element declaration with
ITS annotation, one for an RELAX NG attribute declaration.

---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."

FS> changed that to "To avoid a conflict with rule 2., default
namespaces must not be used in the XPath expressions.".

---16:

Example 24:

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

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

FS> Done.

-- Felix

Received on Tuesday, 14 February 2006 10:53:53 UTC

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