1 / 9

Towards an International Standard Core Component Registry

MoU/MG/03 N 149 rev 2 Status: For Review Date: May 2003 Source: Howard Mason. Towards an International Standard Core Component Registry. Proposal from the IEC/ISO/ITU/UNECE MoU on e-Business Standards. The Current Situation. Multiple organisations developing data definitions

shyla
Download Presentation

Towards an International Standard Core Component Registry

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. MoU/MG/03 N 149 rev 2 Status: For Review Date: May 2003 Source: Howard Mason Towards an International Standard Core Component Registry Proposal from the IEC/ISO/ITU/UNECE MoU on e-Business Standards

  2. The Current Situation • Multiple organisations developing data definitions • Multiple modelling approaches • Overlapping and conflicting definitions • Legacy implementations • Some bilateral cooperation • UN/CEFACT focus through TBG17 group • UN Trade Data Element Directory recognised by regulatory authorities worldwide

  3. The MoU/MG Vision • Common definition for information across an enterprise - supporting useful subsets for implementation • Available from a single point of contact • Content may be distributed across multiple, consistently defined registries/repositories • Freely accessible to business and regulatory authorities • Supporting harmonisation and reusability across standards bodies • Neutral definition of data elements, which can be mapped into different standards

  4. Key Elements • Separate but coordinated responsibility for development • Each group may have some core components under its unique responsibility • Some components will require harmonisation • Controlled language essential for interoperability • ISO/IEC 11179 as enabler for naming convention • Harmonisation of terminology for classification schemes • Support for multi-lingual application • Recognition of UNTrade Data Element Directory • Support for the modelling of fundamental relationships between elements

  5. Recommendations • MoU/MG recognises the ongoing data element harmonisation work in CEFACT TBG17 • MoU/MG encourages its members to accept the offer of UN/CEFACT to host a workshop in September/October 2003 on core components, designed to promote • Involvement of all relevant groups • Mutual understanding of • Modelling approaches • Scopes • Areas for potential harmonisation • Common ground/problem areas • Development of an approach for harmonisation

  6. Workshop Objectives • Develop support for harmonisation • Understand CEFACT work on core components • Explain Core Components Technical Specification • Identify how external organisations can participate - particularly with established models and modelling methods • Consider • Process for registration of “Core Components” • Definition of federated repository structure

  7. Key groups • ISO TC 154 (TDED, BSR) • OASIS UBL • CEFACT (TBG17, TMG-CCWG) • ISO/IEC JTC 1/ SC 32 (ISO/IEC 11179) • ISO TC 37 registration project • ISO/TC 68 • ISO/TC 184 (SC4 and SC5) • ISO/TC 204 • ISO/TC 215 • EAN • OAG • SWIFT

  8. Action for each group • Each group is requested to • attend the planned workshop and • subsequently introduce the relevant Resolution or decision in its own forum, which will declare support for the goal of the common definition and commit to continuing to work towards that goal under the MoU/MG

  9. Action for MoU/MG • Review outcome of workshop at 24/25 Nov 2003 meeting • Identify issues and actions required for progress on • Harmonisation • Registration • Repository

More Related