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] Impact of ICG Adoption on CCRIM SC (Was: [regrep]UN/CEFACT-ICG adopts freebXML Registry)

Sorry for later reply. 

We already looked the work of the Registry CC-Review Sub Committee and we have bought some good ideas from it, like multiple identifiers for example.
But we have not understood your entire document. 
For example our feel about Basic UML model of CC and BIE serialisation that you propose can't really be used to store correctly CC and BIE. 
If you take an ACC instance, it has a lot of properties. These properties could be ASCC or BCC after the BCC are associated with DT ecc... how do you think to take all the information in your serialisation ?
I suppose that each BCC property that you have in your ACC has to be an implicit link to another 'object' and not the simply name of it.

Another point, we don't understand is the mapping of specific Core Components terms model. Why you put CCT, supplementary component restriction, Supplementary Component and associations in this table ?

Ivan Bedini  

-----Message d'origine-----
De : Duane Nickull [mailto:dnickull@adobe.com] 
Envoyé : mercredi 22 septembre 2004 19:17
Cc : regrep@lists.oasis-open.org
Objet : Re: [regrep] Impact of ICG Adoption on CCRIM SC (Was: [regrep]UN/CEFACT-ICG adopts freebXML Registry)


Please take a look at the work of the Registry CC-Review Sub Committee.  
We have planned to give this work to CEFACT to advance this.


(need OASIS username and password to get in)

Duane Nickull


>Hi to all,
>We've worked with UN/CEFACT ICG to redact the UN/CEFACT Repository 
>Strategy and at the meeting we have presented our Registry prototype.
>This prototype allows users to store and retrieve French BIEs in an 
>ebXML RR for EDIFRANCE and it represents a major input for the 
>UN/CEFACT Repository Solution.
>This project gave us experience on your questions. So we'll try now to 
>share our experience.
>First of all we have to concentrate on UN/CEFACT's prototype real needs.
>Our suggestions are:
>-	Compliance with CCTS is the first fundamental point. 
>We have to define the ebRIM components whose maps with Core Components 
>(ACC, BCC, ASCC, DT, CCT) and all their attributes.
>For example what will be in ebRIM the respective CCTS Unique 
>Identifier, version, Dictionary Entry Name... and of course their 
>syntax ? Will be the ASCC an ebRIM association, the ACC the ebRIM 
>extrinsicObject or other... ?
>-	The goal of the registry is to manage the submission,
>modification, validation, versioning, search and retrieve etc... of 
>stored components defined by UN/CEFACT.
>-	Manage Workflow procedures between the UN/CEFACT groups (TBG,
>ATG & ICG) for Business Specification and Technology Solution 
>transformation publication (ebXMLRR Notification ?)
>RepXML prototype gives us a good vision about drawbacks and problems 
>for this purpose.
>Best regards
>R&D Engineer
>France Telecom R&D/BIZZ/PMX
>To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_workgroup.php.

Senior Standards Strategist - Adobe Systems, Inc. - http://www.adobe.com Vice Chair - UN/CEFACT Bureau Plenary - http://www.unece.org/cefact/ Chair - OASIS eb SOA TC - http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ebsoa

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