W3C home > Mailing lists > Public > public-i18n-its@w3.org > January to March 2006

[Bug 2808] Existing locInfo-like markup cannot be mapped using the locInfoSelector method

From: <bugzilla@wiggum.w3.org>
Date: Thu, 16 Feb 2006 11:15:46 +0000
To: public-i18n-its@w3.org
Message-Id: <E1F9h6w-00016t-DO@wiggum.w3.org>


------- Additional Comments From fsasaki@w3.org  2006-02-16 11:15 -------
See thread at

I have the feeling that there are two requirements here:

1) adding locInfo to some markup
2) Identifying locInfo which is already in the existing document

Below I have tried to separate these.

1) can be done
- in situ, via its:locInfo and its:locInfoType, or
- dislocated, via its:locInfo plus its:locInfoType plus  
Example dislocated (already in the draft):
<its:documentRule its:locInfo="This p element has to be handled carefully"
   its:locInfoType="alert" its:locInfoSelector="/body/p[1]"/>

2) can be done only dislocated, e.g. via its:locInfoContent and  
In the current ITS tagset draft we have (in example 32):
  <its:documentRule its:locInfo="" its:locInfoType="alert"
  <its:documentRule its:locInfo="" its:locInfoType="description"
This would be replaced by:
<its:documentRule its:locInfoContent="//*[@locn-alert]"
<its:documentRule its:locInfoContent="//*[@locn-alert]"

In that way, we would not have an additional attribute to  
its:locInfoSelector, but a different one. The benefit: an ITS processor  
1 "if I see its:locInfoSelector dislocated, I have to add the content of  
its:locInfo to a node in the XML document which has no localization  
information yet" (case 1) above)
2 "if I see its:locInfoContent, I have to extract existing localization  
information" (case 2) above)
Received on Thursday, 16 February 2006 11:15:58 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:43:06 UTC