Re: idValue issues

On 8.10.2012 16:35, Yves Savourel wrote:

> 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)

Fair enough.

Although for consistency I would like to make this queryLanguage aware.
We might define "selector expression" as an equivalent to "XPath
expression" when queryLanguage is XPath and use it here instead.

   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
------------------------------------------------------------------