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: catalogs and relative URIs [was: minutes from ER TC 20010429]




On 30/04/2001 22:04:19 Paul Grosso wrote:

>This does not really help me--I don't find it clear, and insofar as I
>can make any sense of it, I disagree.  What our spec says about determining
>the catalog (i.e., the list of catalog entry files--that is what a catalog
>is) is:

I was left a bit confused myself.  Actually, the question of paths and relative
URIs and such reminds me, in a sense, of what is happening in the various
financial XML consortia I'm involved in, because version 1.0 starts out being
about data, then version 2.0 suddenly needs to add a standard process to make it
workable.  I'd like to skip the version 1.0 problem here and suggest that we
need to explicitly describe the process for dealing with paths and relative
URIs.  You may well already feel the same way anyway, but if not, let's discuss
it.

     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