• To: ste@w... (Stefano Debenedetti)
• Subject: Re: how is xpointer supposed to work?
• From: John Cowan <jcowan@r...>
• Date: Thu, 7 Nov 2002 10:30:56 -0500 (EST)
• Cc: xml-dev@l...
• In-reply-to: <11420208.1036678363210.JavaMail.SYSTEM@webaccess> from "Stefano Debenedetti" at Nov 07, 2002 04:19:50 PM

Stefano Debenedetti scripsit:
> 
> hello list, 
> 
> it is very unclear to me how is XPointer information to be received by an XPointer-enabled server, and if such a server is even supposed to exist, as it seems to me that existing browsers keep any info after the crosshatch char # for after-resource-retrieval processing and don't send that part of the URL to the server, and from what I gaher that happens to be conformant to RFC 2396, is that true?

That is standards-conformant behavior.  XPointers can be used as fragment
identifiers in URI references, in which case they are client-side, but may
also be useable in other ways which haven't been thought up yet.

-- 
With techies, I've generally found              John Cowan
If your arguments lose the first round          http://www.reutershealth.com
    Make it rhyme, make it scan                 http://www.ccil.org/~cowan
    Then you generally can                      jcowan@r...
Make the same stupid point seem profound!           --Jonathan Robie

• References:
  • how is xpointer supposed to work?
    • From: Stefano Debenedetti <ste@w...>

• Prev by Date: how is xpointer supposed to work?
• Next by Date: Re: Java API for Accessing XML Schema
• Previous by thread: how is xpointer supposed to work?
• Next by thread: Re: how is xpointer supposed to work?
• Index(es):
  • Date
  • Thread