RE: Our Approach (WAS Re: [regrep-cc-review] Kickoff!)

[David RR Webber - XML ebusiness <Gnosis_@compuserve.com>]

Joe,

Ah ha!  Bingo!

See the pages  of the OASIS CAM spec' - especially 
figure 4.1, page 19, and Section 4.4.1 - that already detail the 
registry interfacing support ; -)

We're ready!

We just need to formalize the XML and the access mechanisms
and we are all set to make this all come together.

(I like the simple RESTful URL interface especially BTW 
to "pluck" into the registry).

And 'Yes' - you could store a BIE as part of a CAM template
as you correctly guessed.

Thanks, DW.
===============================================================
Message text written by "Chiusano Joseph"
>It seems to me that once someone defines (2) - whoever that may be -
then Core Component users (both ebXML Registry and non-ebXML Registry)
can have available to them products that assemble schemas from the XML
representations of CCs and BIEs (sounds like CAM). Such a product would
access the XML "wrapper" that surrounds each CC and BIE in its assembly
process using a content-based query mechanism (rather than a
product-based query mechanism). This would allow such a product to
operate on CCs and BIEs regardless of the system in which they are
stored/maintained.

So for ebXML Registry, it seems to me that registry implementations
would need functionality to produce the XML format of CCs and BIEs from
the registry metadata (Nikola, I believe that this is the crux of the
e-mail you sent to the Registry TC several months ago, with the arrows).
From that point on, the assembly product would operate on the CCs and
BIEs in a platform/system-neutral manner.

Thoughts?
<