OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: Parser Behaviour (serious)

[ Lists Home | Date Index | Thread Index ]
  • From: Paul Grosso <pgrosso@arbortext.com>
  • To: xml-dev@xml.org
  • Date: Mon, 03 Apr 2000 11:28:06 -0500

At 14:57 2000 04 02 -0400, Liam R. E. Quin wrote:
>On Sun, 2 Apr 2000, Tim Bray wrote:
>> Another option is
>> you could implement a Public Identifier resolver, which is pretty easy
>> even though there's not yet a standardized interoperable scheme for this.
>Public identfiers don't help here --
><!DOCTYPE boy
>    PUBLIC "anything you like"
>    "http://www.xml.com/doctypes/boy.dtd"
>You are still required to resolve the system identifier, and you can't.

This is not true.  To quote from Section 4.2.2 of XML 1.0:

  In addition to a system identifier, an external identifier
  may include a public identifier. An XML processor attempting to
  retrieve the entity's content may use the public identifier
  to try to generate an alternative URI. If the processor is unable
  to do so, it must use the URI specified in the system literal.

In fact, I think using PUBLIC identifiers with a catalog to map
them (and maybe SYSTEM mapping entries in that catalog) is a good
way to address a major aspect of this problem.


This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS