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

[Bug 3464] Allowing for xpath expressions to point to term definitions

From: <bugzilla@wiggum.w3.org>
Date: Fri, 14 Jul 2006 19:55:04 +0000
CC:
To: public-i18n-its@w3.org
Message-Id: <E1G1Tke-0000uf-PE@wiggum.w3.org>

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

           Summary: Allowing for xpath expressions to point to term
                    definitions
           Product: ITS
           Version: LastCall
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: ITS tagset
        AssignedTo: fsasaki@w3.org
        ReportedBy: ysavourel@translate.com
         QAContact: public-i18n-its@w3.org


Issue #22 of i18nCore comments:
http://www.w3.org/International/reviews/0606-its/

Section 6.4.2: Please provide a mechanism to point to a term definition if it
doesn't have an associated id? Eg. in a DL list, where the successive DT and DD
elements contain terms and definitions without ids. Surely something like
termInfoPath is needed.

Example 19 shows this scenario quite clearly. Terms are identified, but not
linked to the definitions given in the example.

FS: You could point to term definitions with a termInfoPointer attribute: 
<dl> 
 <dt>...</dt> 
 <dd>...<dd> 
</dl> 

possibly in a different document (see my reply to your comment 50 below): 

<its:termRule selector="//dl" termInfoPointer="following-sibling::dd"/> 

For consistency, I would propose to keep the naming scheme "xxxPointer", and
not "termInfoPath". Also for consistency, where should be a global or local
termInfo attribute (if the ITS group decides to accept this proposal).
Received on Friday, 14 July 2006 20:48:33 UTC

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