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

[ESW Wiki] Update of "its0505LimitImpact" by YvesSavourel

From: Richard Ishida <ishida@w3.org>
Date: Mon, 22 Aug 2005 09:36:39 +0100
To: <public-i18n-its@w3.org>
Message-Id: <20050822083640.0A3784EECF@homer.w3.org>


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

------------------------------------------------------------------------------
  = Limited Impact =
  
  
- === Summary ===
+ == Summary ==
  
- All solutions proposed should be designed to have as less impact as possible on the tree structure of the original document and on the content models in the original schema.
+ [R014] All solutions proposed should be designed to have as less impact as possible on the tree structure of the original document and on the content models in the original schema.
  
  
- === Challenge/Issue ===
+ == Challenges ==
  
  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.
+  * Break the XPath expressions already in use to access part of the document.
  
-  * interfere with {{{<xsl:value-of/>}}} for extracting information.
+  * Interfere with {{{<xsl:value-of/>}}} for extracting information.
  
-  * interfere with numbering and other aspects of styling the original document.
+  * 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 offer implementations that has a limited impact in the original document and on the content models in the original schema.
+ Solutions for any of the ITS requirements must take in account these potential drawbacks and offer implementations that have limited impact on the original document and on the content models in the original schema.
  
  For instance:
  
   * Use attributes whenever possible (they have a lesser impact than elements). For example:
  
+  {{{Using an extra attribute
+ 
-  {{{<table its:translate="no">
+ <table translate="no">
   <tr>...
  </table>}}}
  
   is better than:
  
-  {{{<its:notrans>
+  {{{Using an extra element
+ 
+ <notrans>
   <table>
    <tr>...
   </table>
  </notrans>}}}
  
-  * Use data categories that already exist in the original markup by either mapping them to ITS concepts (see [http://esw.w3.org/topic/its0504ReqPurposeSpecMap]) or by using them to carry ITS attributes. For example:
+  * Use data categories that already exist in the original markup by either mapping them to ITS concepts (see "[http://esw.w3.org/topic/its0504ReqPurposeSpecMap]") or by using them to carry ITS attributes. For example:
  
-  {{{<its:info>
+  {{{Mapping concepts
+ 
+ <info>
- <its:mapping target='quote' its='notrans'/>
+  <mapping target='quote' its='notrans'/>
- <its:info>
+ <info>
  ...
  <para>The motto of Québec is:
- <quote>"je me souviens"</quote>.</para>}}}
+  <quote>"je me souviens"</quote>.</para>}}}
  
   * Group general ITS information in branches that are placed in locations where they have a minimal impact:
  
-  {{{<doc>
+  {{{Information placement
+ <doc>
-  <its:info>
+  <info>
-   ...
+  ...
-  </its:info>
+  </info>
   <header>...
   <body>...}}}
  
  
- === Notes ===
+ == Notes ==
  
- On possible solution which has to be discussed is whether ITS should encompass not only a tag set, but also a specification of processing steps for documents. One step then could be the separation of the document in namespace specific sections. This would limit the side effects mentioned above.
+ One possible solution which has to be discussed is whether ITS should encompass not only a tag set, but also a specification of processing steps for documents. One step then could be the separation of the document in namespace specific sections. This would limit the side effects mentioned above.
  
- The Namespace Routing Language [http://www.thaiopensource.com/relaxng/nrl.html] could be used for this purpose. Part 4 "NVDL [Namespace-based Validation Dispatching Language]" of the ISO / IEC 19757 proposal DSDL [Document Schema Definition Languages] also relies mainly on NRL. The following example NRL document can be applied to XML documents with markup from the xhtml namespace and a fictive ITS namespace. With the NRL document, the XML document are validated only agains the xhtml scheme "xhtml.rng":
+ The Namespace Routing Language [NRL][http://www.thaiopensource.com/relaxng/nrl.html] could be used for this purpose. The "Part 4: Namespace-based Validation Dispatching Language — NVDL" [NVDL][http://dsdl.org/0525.pdf] of the ISO/IEC 19757 proposal "Document Schema Definition Languages (DSDL)" [DSDL][http://dsdl.org/] relies mainly on NRL. The following example NRL document can be applied to XML documents with markup from the xhtml namespace and a fictive ITS namespace. With the NRL document, the XML document are validated only against the XHTML scheme "xhtml.rng":
  
  {{{
  <rules startMode="root"
@@ -95, +102 @@

  </rules>
  }}}
  
+ 
- === The requirement in the Schema versus in the XML document ===
+ == The requirement in the Schema versus in the XML document ==
  
  In a schema, this requirement concerns the structure of content models. Problems can arise also if the schema has no namespace:
  
  {{{
- <!ELEMENT text (div+>
+ <(exclamation-point)ELEMENT text (div+>
- <!ELEMENT div (p | table | ...>
+ <(exclamation-point)ELEMENT div (p | table | ...>
  }}} 
  
  If an ITS span element should be used to indicate i18n and l10n related properties of the <table> element, the <table> element would disappear from the content model of the <div> element:
  
  {{{
- <!ELEMENT div (p | its:span | ...>
+ <(exclamation-point)ELEMENT div (p | its:span | ...>
- <!ELEMENT its:span (table | ...)>
+ <(exclamation-point)ELEMENT its:span (table | ...)>
  }}}
  
  Since there is no namespace for the original schema (i.e. the <text>, <div>, <table> or <p> elements), the Namespace Routing Language does not solve the conflicts between ITS elements and other elements.
Received on Monday, 22 August 2005 08:37:21 GMT

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