[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: first proposal
>Please be sure you all understand the semantics of the TR9401 catalog >entry type before you go here. Note that its semantics imply (logically) >"appending" the referenced catalog *at the end* of the current catalog. >This is not the usual behavior of "import", so I think we're asking for >problems using such a term. If you want to match the semantics, perhaps >"nextcatalog" is best. I agree with Paul on this one. I see it more as catalogue chaining than import, so some suggestion of a next/fallback/failover catalogue makes more sense to me that overloading "import" with yet another slightly incompatible semantic. Cheers, Tony. PS I'm here at XML 2000, so if anyone else is, come say hello (& visit the Reuters stand :-) ). ======== 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