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

 


Help: OASIS Mailing Lists Help | MarkMail Help

entity-resolution-comment message

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


Subject: Re: [entity-resolution-comment] Some queries on the XML Catalogs spec


> >Is the system identifier input to the resolver the system identifier
> >as it appears in the document, or the result of absolutizing that?
> >Presumably the latter, but it doesn't seem to say that in section 7.1.

> It should be the former, though I understand some processors such as
> SAX make this difficult.  But I believe it should definitely be the former.  
> Otherwise, how could you make an entry that worked, for example, for:

>   <!DOCTYPE book SYSTEM "docbook.dtd">

I had assumed that you would always use a public identifier in the case
of "well-known" doctypes, but I don't have much experience of actually
using catalogs!

The thing that worries me about using the relative URI is the
possibility of "URI-capture".  There must be a million (ok, a
thousand) people who have made up their own DTDs called "book.dtd" or
"address.dtd".

> Personally, I'd think it would be fine to treat the XML catalog as
> well-formed XML and then do any error checking you wish--including
> validating it against a built-in DTD.

When I looked at the DTD the thing that struck me was that you will
often need to apply it just to get the defaulted (fixed) namespace
declaration on the root element.  Or do people usually put it in
explicitly?

-- Richard



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