Re: LC-1565 Use of escape characters in XPath expressions

Dear diselecters,

Ok here is some examples in Delivery Context: XPath Access Functions 1.0

dcn:cssmq-width("px", 500) > 400
dcn:cssmq-width("cm") < 2.54
dcn:cssmq-height("px") > 200
dcn:cssmq-height("cm", 2.54)
dcn:cssmq-device-width("px") < 640
dcn:cssmq-grid()

I don't see any example using AVT's -- you're propably talking about
example in 7.1 Using Attribute Value Templates in Content Selection
for Device Independence (DISelect) 1.0.

Moreover, if you want to be consistent, you should say that those
values have to be put into attributes around APOS ' -- if not it won't
be well formed.

That's another point for which I think in Delivery Context: XPath
Access Functions 1.0, the XPath expression SHOULD NOT be escaped at
all

Best regards,

Mohamed




On 1/31/07, Rhys Lewis <Rhys.Lewis@volantis.com> wrote:
> Dear Mohammed,
>
> It's an interesting approach. Unfortunately, our examples themselves rely on features of the host language, and hence we need to say something about it. For example, we use AVTs to update the class attribute in one example.
>
> Since our current expectation is that XML languages will be the ones that implement DISelect, it seems most appropriate to document the syntax that requires escaping.
>
> However, a comment about the fact that escaping would not be required in languages that are not XML based could also be helpful. We could certainly add that.
>
> As to other W3C documents that describe XPath expressions in XML with examples, the XSLT specification does explicitly use escaping.
>
> Very best wishes
> Rhys
>
>
> -----Original Message-----
> From: Innovimax SARL [mailto:innovimax@gmail.com]
> Sent: 31 January 2007 09:45
> To: Rhys.Lewis@volantis.com
> Cc: public-diselect-editors@w3.org
> Subject: Re: LC-1565 Use of escape characters in XPath expressions
>
> Dear Rhys,
>
> Ok let's try to argument
>
> XPath 1.0 has never been targeted to be used ONLY inside XML dialects, and it has been a good idea, since XQuery IS NOT an XML dialect
>
> I think that for keeping broader audience for specification, unnecessary limitation should be dropped, especially for an extension of XPath
>
> So examples should be given, without escaping
>
> I imagine a simple note at the bottom of the specification, which should mention, that "for using it inside an XML dialect such that XHTML, it should be escaped" could be sufficient
>
> Regards
>
> Mohamed
>
> On 1/31/07, Rhys Lewis <Rhys.Lewis@volantis.com> wrote:
> >
> >
> > Dear Mohamed,
> >
> > Thanks for the clarification about your comment.
> >
> > Our examples are indeed XML, because we assume the host language is
> > XHTML Version 2. This is stated in the section on Document
> > Conventions. The text
> > reads:
> >
> > "In the examples, the default namespace, with no prefix, is used to
> > indicate the host language within which the content selection markup is being used.
> > The examples assume that the host language is XHTML Version 2 [XHTML 2]."
> >
> > Since XHTML Version 2 is an XML-based language, we have applied the
> > escaping for XPath.
> >
> > I hope that this explanation means that you will be able to accept the
> > disposition of this particular comment.
> >
> > Very best wishes
> >
> > Rhys Lewis
>
>
> --
> Innovimax SARL
> Consulting, Training & XML Development
> 9, impasse des Orteaux
> 75020 Paris
> Tel : +33 8 72 475787
> Fax : +33 1 4356 1746
> http://www.innovimax.fr
> RCS Paris 488.018.631
> SARL au capital de 10.000 €
>


-- 
Innovimax SARL
Consulting, Training & XML Development
9, impasse des Orteaux
75020 Paris
Tel : +33 8 72 475787
Fax : +33 1 4356 1746
http://www.innovimax.fr
RCS Paris 488.018.631
SARL au capital de 10.000 €

Received on Saturday, 3 February 2007 12:45:43 UTC