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

 


Help: OASIS Mailing Lists Help | MarkMail Help

regrep message

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


Subject: Re: [regrep] Interoperability of Content?


Farrukh,

I think we're finding something here that we probably 
need to address.

Content falls under one of two categories for this
purpose - 

1) generalized content, and 
2) specific content pertinant to ebusiness architecture
    components.

It's this second bucket that I think we cannot just duck.
Some examples - UDDI have defined bindings for
certain catalogue entries.  Just think of the chaos
if people could define their own...

So I think we have to recognise that we have a 
set of these - CPA, CPP, BPSS, CCTS, Discovery
and so forth, where each is supported by a major 
spec' - where there is content and process
and behaviours to be supported and delivered.

So I believe it is OK - in the Registry spec' to 
have an addendum with a "How to" guide 
for these - with use cases - or at a minimum
URLs pointing to where this information is
located.   And we cannot just punt this - we
need to make sure the Registry provides
the functionality.

Now the good news is that this is not a
vast list - we are limiting ourselves to a
very select list here.

Thanks, DW.
=========================================
Message text written by "Chiusano Joseph"
> 
<Excerpt>
If we are talking about interoperability of CC then that is 
out-of-scope for this TC IMO.
</Excerpt>
<



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


Powered by eList eXpress LLC