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

Re: XPointer crisis

• Subject: Re: XPointer crisis
• From: heikki@n... (Heikki Toivonen)
• Date: Fri, 01 Feb 2002 12:12:40 -0800
• Cc: xml-dev@l...
• 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...>
• User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2

Daniel Veillard wrote:

>On Fri, Feb 01, 2002 at 02:08:50PM -0500, Jonathan Robie wrote:
>
>>In HTML, most pointers are done with very simple pointers like this:
>>
>>http://somesite.com/html/top.html#section_2
>>
>
>  Whose semantic is hardcoded in a DTD that nearly no application
>ever respected or used. Let's have a look of the alternatives in
>XML:
>
>  #foo
>
>  Hard to rely on it with XML, well last time I suggested on this forum xml:id
>I got a lot of flack back, I won't try again.
>  So either you accept to force validation of document (and hence
>possibly have to fetch and trust remote DTD in your framework) or you
>need other pointing schemes.
>
This isn't as hard as you'd think. You can have non-validating parser 
pay attention to ID type attributes.

In some cases you may author your document so that it contains an 
internal subset specifying the ID type attributes.

Your application may also support some kind of catalog system (a la XML 
Catalog) so that it could load a local DTD file instead of a remote DTD.

Finally your application may have hardcoded support for some document 
types/schemas/namespaces, and may be able to recognize ID attributes 
because of that (take XHTML for example).

Mozilla (which uses Expat) supports all of the above (catalog support is 
hardcoded for a few precanned DTDs at  the moment). This is not a 
perfect solution, but in many cases adequate.

-- 
  Heikki Toivonen

• Follow-Ups:
  • Re: XPointer crisis
    • From: Daniel Veillard <veillard@r...>

• 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...>

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