[ESW Wiki] Update of "its0509SpecScoping" by ChristianLieske

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 ChristianLieske:
http://esw.w3.org/topic/its0509SpecScoping


------------------------------------------------------------------------------
  
  = Scoping Mechanism =
  
+ Any of the data categories relevant for ITS (e.g. the "Indicator of Translatability") should be subject to well-defined scoping rules. Otherwise, the semantics of the data category will not be clear enough to allow proper implementations.
+ 
+ Example for the "Indicator of Translatability":
+ 
+ A value can be specified on any element. The value pertains to any child element unless overwritten.
+ 
+ In a way, any attempt to scoping needs to address the following issues:
+ 
+  * How can scoping be defined declaratively? Example: The "Indicator of Translatability" is defined
+    by means of an XPath expression in a special container element.
+ 
+  * Which implicit scoping rules apply? Example: The value pertains to any child element unless overwritten.
+ 
+  * What are the rules for defaults? Example: If no "Indicator of Translatability" is present, all of
+    the content should be translated.
+ 
+ '''[CL] Of course we could refer to information/discussions related to "xml:lang" here.''' 
+ 
  === Levels ===
  
- We identified four main location where ITS information could need to be specified.
+ Four main locations where ITS information could specified can be envisioned:
+ 
+ '''[CL] All but the second one are similar to CSS; see [http://lists.w3.org/Archives/Public/public-i18n-its/2005JanMar/0043]'''
  
   * In an external file (e.g. to address general information for DTD-based document types)
  
+ '''[CL] I would rather give external CSS as an example. '''
+ 
-  * In schemes files (e.g. XML Schema and Relax-NG documents).
+  * In schemas (e.g. XML Schema and Relax-NG documents).
  
   * "In a header" of a document instance, i.e. grouped somewhere at the top the document. (e.g. to address cases where ITS info has to be overwritten at a high level in a document (vs. at the element level).
  
+ '''[CL] I would rather give the 'style' element as an example. '''
+ 
   * At the element level in a document instance. (e.g. to overwrite the ITS info for that element).
  
+ '''[CL] I would rather give the 'style' attribute as an example. '''
  
- === Example with translatibility ===
+ === Discussion (Example related to (Indicator of Translatibility)) ===
  
- To specify translability we currently defined the following:
+ To specify that something needs to be translated we currently defined the following:
  
-  * By default, all element are translatable and all attribute are not translatable.
+  * By default, the content of all elements has to be translated and the values of all attributes do not have to be translated.
  
+ To change the default (ie. to specify what needs to be translated and what does not need to be translated), we discussed the following:
+ 
-  * We have a {{{translate}}} attribute with a "yes|no" value to provide overwriting information. This can be used at the element level, and within schema files (e.g. when defining a XSD <element>).
+  * We have a {{{translate}}} attribute with a "yes|no" value. The attribute can be used at the element level, and within schema files (e.g. when defining a XSD <element>).
  
  {{{<para id="a1" its:translate="no"
   >Do not translate this, <span its:translate="yes">except this part</span>, etc.</para>}}}
  
+  * We have two attributes {{{translateYes}}} and {{{translateNo}}}. The values of these attributes are XPath expressions. The attributes can be used at the element level, and within schema files (e.g. when defining a XSD <element>).
  
- Several questions regarding the scope:
+ {{{<para id="a1" its:translateNo="."
+  >Do not translate this, <span its:translateYes=".">except this part</span>, etc.</para>}}}
  
-  * The cases for "external file" and "in a header" level are not supported yet.
+ The second approach seems provide more power:
  
-  * What do we do for attributes? Should overwriting the don't-translate default for attribute with an ITS mechanism be even allowed?
+  * Since XPath expressions are used, the information cannot only be given on the element-level. It can also be given in a "external file" or "in a header".
  
+  * Since XPath expressions are used, the information cannot only be give for element. Rather it can be given for attributes as well.
+ 
+ {{{<para id="a1" its:translateNo="@productCode"
+ Translate this, <span productCode="River"> it's great stuff</span>, etc.</para>}}}
+ 
+ Remark: Should overwriting the don't-translate default for attribute with an ITS mechanism be even allowed?
+

Received on Tuesday, 4 October 2005 13:40:00 UTC