W3C home > Mailing lists > Public > public-i18n-its@w3.org > October to December 2005

[ESW Wiki] Update of "its0509SpecScoping" by fsasaki

From: <w3t-archive+esw-wiki@w3.org>
Date: Thu, 06 Oct 2005 16:44:30 -0000
To: w3t-archive+esw-wiki@w3.org
Message-ID: <20051006164430.12738.35374@localhost.localdomain>
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "ESW Wiki" for change notification.

The following page has been changed by fsasaki:
http://esw.w3.org/topic/its0509SpecScoping


------------------------------------------------------------------------------
  
  Note that we would be doing all this just to support overriding information for attributes. And I'm not sure how easy it would be to support extension with this.''']END-YS]]'''
  
+ '''[[FS-START['''
+ 
+ I think a high priority should be that the ITS tag set should be as small as possible. Yves proposal allows to reuse its:rule for various kinds of rules, depending on the attributes. I just would like to have the same tags for the in situ and the dislocated case. A general solution for this looks like this:
+ 
+ {{{
+ <myns:myElement its:translateNo="//para">..</myns:myElement>
+ <myns:myElement its:translateYes="@productCode">..</myns:myElement>
+ }}}
+ 
+ A content author who refers to the content of the element would write: 
+ 
+ {{{
+ <myns:myElement its:translateNo=".">..</myns:myElement>
+ }}}
+ 
+ If we would create locinfo, we could do that with a its:locinfo attribute in the same way:
+ 
+ {{{
+ <myns:para its:locinfo="//para">This is some locinfo</myns:para>
+ }}}
+ 
+ The information "This is some locinfo" would apply to all kinds of locinfo.
+ 
+ So the general way to express rules and other kinds of information:
+ 
+  * have attributes which describe what all kind of ITS related information this is
+ 
+  * have for all these attributes xpath expressions as a value, with "." as the value for the content author case. I think not complete xpath, but the subset used in xslt would be good, see [http://www.w3.org/TR/2005/WD-xslt20-20050915/#pattern-syntax]
+ 
+  * leave the interpretation of the attributes specific. E.g., its:translateNo or its:translateYes will be interpreted as "no" or "yes". its:locinfo will be interpreted that the content of the myns:para element contains the locinfo. its:ruby or its:bidi could be constructed in the same way, with a different interpretation. 
+ 
+ This way of adding ITS information via attributes is borrowed from XLink, cf. [http://www.w3.org/TR/2005/WD-xlink11-20050707/#att-method]. So we would not have to invent something, we just reuse the Xlink way to indicate "this element contains ITS specific information" and XPath / the XSLT subset of XPath. It would be good not to be revolutinary :) , and it has the advantage that ITS would have *no* elements, but only attributes. The XLink like solution - only using attributes -  would contribute to the solution of the limited impact requirement and make possible commentors from the architecture domain happy ;)''']END-FS]]'''
+ 
Received on Friday, 7 October 2005 02:05:37 UTC

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