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 Catalog issue 3


Paul Grosso wrote:


> I'm a bit concerned about having to make clear just how to handle
> cases where a single delgate entry has, say, assignments to all
> of publicPrefix, systemPrefix and URIPrefix (or whatever they are
> called).

Good point.

> Though I'm sure we could define things so that the attribute
> form is logically equivalent to the separate entry type form, I'd like
> to hear what is wrong with having different entry types such as:
> 
>   delegate-publc or just delegate for public ids
>   delegate-system for system ids
>   delegate-URI for other URIs.
> 
> Given that we have separate entry types for public, system, and URIs,
> I think this would end up being easier to explain and easier for users.

Also a good point.  All right, how about separate elements
delegate, delegate-system, delegate-URI, with a common attribute
named prefix.

-- 
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



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


Powered by eList eXpress LLC