Added by gunther.stuhec, last edited by gunther.stuhec on Apr 04, 2007

Labels

 
(None)

1. Objectives

1.1   Purpose

Context, as a key driver to precisely determine business meaning and intent of information definition and exchange, requires a formal structure and methodology.  Although context has been identified as a key component of the UN/CEFACT standard, a formal mechanism for defining and using context has not been in place. With an increasing maturity of a number of standards (CCTS, CCMA, UMM, etc.) that all have strong needs to define and use context, now is the time to form a project to tackle this problem.
 The purpose of this project is to develop a methodology and technical specification for developing, registering, and using context drivers as part and for the application of a number of UN/CEFACT standard artefacts, such as Business Data Type, Business Information Entity, Business Message, Business Area, Business Process Models etc.  This project will start from the current context mechanism described in the Core Components Technical Specification (CCTS).
 
This project will be a joint effort between TMG, TBG, and ICG.  It will be, however, led and managed by TMG with participation from TBG and ICG members, as context methodology will impact a number of stanards artefacts being developed under UN/CEFACT. 

1.2 Scope

The specification will provide a methodology for assigning context to business information using a number of defined context drivers by advancing the context driver mechanism of the CCTS. The specification will take into account the ongoing work within TMG (UMM collaboration models), ICG (Registry Implementation Specification) and within TBG (Common Business Process Catalogue).  The methodology will also include a recommendation for the code lists that can be used for the defined context drivers and a proposal of how to maintain these code lists.
 The proposed steps to develop the draft specification are as follows:

  1. Review and evaluate current UN/CEFACT standards that are related to and potentially impacted by the context methodology;
  2. Develop a context framework meta-model and a context methodology for the implementation of the meta-model;
  3. For each area (category) of the context meta-model, develop a taxonomy that can be used to populate the eventual context driver value instance.  Existing taxonomies shall be used.
  4. Collaborate with TBG in developing business process related context model and examples;
  5. Collaborate with ICG in registry meta-model and implementation;
  6. Develop first complete draft for review; 

2. Key Deliverables

The document to be delivered is:  TMG Context Methodology Specification
           

3. Functional Expertise of Membership

Membership is open to experts who have broad knowledge in the areas of Business Process, Business Process Modelling, Data Modelling, Core Components, Taxonomy, and Business Functions and Domain modelling.  Members will be drawn from UN/CEFACT Work Groups, ISO TC 154, other ISO TCs, and from industry groups.  In addition, Heads of Delegations may invite experts from their constituency to participate in the work. Experts are expected to contribute to the work based solely on their expertise and to comply with the UN/CEFACT Code of Ethics.
 

4. Geographical Focus

The focus is global in nature.
 

5. Delegated Responsibilities

The project team is empowered in accordance with agreed procedures to:

  1. Establish sub-groups and supporting teams as required;
  2. Cooperate and establish liaisons with other groups and organizations as required.

Statement of resource requirements: Participants in the project shall provide resources for their own participation. The existence and functioning of the project team shall not require any additional resources from the UNECE secretariat, other than the installation of an appropriate list serve.
 

6. Contributions Submitted

UN/CEFACT Core Components Work Group will contribute:

  • Core Components Technical Specification v2.01
  • Approved changes to CCTS v2.01
  • UN/CEFACT Business Process Work Group will contribute:
  • UMM Base Module 1.0 (First Working Draft)
  • UMM Foundation Module 1.0 (First Working Draft)
  • UMM Meta-model - Revision 12
  • UMM User Guide for Rev12 Other contributions include:
  • TBG14 Common Business Process Catalogue Technical Specification v1.0
  • ICG Registry Specification
  • ICG Registry Procedure Guideline