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

Re: XPointer crisis

• To: Christian Nentwich <c.nentwich@c...>
• Subject: Re: XPointer crisis
• From: Daniel Veillard <veillard@r...>
• Date: Sat, 2 Feb 2002 07:06:11 -0500
• Cc: Jonathan Robie <jonathan.robie@s...>, "Simon St.Laurent" <simonstl@s...>, "David G. Durand" <david@d...>, xml-dev@l...
• In-reply-to: <004f01c1abd8$565b8a90$7f0386d9@gate>; from c.nentwich@c... on Sat, Feb 02, 2002 at 10:56:56AM -0000
• References: <1012587257.27106.38.camel@l...> <p05100303b8807575e600@[192.168.155.106]> <1012587257.27106.38.camel@l...> <20020201123611.D29819@r...> <5.1.0.14.0.20020201134448.029015c8@157.189.161.214> <20020201144101.E29819@r...> <004f01c1abd8$565b8a90$7f0386d9@gate>
• Reply-to: veillard@r...
• User-agent: Mutt/1.2.5.1i

On Sat, Feb 02, 2002 at 10:56:56AM -0000, Christian Nentwich wrote:
> 
> >   #/root/foo[1]/bar[2]
> >   Just doesn't work as is because it doesn't allow for namespace support
> > and hence out of scope (or you put schemes in to allow binding namespace
> > prefixes to URI, possible but I don't remember anybody suggesting it).
> 
> If it's a standalone XPointer, the application can make an API call to pass
> a namespace context. If it's used as part of XLink, you can define the
> namespaces to be those that are in scope for the link node. Both are
> unambiguous, no need to pollute the XPointer expression. (XPath applications
> also get the namespace prefixes from elsewhere, not from inside the path)

  Except XPointer is expected to be part of URIs and as such MUST
be context independant. The W3C director sent XPointer back to Working Draft
status one year ago due to this problem, not be considered acceptable either.

Daniel

-- 
Daniel Veillard      | Red Hat Network https://rhn.redhat.com/
veillard@r...  | libxml Gnome XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/

• References:
  • Re: XPointer crisis
    • From: "Simon St.Laurent" <simonstl@s...>
  • XPointer crisis
    • From: "David G. Durand" <david@d...>
  • Re: XPointer crisis
    • From: Daniel Veillard <veillard@r...>
  • Re: XPointer crisis
    • From: Jonathan Robie <jonathan.robie@s...>
  • Re: XPointer crisis
    • From: Daniel Veillard <veillard@r...>
  • Re: XPointer crisis
    • From: "Christian Nentwich" <c.nentwich@c...>

• Prev by Date: Re: XPointer crisis
• Next by Date: RE: Co-operating with Architectural Forms
• Previous by thread: Re: XPointer crisis
• Next by thread: Re: XPointer crisis
• Index(es):
  • Date
  • Thread