• To: <xml-dev@l...>
• Subject: Re: XPointer architecture (Re: XPointer and XML Schema)
• From: "Rick Jelliffe" <ricko@a...>
• Date: Fri, 19 Jul 2002 20:00:40 +1000
• Cc: <www-xml-linking-comments@w...>
• References: <f5bit3e8gsj.fsf@c...><f5badoq8gg0.fsf@c...><009101c22e1b$ca26a480$4bc8a8c0@A...><1026996266.23053.81.camel@ibook> <020501c22ed0$8d4a5790$4bc8a8c0@A...> <1027070291.24801.31.camel@ibook>

From: "Eric van der Vlist" <vdv@d...>
 
> On Fri, 2002-07-19 at 05:01, Rick Jelliffe wrote:

> Yes and no, the architecture in which HTTP based XPointer is used is 3+
> tiers and I have focussed up to now in the interactions between the user
> agent and the server only.

But I am simply not talking about XPointer.  The term "fragment" has a use
apart from the fragment identifier of URIs: e.g. fragment interchange.

I am trying to think through some issues that relate to when a chunk
of a document has been requested by any mechanism that uses
server-side XQuery or XPath2s and the query/path uses TAI augmentations.

Cheers
Rick Jelliffe

• Follow-Ups:
  • Re: XPointer architecture (Re: XPointer and XMLSchema)
    • From: Eric van der Vlist <vdv@d...>

• References:
  • Re: XPointer and XML Schema
    • From: ht@c... (Henry S. Thompson)
  • Re: XPointer and XML Schema
    • From: "Rick Jelliffe" <ricko@a...>
  • Re: XPointer and XML Schema
    • From: Eric van der Vlist <vdv@d...>
  • Re: XPointer and XML Schema
    • From: "Rick Jelliffe" <ricko@a...>
  • XPointer architecture (Re: XPointer and XML Schema)
    • From: Eric van der Vlist <vdv@d...>

• Prev by Date: RE: XSLT and URI processing
• Next by Date: Re: XPointer architecture (Re: XPointer and XMLSchema)
• Previous by thread: XPointer architecture (Re: XPointer and XML Schema)
• Next by thread: Re: XPointer architecture (Re: XPointer and XMLSchema)
• Index(es):
  • Date
  • Thread