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

http://www.w3.org/Bugs/Public/show_bug.cgi?id=2808





------- Additional Comments From fsasaki@w3.org  2006-02-16 11:15 -------
See thread at
http://lists.w3.org/Archives/Public/public-i18n-its/2006JanMar/0128.html

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  
its:locInfoSelector.
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  
its:locInfoType
In the current ITS tagset draft we have (in example 32):
  <its:documentRule its:locInfo="" its:locInfoType="alert"
    its:locInfoSelector="//@locn-alert"/>
  <its:documentRule its:locInfo="" its:locInfoType="description"
    its:locInfoSelector="//@locn-note"/>
This would be replaced by:
<its:documentRule its:locInfoContent="//*[@locn-alert]"
   its:locInfoType="alert"/>
<its:documentRule its:locInfoContent="//*[@locn-alert]"
   its:locInfoType="alert"/>

In that way, we would not have an additional attribute to  
its:locInfoSelector, but a different one. The benefit: an ITS processor  
knows
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