[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 adoptsfreebXML Registry)
ICG (Information Content Management Group) is responsible for the libraries of both metadata and actual data, and for technical harmonization and auditing. ATG (Applied Technologies Group) is responsible for the creation and maintenance of document structures deployed by specific technologies or standards, such as UN/EDIFACT, UN Layout Key, UN e-docs or XML.ATG2 is the sub-group of ATG that is responsible for harmonization of core components, dealing with data maintenance requests (DMRs), etc. They would be providing the content for the libraries to ICG. Hope this helps. Regards, Sally -----Original Message----- From: Farrukh Najmi [mailto:Farrukh.Najmi@Sun.COM] Sent: Friday, September 17, 2004 2:54 PM To: firstname.lastname@example.org Subject: Re: [regrep] Impact of ICG Adoption on CCRIM SC (Was: [regrep] UN/CEFACT-ICG adoptsfreebXML Registry) Chiusano Joseph wrote: >Farrukh, > >Is the UN/CEFACT ATG2 group involved in this? Or is this separate from >their work? > > My understanding is that ICG view both TMG and ATG as key stakeholders in the ICG architecture. The typical workflow will be handing off content to ICG to manage within their architecture and ATG will be downstream from ICG in that they will be using the repository to create additional metadata and content. ICG sits in the middle of this workflow as best as I understand. For more detailed questions please contact Mike Conroy "michael.conroy" <email@example.com> who chairs ICG. Thanks. -- Regards, Farrukh >Joe > >Farrukh Najmi wrote: > > >>One important thing I did not mention is that UN/CEFACT is now doing two >>things as part of their ICG Architecture: >> >>1. Define a normative expression syntax in XML for Core Components >> >>2. Define a normative mapping from CCTS Information Model to ebXML >>Registry Information Model >> >>These were 2 important specification that SHOULD have been done by CCTS >>but since they were not we chartered CCRIM SC to do these. >>Now that UN/CEFACT teams are committed to doing this work I propose that >>the CCTS team donate their current work-in-progress as input (along with >>any recommendations) to the UN/CEFACT ICG and CCTS teams and recharter >>to become the liaison and consultant to those teams as they define and >>finalize these two tasks. >> >>Duane and others colleagues. What do you think of this idea? >> >>-- >>Regards, >>Farrukh >> >>Farrukh Najmi wrote: >> >> >> >>>The UN/CEFACT Information Content Management Group (ICG) has officially >>>adopted the ebXML Registry standard as the center >>>piece of their new Information Content Management Architecture. >>> >>>The architecture will be implemented as a federation of autonomous ebXML >>>Registries operated by various UN/CEFACT members countries and >>>organization. They are also envisioning a top level UN/CEFACT ebXML >>>Registry as the leader of the registry federation. The UN registry >>>federation will store Core Component artifacts as well as many other UN >>>defined artifacts. >>> >>>At ICG invitation I attended a two day meeting Thursday and Friday. >>>On Thursday I presented ebXML Registry standard to them and discussed >>>their requirements and how ebXML Registry standard met those >>>requirements. On Friday we developed the blueprint for their >>>ebXML Registry based architecture which was then presented to the broader >>>participant of the UN/CEFACT conference. >>> >>>It was good to see David Webber in the audience who contributed to >>>the lively discussion. The presentation was well received. >>> >>>I will send link to the UN/CEFACT Information Content Management >>>Architecture slides as soon as it gets posted on their web site: >>> >>> http://www.disa.org/cefact-groups/icg/ >>> >>>All in all I am overwhelmed by the success of this meeting and hope that >>>this momentum in the adoption of the ebXML Registry standard continues >>>to escalate. >>> >>>We as a team should feel very proud of the success of our standard. >>> >>> >>> >>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. >> >> > > > 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.