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

[ESW Wiki] Update of "its0506ReqConstraints" by YvesSavourel

From: <w3t-archive+esw-wiki@w3.org>
Date: Tue, 23 Aug 2005 08:03:25 -0000
To: w3t-archive+esw-wiki@w3.org
Message-ID: <20050823080325.14075.12479@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/its0506ReqConstraints


The comment on the change is:
Updated From Req Doc

------------------------------------------------------------------------------
  
  Follow the [http://esw.w3.org/topic/itsHowTo conventions] for editing this page.
  
- '''[http://esw.w3.org/topic/its0505WikiProcess  Status: Working Draft]''' 
+ '''[http://esw.w3.org/topic/its0505WikiProcess  Status: Working Draft]''' (Req Doc)
  
  This item is a generalization of the "Indicator of Container Size" requirement started here: [http://esw.w3.org/topic/its0503ReqContainerSize].
  
@@ -14, +14 @@

  
  = Indicator of Constraints =
  
- === Summary ===
+ == Summary ==
+ 
+ [R001] It should be possible to associate one or more constraints to specific content
  
  
- It should be possible to associate one or more constraints to a specific content.
- 
- 
- === Challenge/Issue ===
+ == Challenges ==
  
  Translatable data may come with various constraints in the way they can be modified. For example, the content of the following <string> element must accommodate the length restriction imposed by the small display panel where it is used:
  
+ {{{Length restriction
+ 
- {{{<!-- LED display has only 16 characters -->
+ <!-- LED display has only 16 characters -->
- <string id="123">Printing...</string>}}}
+ <string id="s123">Printing...</string>}}}
  
  In this case a standard method should be used for indicating the dimensions of the container so that localization tools can automatically recognize them and, when possible, enforce the constraint during translation.
  
  Examples of constraints are:
  
-  * container size (e.g. maximum length, etc.)
+  * Container size (e.g. maximum length, etc.)
+ 
-  * text allowed in a limited set of characters (e.g. translatable paths or filenames)
+  * Text allowed in a limited set of characters (e.g. translatable paths or filenames)
-  
+ 
  These constraints may need to be defined at the schema level or they may need to be defined for specific instances of an element.
  
  In some cases, the constraint may be applicable only for a given context or a given tool.
  
+ == Notes ==
  
+ XSD (XML Schema Part 2: Datatypes Second Edition) provides a mechanism to define "Constraining Facets" ([XSD][http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/], section 4.3) that may provide some solution for this requirement at the schema level. At the instance level, Schematron [Schematron][http://www.schematron.com/] could be used for the same purpose.
- === Notes ===
- 
- XSD (XML Schema Part 2: Datatypes Second Edition) provides a mechanism to define "Constraining Facets" http://www.w3.org/TR/xmlschema-2/#rf-facets that may provide some solution for this requirement at the schema level. At the instance level, Schematron ([http://www.schematron.com/]) could be used for the same purpose.
  
  Sometimes the constraint may need to be expressed using units different from the unit used in the document. For example, the maximum length of a string may need to be expressed in byte or pixels, or display cells instead of characters. This may lead to the need for quite a few parameters with the constraint (e.g. the encoding to use, or the font and point-size information, etc.)
  
Received on Tuesday, 23 August 2005 12:50:49 GMT

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