W3C home > Mailing lists > Public > public-multilingualweb-lt@w3.org > October 2012

RE: idValue issues

From: Shaun McCance <shaunm@gnome.org>
Date: Fri, 12 Oct 2012 18:02:25 -0400
To: Yves Savourel <ysavourel@enlaso.com>
Cc: public-multilingualweb-lt@w3.org
Message-ID: <1350079345.2163.117.camel@recto>
So although all the *Pointer attributes are defined to be relative
location paths, I think we just end up getting a string value from
the pointed-to nodes for everything except targetPointer. In fact,
I could imagine wanting to do something like this with params:

<its:rules>
<!--
For in-house translators, instead use:
$baseurl = http://internal.example.com/docs/
-->
<its:param name="baseurl">http://example.com/docs/</its:param>
<its:locNoteRule selector="//*[@noteref]"
  locNoteRefPointer="concat($baseurl, @noteref)"/>
</its:rules>
<p noteref="notes.html#foo">Foo</p>

That example doesn't conform, but it seems legitimate.

--
Shaun

On Mon, 2012-10-08 at 08:35 -0600, Yves Savourel wrote:
> 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
Received on Friday, 12 October 2012 22:02:49 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:31:55 UTC