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

[ESW Wiki] Update of "its0504ReqPurposeSpecMap" by YvesSavourel

From: <w3t-archive+esw-wiki@w3.org>
Date: Tue, 23 Aug 2005 08:26:58 -0000
To: w3t-archive+esw-wiki@w3.org
Message-ID: <20050823082658.14973.53620@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/its0504ReqPurposeSpecMap


The comment on the change is:
Updated From req Doc

------------------------------------------------------------------------------
  
  Follow the [http://esw.w3.org/topic/itsHowTo conventions] for editing this page.
  
- '''[http://www.w3.org/International/geo/2004/article-devt-process.html Status: Working Draft]''' 
+ '''[http://www.w3.org/International/geo/2004/article-devt-process.html Status: Working Draft]''' (Req Doc) 
  
  Author: Christian Lieske
  
@@ -14, +14 @@

  
  == Summary ==
  
- Currently, it does not appear to be realistic that all XML vocabularies tag localization-relevant information identical (e.g. all use the "term" tag for terms). One way to take care of diverse localization-relevant markup in localization environments is a mapping mechanism which maps localization-relevant markup onto a canonical representation (such as the Internationalisation Tag Set).
+ [R008] Currently, it does not appear to be realistic that all XML vocabularies tag localization-relevant information identical (e.g. all use the "term" tag for terms). One way to take care of diverse localization-relevant markup in localization environments is a mapping mechanism which maps localization-relevant markup onto a canonical representation (such as the Internationalization Tag Set). 
  
- == Challenge/Issue ==
+ == Challenges ==
  
+ From a localization point of view, many XML vocabularies include markup which requires special attention, since the markup is associated with a specific type of content. Examples:
- From a localization point of view, many XML vocabularies include markup
- which requires special attention, since the markup is associated with a
- specific type of content. Examples:
  
-  a. elements which are associated with embedded/binary graphics
+  * elements which are associated with embedded/binary graphics
-  
-  b. elements which are associated with specific text styles (e.g. underline and bold)
  
-  c. elements which are associated with linking (e.g. the "a" in HTML)
+  * elements which are associated with specific text styles (e.g. underline and bold)
  
-  d. elements which are associated with lists
+  * elements which are associated with linking (e.g. <a> in HTML)
  
-  e. elements which are associated with tables
+  * elements which are associated with lists
  
-  f. elements which are associated with with generated content (e.g. an element that fires a query to a database in order to pull in the data for a product catalogue)
+  * elements which are associated with tables
  
- Some reasons why this type of markup may require special attention:
+ elements which are associated with with generated content (e.g. an element that fires a query to a database in order to pull in the data for a product catalogue)
  
-  a. the localization tool may be able to render specific text styles in a standard way (e.g. increased font weight for bold)
+ Here are some reasons why this type of markup may require special attention:
  
-  b. embedded binary images may have to follow a specific workflow
+  * the localization tool may be able to render specific text styles in a standard way (e.g. increased font weight for bold)
  
-  c. content generation queries may have to be adapted
+  * embedded binary images may have to follow a specific workflow
  
+  * content generation queries may have to be adapted
- Since it is hardly imaginable that all content developers will be able
- to work with the same elements and attributes for this specific type of
- content, the ITS should include markup which allows people to specify
- the purpose of specific elements.
  
- Challenges arise for example from the fact that the 'source/original' vocabularies may vary widely wrt. the representation they choose for a specific data category (e.g. their markup related to graphics; see the longer discussion of this at [http://lists.w3.org/Archives/Public/public-i18n-its/2005AprJun/0096.html].
+ Since it is hardly imaginable that all content developers will be able to work with the same elements and attributes for this specific type of content, the ITS should include markup which allows people to specify the purpose of specific elements.
+ 
+ Challenges arise for example from the fact that the 'source/original' vocabularies may vary widely with regards to the representation they choose for a specific data category (e.g. their markup related to graphics; see the longer discussion of this).
+ 
  
  == Notes ==
  
-  * This requirement is related to [http://esw.w3.org/topic/its0505LimitImpact].
+ This requirement is related to the "Section 3.15: Limited Impact" requirement.
  
-  * For the specific case of linking something to look at already exists: HLink (cf. ["http://www.w3.org/TR/2002/WD-hlink-20020913/"]).
+ For the specific case of linking something to look at already exists: HLink [HLink].
  
-  * The approach may be used to support term identification. Suppose that an original document has the following:
+ The approach may be used to support term identification. Suppose that an original document has the following:
  
+ {{{Markup to map
  
-  "You can define multiple computation IDs for one company in the <index sortstr="currency restatement">Currency Restatement</index> program"
+ You can define multiple computation IDs for one company in the <index sortstr="currency restatement">Currency Restatement</index> program.}}}
  
+ When you wish that the {{{<index>}}} element serves as an ITS "term", you could use the following mapping:
  
-  When you wish that the "index" element serves as an ITS "term", you could use the following purposeSpec: 
+ {{{Mapping
  
+ <purposeSpec>
+  <servesPurpose origVoc="index" its="term"/>
+ </purposeSpec>
+ One question to answer is: How can existing attributes (e.g. {{{sortstr}}} in the sample above) be carried over, or how can new attributes (like {{{partOfSpeech}}}, {{{termType|||) be introduced?}}}
  
-  <its:purposeSpec>
- 	<servesPurpose origVoc="index" its="term"/>
-  </its:purposeSpec>
- 
- 
-  One question to answer is: How can existing attributes (e.g. "sortstr" in the sample above") be carried over, or how can new attributes (like "POS", "termType") be introduced?
  
  == Quick Guideline Thoughts ==
  
Received on Tuesday, 23 August 2005 13:14:31 GMT

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