Re: XML Catalog issue 23

[dcpleland@ftnetwork.com]

Hi John;

I agree that there should be a permissive/optional inclusion of processing for non XML catalogs.  I have a need for processing both SGML and XML files, and reckon that there will be SGML catalogs involved.

This was well stated in the discussion from another (Paul?) and since I concurred, left it there.  But would now like to document it, for future reference, if needed.

Regards,
David Leland
************************************************************
jcowan@reutershealth.com wrote on 3/19/01 7:27:11 PM
************************************************************
# Should we assert that delegate and nextCatalog entries must
# point to other instances of XML Catalogs? Is it an error for
# delegate and nextCatalog to point to resources that are not XML
# Catalogs?

I think we need to define this in terms of the behavior of XML
Catalog processors, namely that they MAY allow XML Catalogs to
point to non-XML-Catalogs.

If so, this is really part of the "processing model" issue 15.
I propose that we consider it part of 15.

-- 
There is / one art             || John Cowan <jcowan@reutershealth.com>
no more / no less              || http://www.reutershealth.com
to do / all things             || http://www.ccil.org/~cowan
with art- / lessness           \\ -- Piet Hein


------------------------------------------------------------------
To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to: entity-resolution-request@lists.oasis-open.org


___________________________________________________________________________________________________
Get your free e-mail account with *unlimited* storage at  http://www.ftnetwork.com

Visit the web site of the Financial Times at  http://www.ft.com