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] Implementing CCTS in Registry - further thoughts


<Snip>
That should be the job of the 
Domain specific TC (e.g. CCTS).
The CC Review subcommittee should offer its services to act in a 
consulting role to the CCTS team but must not be the owner of such a 
specification.
</Snip>

That sounds like a very interesting model - and I agree very much with
this concept.  The sense that I have gotten from the CCTS folks in the
past is that they are looking to us to define this, and (at least at
that time) did not have any interest in taking it on themselves, even if
we were to act in a consulting role.  How can we overcome that?

- Joe

Farrukh Najmi wrote:
> 
> Chiusano Joseph wrote:
> 
> >[Greetings from Snow-Pummeled Washington D.C.!]
> >
> >It appears to me that we could have 3 separate "specs" (using term
> >loosely) growing out of the CC spec:
> >
> >(1) ebXML Registry Representation of Core Components (and their
> >associated entities)
> >(2) Context/Assembly
> >(3) XML Serialization
> >
> >It also seems that (1) would be done within our TC (the CC Review
> >subcommittee), but (2) and (3) might be done elsewhere (another TC or
> >within another existing TC).
> >
> >Does that sound correct?
> >
> Hi Joe,
> 
> While I support the good work of CCTS 100%, I feel strongly that our TC
> should not be specifying the binding of any Domain specific model (e.g.
> CC) to ebXML Registry representation. That should be the job of the
> Domain specific TC (e.g. CCTS).
> The CC Review subcommittee should offer its services to act in a
> consulting role to the CCTS team but must not be the owner of such a
> specification.
> 
> The simple criteria I would propose for making such decisions is to
> replace CC with Foo where Foo is some domain specific model (e.g. Health
> Level 7, OGC, OAG etc.) and ask the question what would we do in that
> situation.
> 
> Would we have the HL7 or OGC binding to ebXML Registry be owned and
> defined a an ebXML Registry TC subcommittee? I should hope not. So why
> would we need to have an ebXMl Registry TC own / define the mapping for CC?
> 
> --
> Regards,
> Farrukh
> 
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>

Attachment: Chiusano_Joseph.vcf
Description: Card for Joseph Chiusano



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


Powered by eList eXpress LLC