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

RE: XPointer crisis

• To: "'David G. Durand'" <david@d...>,<xml-dev@l...>
• Subject: RE: XPointer crisis
• From: "Michael Kay" <michael.h.kay@n...>
• Date: Fri, 1 Feb 2002 19:48:39 -0000
• Importance: Normal
• In-reply-to: <p05100303b8807575e600@[192.168.155.106]>
• Reply-to: <michael.h.kay@n...>

> I am writing to urge immediate action related to Xpointer, if you
> care about it.
>
I think the prospect of a simplified XPointer is very attractive. Lots of
people need simple pointers into an element within a document; very few
people need anything of the complexity of the current XPointer spec:
especially ranges.

Apart from anything else, I've always felt that the XLink/XPointer
architecture was far too presentation-oriented. It fails to recognize that
the document as displayed on screen may be only distantly related to the
source XML, which to my mind is the essence of the XML success story. Ranges
don't mean anything unless your document is being displayed more-or-less
as-is.

And to pick up a thread that's gone dormant, I'd like to see the "bare
names" XPointer complemented by an xml:id="aaaa" attribute that provides an
ID attribute independent of any schema or DTD declarations.

Mike Kay

• Follow-Ups:
  • Re: XPointer crisis
    • From: Gavin Thomas Nicol <gtn@r...>
  • RE: XPointer crisis
    • From: Jonathan Robie <jonathan.robie@s...>
  • Re: XPointer crisis
    • From: John Cowan <jcowan@r...>

• References:
  • XPointer crisis
    • From: "David G. Durand" <david@d...>

• Prev by Date: XML Catalog Resolvers 1.1 Released
• 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