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

[ESW Wiki] Update of "its0505LimitImpact" by YvesSavourel

From: <w3t-archive+esw-wiki@w3.org>
Date: Fri, 20 May 2005 20:18:56 -0000
To: w3t-archive+esw-wiki@w3.org
Message-ID: <20050520201856.25860.34945@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 YvesSavourel:
http://esw.w3.org/topic/its0505LimitImpact


------------------------------------------------------------------------------
  '''[http://esw.w3.org/topic/its0505WikiProcess  Status: Initial Draft]''' 
  ie. please focus on technical content, rather than wordsmithing at this stage.
  
+ The original discussion is the feedback from Norm:
+ [http://lists.w3.org/Archives/Member/member-i18n-its/2005AprJun/0025.html]
+ 
  Author: Yves Savourel
  
  = Limited Impact of the Tag Set =
  
+ 
+ === Summary ===
+ 
+ All solutions provided by the tag set should be designed to have as less impact as possible on the tree structure of the original document.
+ 
+ === Description ===
+ 
+ Inserting elements or attributes of a different namespace in an XML document can have side effects on various processing aspects. For example, the inserted nodes may:
+ 
+  * break the XPath expressions already in use to access part of the document.
+ 
+  * interfere with {{{<xsl:value-of/>}}} for extracting information.
+ 
+  * interfere with numbering and other aspects of styling the original document.
+ 
+ Any solution for one of the ITS requirements must take in account these potential drawbacks and try to be implemented in a way that limits the impact in the original document.
+ 
+ For instance:
+ 
+  * Use attributes whenever possible (they have a lesser impact than elements). For example:
+ 
+  {{{<table ist:translate="no">
+  <tr>...
+ </table>}}}
+ 
+  is better than:
+ 
+  {{{<its:notrans>
+  <table>
+   <tr>...
+  </table>
+ </notrans>}}}
+ 
+  * Use data categories that already exist in the original markup by either mapping ITS concepts to them (see [http://esw.w3.org/topic/its0504ReqPurposeSpecMap]) or using them to carry the ITS attributes:
+ 
+  {{{<p>The motto of Qu├ębec is:
+ <q its:translate="no">"je me souviens"</q>.</p>}}}
+ 
+  * Group general ITS information in branches that are placed in locations where they have a minimal impact:
+ 
+  {{{<doc>
+  <its:info>
+   ...
+  </its:info>
+  <header>...
+  <body>...}}}
+ 
Received on Friday, 20 May 2005 20:37:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:12:44 GMT