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

 


Help: OASIS Mailing Lists Help | MarkMail Help

entity-resolution message

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


Subject: Re: XML Catalogs Working Draft 12 Jun 2001



On 19/06/2001 22:38:26 Daniel Veillard wrote:

>    - 5.1. The xcatalog File
>      I really dislike this mechanism. It breaks the XML processing model
>      in general, we should not add this step when loading an XML resource.
>      It's hazardeous (like reusing a directory where another project was
>      loaded before), and transform the relatively rigorous XML parsing
>      process by adding a step allowing random failure. For me it's really
>      not an option (i.e. I won't implement it).
>      If the author wants to signal the presence of a catalog use a
>      PI (like the xml-stylesheet one) at least it's clearly flagged
>      by the author and more flexible.

Just a short comment that PIs in a file are no less hazardous than reusing a directory, because the usual rules of cut-and-paste will tell you that the PI was probably not explicitly inserted by the author for the file you are looking at.

     Cheers,
          Tony.
========
Anthony B. Coates
Leader of XML Architecture & Design
Chief Technology Office
Reuters Plc, London.
tony.coates@reuters.com
========

-----------------------------------------------------------------
        Visit our Internet site at http://www.reuters.com

Any views expressed in this message are those of  the  individual
sender,  except  where  the sender specifically states them to be
the views of Reuters Ltd.


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


Powered by eList eXpress LLC