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] | [List Home]

Subject: Re: [regrep] ebXML Registry: Deviations from CCTS


I think we're talking about the same thing but missing a piece here.

What I'm talking about works with or without a CAM processor
available as a service of the registry.

The CAM team is defining the XSD for storing in XML the
semantic content of an element or attribute.  That is the XML
you will get back if you query the registry for a specific
content reference ID.

Now if you use a simple Registry association link - a
bi-directional one - from that XML instance stored in
regisrty to a node in the RIM of a CCTS - then if you
query the CCTS RIM object - you can optionally get back
all the XML from those semantic entries - or vice versa -
you can find the CCTS model for an XML definition.

That's why I'm not seeing we need to change anything on
the CCTS front, we just need to add the means to store
XML semantics in a consistent format and simply link
the two.

Similarly for a BIE you can store a CAM template
sub-assembly (as XML) right now today - and then
link it to the CCTS BIE - so anyone wanting that - will just
put that include instruction for the CAM processor into their
transaction definition template.

Simple use of XML instances to carry the required semantic
detail.   The Registry SCM can define what that semantic
structure looks like - and the CAM draft provides a useful
start point.   What I especially like is that we are keeping
the semantic XML very simple in this way - and using
the Registry RIM to do the hardwork for us.

Thanks, DW.

----- Original Message ----- 
From: "Duane Nickull" <dnickull@adobe.com>
To: "David RR Webber" <david@drrw.info>
Cc: "Chiusano Joseph" <chiusano_joseph@bah.com>; "CCRev"
<regrep-cc-review@lists.oasis-open.org>; "Alan Stitzer"
<Alan.Stitzer@marsh.com>; "Mary Kay Blantz" <blantz@attglobal.net>;
Sent: Wednesday, January 07, 2004 3:27 PM
Subject: Re: [regrep] ebXML Registry: Deviations from CCTS

> David RR Webber wrote:
> >...There is already a provision in the <ContentReference>
> >section of CAM so you can reference across to the
> >CCTS model component and hence the RIM...
> >
> David:
> The issue will  be how the RIM instance data is serialized into some
> format and tranferred to the registry client (including any registry
> aware CAM processor).  Right now, RSS does not adequetely facilitate
> this if CC's are going to be captured in RIM isntance data rather than
> as Registry Objects.  If someone were to integrate the CAM processor
> with a registry, they need to know exactly what they will get back when
> querying the registry.
> Joseph is well on the way to defining it.  He has started by identifying
> he RIM definciencies that need to be bridged first, then we can move
> onto examining the RSS returns to see how they may be adapted to meet
> the needs of CAM and others.
> It am glad to see that CAm is ready.  That means that CCRIM work must be
> finished and the problem should be solved.
> Duane
> -- 
> Senior Standards Strategist
> Adobe Systems, Inc.
> http://www.adobe.com

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