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


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: Re: DOCBOOK-APPS: RE: XML catalog resolution problems

On Wed, Oct 30, 2002 at 09:28:44AM -0600, Paul Grosso wrote:
> At 12:27 2002 10 30 +0100, Jeanson Mauritz wrote:
> >When trying xsltproc, I found that it accepts and resolves <system>
> >entries for stylesheets in catalog files. As I take it, this is not
> >the correct behaviour.
> You are correct, xsltproc is not in compliance with the XML Catalog spec.
> The XML Catalog spec makes it clear that system entries are for 
> resolving external identifiers (production 75 in XML) and clearly 
> says about URI entries [1]:

  And I have said to the XML Catalog comitee that an URI Reference is
an URI-Reference and that having to distinguish arbitrarilly one done
from a DOCTYPE entry from one done from an xi:include href entry 
doesn't make any sense to me, and that I would not support the distinction
in my software unless getting a meaningful reason to distinguish
  I haven't received any justification yet from the commitee about the
reason to distinguish those exept "they are different", no sorry ...

 I see ZERO reason why the two following URI-Reference made from a 
single XML entity should lead to using different resource for 

<DOCTYPE foo SYSTEM "http://example.com/foo.dtd>
<xi:include href="http://example.com/foo.dtd"; parse="text"/>

  This distinction is extremely confusing, and so far can't be justified
I really don't see why it's there and the intended purpose.


Daniel Veillard      | Red Hat Network https://rhn.redhat.com/
veillard@redhat.com  | libxml GNOME XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC