- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 22 Feb 2006 15:49:38 +0000
- To: public-i18n-its@w3.org
- Cc:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=2915 Summary: Clarify relationship between host vocabulary markup data cats and ITS data cats Product: ITS Version: LastCall Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: ITS tagset AssignedTo: fsasaki@w3.org ReportedBy: christian.lieske@sap.com QAContact: public-i18n-its@w3.org (see also bug 2877 (terminology data category)) 1. What if the host vocabulary already has markup related to terms (see for example DITA and DocBook)? Do we recommend keeping it and mapping it via a documentRule? If so: Can this recommendation be generalized, and thus for example become part of the introduction to data categories? 2. What if the host vocabulary and our ITS markup related to terms only share some commonalities? Example: The DITA "term" element allows more than just one attribute with additional information? Do we suggest to a. move stuff from ITS into host vocabulary <dita:term its:dir="ltr">PlateBroiler</dita:term> b. move stuff from host vocabulary into ITS <its:term dita:platform="CoolOS">PlateBroiler</its:term> Or do we suggest something completely different? 3. What if we have a clash of the information from the namespace of the host vocabulary and the ITS namespace? Example <head> <documentRule its:term="yes" its:termSelector="//dita:term"> </head> <body> <p>The highly visible <dita:term dita:translate="no">PlateBroiler</term> ... </body> 4. What if the host vocabulary and ITS differ with regard to one of the following: 4.1 content model (for example PCDATA vs. mixed) 4.2 data type (for example NMTOKEN vs. CDATA)
Received on Wednesday, 22 February 2006 15:49:45 UTC