W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > July 2006

RE: Inputs and outputs

From: Grosso, Paul <pgrosso@ptc.com>
Date: Thu, 20 Jul 2006 19:40:36 -0400
Message-ID: <CF83BAA719FD2C439D25CBB1C9D1D3020412A85B@HQ-MAIL4.ptcnet.ptc.com>
To: <public-xml-processing-model-wg@w3.org>

I'm not at all eager to complicate things with an xpath-like
axis defined by xproc.

But I don't see that slashes are necessarily confused with
xpath.  Way before xpath ever existed, slashes had been 
commonly used to designate hierarchy in file paths and
URIs.  I just think of the use of a slash here as another
case of hierarchical paths like in URIs.

paul

> -----Original Message-----
> From: public-xml-processing-model-wg-request@w3.org 
> [mailto:public-xml-processing-model-wg-request@w3.org] On 
> Behalf Of Rui Lopes
> Sent: Thursday, 2006 July 20 18:17
> To: public-xml-processing-model-wg@w3.org
> Subject: Re: Inputs and outputs
> 
> Alex Milowski wrote:
> > Actually, we could make it like XPath by adding our own axes for
> > steps, inputs, outputs and whatever else we want:
> 
> > 
> > This might be become import to components who want 
> parameters to refer
> > to particular input or output ports.
> 
> I really like the concept (specially axes), but my concern on 
> confusing 
> this XPath-lookalike language with real XPath remains. Or even worse, 
> binding parameters to particular output port fragments (if I 
> understood 
> correctly what you've meant), would mix non-XPath with real 
> XPath, e.g.:
> 
> my-xslt/output::result/rdf:RDF/rdf:Description/@rdf:about
> 
> Or did I misunderstand that "parameters to refer..." bit ?
> 
> 
> Cheers,
> Rui
> 
Received on Friday, 21 July 2006 00:18:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:21:48 GMT