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

Re: XPointer crisis

• To: xml-dev@l...
• Subject: Re: XPointer crisis
• From: Joe English <jenglish@f...>
• Date: Sat, 02 Feb 2002 09:50:11 -0800
• In-reply-to: <004f01c1abd8$565b8a90$7f0386d9@gate>
• References: <004f01c1abd8$565b8a90$7f0386d9@gate> <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...>

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.

Or it could use the target document's namespace context.
That is, the QNames in the XPointer must be lexically identical
to the QNames in the target document.  (With this scheme an XPointer 
processor could ignore namespace issues altogether.)


--Joe English

  jenglish@f...

• Follow-Ups:
  • RE: XPointer crisis
    • From: "Evan Lenz" <elenz@x...>

• References:
  • Re: XPointer crisis
    • From: "Christian Nentwich" <c.nentwich@c...>
  • 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...>

• Prev by Date: RE: What am I overlooking...?
• Next by Date: "Smart ASCII" -> XML for authoring?
• Previous by thread: Re: XPointer crisis
• Next by thread: RE: XPointer crisis
• Index(es):
  • Date
  • Thread