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 17:03:14 -0000
To: w3t-archive+esw-wiki@w3.org
Message-ID: <20051006170314.13644.18045@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


------------------------------------------------------------------------------
  
   * 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]]'''
+ 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 ;)
  
+ Oh, I forgot, here is an ruby example, combinded with translation information:
+ 
+ {{{
+ <myns:myElement its:ruby="." its:translateNo=".">
+ <its:rb>This is the base text.</its:rb>
+ <its:rt>This it the ruby text.</its:rt>
+ </myns:myElement>
+ }}}
+ 
+ The good message here is again that the myns:myElement element has no need to be deleted or converted into its:ruby. It is interpreted as its:ruby via the attribute its:ruby.
+ ''']END-FS]]'''
+ 
Received on Friday, 7 October 2005 02:25:47 UTC

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