- From: Yves Savourel <ysavourel@enlaso.com>
- Date: Mon, 8 Oct 2012 08:35:12 -0600
- To: <public-multilingualweb-lt@w3.org>
Hi Jirka, all,
I believe the idValue attribute is not the same as the classic pointers we have in other places.
The definition says: "It contains an XPath expression which constructs a string corresponding to the identifier of the node to which this rule applies[ should be located]."
(Note there is a copy/paste error: the words "should be located" at the end should be deleted. I'll fix that).
So the value returned by the XPath expression is not a node where to find the Id value, but the ID value itself. This allows to construct IDs like shown in example 63 (http://www.w3.org/International/multilingualweb/lt/drafts/its20/examples/xml/EX-idvalue-element-2.xml)
-yves
-----Original Message-----
From: Jirka Kosek [mailto:jirka@kosek.cz]
Sent: Monday, October 08, 2012 8:16 AM
To: public-multilingualweb-lt@w3.org
Subject: idValue issues
Hi,
I have just noticed two inconsistencies in definition of idValueRule
(http://www.w3.org/TR/its20/#idvalue):
- idValue attribute is defined as containing XPath expression. It should contain "relative selector" in order to support new queryLanguage
- also should be this attribute named idValuePointer - on all other rule elements attributes pointing to elements containg actual value are suffixed with "Pointer"
Thoughts?
Jirka
--
------------------------------------------------------------------
Jirka Kosek e-mail: jirka@kosek.cz http://xmlguru.cz
------------------------------------------------------------------
Professional XML consulting and training services
DocBook customization, custom XSLT/XSL-FO document processing
------------------------------------------------------------------
OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member
------------------------------------------------------------------
Received on Monday, 8 October 2012 14:35:43 UTC