RE: Namespaces bindings on options/vars/params - node-set results

Hi all,

I was just wondering about this again and realized that nobody has
commented on this (old) email of mine. Anybody has an opinion?

Regards,
Vojtech

> -----Original Message-----
> From: public-xml-processing-model-wg-request@w3.org
[mailto:public-xml-
> processing-model-wg-request@w3.org] On Behalf Of Toman_Vojtech@emc.com
> Sent: Monday, April 26, 2010 1:55 PM
> To: public-xml-processing-model-wg@w3.org
> Subject: Namespaces bindings on options/vars/params - node-set results
> 
> Hi all,
> 
> Item 2 in the first numbered list in section 5.7.5 (Namespaces on
> variables, options, and parameters) says:
> 
> "If the select attribute was used to specify the value and it
evaluated
> to a node-set, then the in-scope namespaces from the first node in the
> selected node-set (or, if it's not an element, its parent) are used."
> 
> I was trying to write a test case for this requirement, but I realized
> that I don't understand what the above sentence actually means - that
> is, in the context of XProc V1, where the types of options/variables
and
> parameters are strings (or xs:untypedAtomic). Is this sentence some
kind
> of a leftover that should have been removed, or does it mean that
> *before* a node-set result of an XPath expression is converted to a
> string, the namespace bindings from the first node in the node-set are
> used? If so, could somebody provide an example that would show why
this
> is needed/useful?
> 
> Regards,
> Vojtech
> 
> 
> --
> Vojtech Toman
> Principal Software Engineer
> EMC Corporation
> toman_vojtech@emc.com
> http://developer.emc.com/xmltech
>

Received on Thursday, 1 July 2010 13:57:59 UTC