[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: ANN: xpath1() scheme for XPointer

• To: "Simon St.Laurent" <simonstl@s...>
• Subject: Re: ANN: xpath1() scheme for XPointer
• From: Uche Ogbuji <uche.ogbuji@f...>
• Date: Sat, 26 Oct 2002 17:21:49 -0600
• Cc: xml-dev@l...
• In-reply-to: Message from "Simon St.Laurent" <simonstl@s...> of "Sat, 26 Oct 2002 12:39:34 EDT." <4.2.0.58.20021026123659.01ed9890@p...>
• Sender: uche.ogbuji@f...

> At 10:11 AM 10/26/2002 -0600, Uche Ogbuji wrote:
> >Maybe your idea will work for the XInclude part, though I think it's 
> >likely to
> >be messy either way.  However wording that says "xpath() processors must
> >report an error if they encounter either an unresolved entity" is not really
> >meaningful.  You rightly couch your draft mostly by reference to XPath, and
> >XPath has no concept of an XML entity (besides the sliver in
> >unparsed-entity-uri().  I think it's not really meaningful, then to say that
> >an XPath processor could encounter an unresolved entity.
> 
> It's not meaningful to the XPath processor itself, but it could plausibly 
> be triggered by an unparsed entity report from the parser feeding the XPath 
> processor.
> 
> Plausible doesn't seem good enough in this case, so I'm leaning toward a 
> simple warning in the document that XPath resolution may return varying 
> results depending on the parser used to feed the XPath processor.

If I had a vote, I'd vote for this.  Fiats on lower-level ambiguities would 
only tend to smirch the neatness of your spec.


> I could 
> alternately specify that entity resolution must be performed before the 
> XPath processor, but that feels like my higher-level spec is reaching down 
> a few levels into the murk.

Precisely.


-- 
Uche Ogbuji                                    Fourthought, Inc.
http://uche.ogbuji.net    http://4Suite.org    http://fourthought.com
Python&XML column: 2. Introducing PyXML - http://www.xml.com/pub/a/2002/09/25/p
y.html
The Past, Present and Future of Web Services 1 - http://www.webservices.org/ind
ex.php/article/articleview/663/1/24/
The Past, Present and Future of Web Services 2 - 'http://www.webservices.org/in
dex.php/article/articleview/679/1/24/
Serenity through markup - http://adtmag.com/article.asp?id=6807
Tip: Using generators for XML processing - http://www-106.ibm.com/developerwork
s/xml/library/x-tipgenr.html

• References:
  • Re: ANN: xpath1() scheme for XPointer
    • From: "Simon St.Laurent" <simonstl@s...>

• Prev by Date: Re: XInclude: security risk 1
• Next by Date: Re: Are XML's Good Ideas hidden? (was Re: Re: What are Sc...
• Previous by thread: Re: ANN: xpath1() scheme for XPointer
• Next by thread: RE: ANN: xpath1() scheme for XPointer
• Index(es):
  • Date
  • Thread