Page Operations
Browse Space
Objectives (from the project proposal)
- To specify the methodology to develop syntax independent business messages from Core Components artifacts in accordance with the UN/CEFACT Modeling Methodology (UMM).
- To define a structure (meta-model) of syntax independent business messages in accordance with the UMM.
Purpose
The purpose of this project is to develop technical specifications for syntax-neutral semantic assembly of business messages, based on the use of both the UN/CEFACT Modeling Methodology (UMM) and the Core Components Technical Specification (CCTS).
Scope
The specification will provide a specific methodology for assembling higher level Business Information Entities for electronic messages in a semantic and reusable order, but messages which are not electronic may eventually be built from this specification. This methodology also includes the definition of templates for similar structuring of all types of business messages. This is one of the key features for high reusability of business messages and getting a common understanding of business messages on a semantic level.
The technical specification will focus on the business section of a message, and will not include any enveloping needed to transmit this information. It will include models as appropriate and will fit into the same architecture as UN/CEFACT Business Process specifications. The business message will be a Business Information Entity (BIE) which is based on an appropriate business message template and no corresponding Aggregate Core Component (ACC) will be required.
Requirements List
| Number | Category | Name | Description | Comment | Contributor |
|---|---|---|---|---|---|
| 1 | General | Need of CCMA | Describe the need for CCMA. In other words, define how CCMA compliant business messages connect/interact/depend with other e-business/ebXML standards including Core Component Technical Specification (CCTS), ebXML Business Process (ebBP), UMM compliant artifacts, and other UN/CEFACT e-business standards. |  TBD | |
| 2 | Methodology | Identify methodology | Identify a methodology for message assembly. | TBD | |
| 3 | Methodology | Identify environment | Identify an environment where message assembly takes place. | TBD | |
| 4 | Methodology | Identify concepts | Identify what are new concepts, and which concepts we reuse from other specs. | TBD | |
| 5 | Methodology | Syntax neutral business message | Define what exactly is a syntax neutral business message. | TBD | |
| 6 | Methodology | Compare with ABIE | Identify how CCMA business message is different from or the same as an Aggregate Business Information Entity (ABIE) and whether an Aggregate Core Component needs to be defined for a business message. | TBD | |
| 7 | Methodology | Message structure properties | Identify whether a message structure defined by the CCMA methodology has properties of its own. | TBD | |
| 8 | Relation to specs | UMM patterns | Identify how CCMA is associated with UMM especially the business transaction patterns (e.g., how do we handle quality of services provided in UMM, how do we integrate action, intention, and transaction). | TBD | |
| 9 | Relation to specs | UCM | Determine the relationship between the CCMA and Unified Context Methodology (UCM). | TBD | |
| 10 | Relation to specs | SBDH integraiton | Identify the role of the Standard Business Document Header (SBDH) and how to integrate it into the message. | TBD | |
| 11 | Relation to specs | Registry naming | Identify naming rules so we can store results in Registry and Repository (i.e., what will be the Dictionary Entry Name (DEN)). | TBD | |
| 12 | Details | Transport requirements | Identify any CCMA level requirements that are necessary to use business messages with a messaging specification such as SOAP or ebXML messaging. | TBD | |
| 13 | Details | Versioning and consistency | How to ensure consistency of data structure of a business message across usages and versions. | TBD | |
| 14 | Details | Context | Define how context relates. | TBD | |
| 15 | Details | Referencing | How to indicate data via references (such as the key/keyref concept). | TBD | |
| 16 | Details | Naming | Identify how results are to be named (e.g., alignment with the UN/CEFACT Naming and Design Rules). | TBD | |
| 17 | Details | Templates | Develop message assembly templates and a common message assembly structure. | TBD | |
| 18 | Details | Syntax derivation guidance | Provide usage guidance/examples that derive syntax specific business messages from syntax neutral business message. | TBD | |
| 19 | Details | Actions and verbs | Define handling of specific actions (verb) as to how they apply to business message in business process transaction (e.g., how to handle empty element). | TBD | |
| 20 | Details | Containers | Define how to use list container (gathering of repetitive information into a container for processing these information more effectively) in the business message assembly. | TBD | |
| 21 | Details | Partial updates | Define a procedure for submitting complete lists or partial lists in a list container, for e.g. updated list of a telephone book can be sent completely, or only the updated line items will be resent. | TBD | |
| 22 | Details | Defaults | Define how to use default container (the main purpose is to shrink down the volume of the message by indicating some default values in the message, e.g., currency code) in the business message assembly. | TBD | |
| 23 | Customization | If and how | How to customize message, if allowed, at the CCMA level. | TBD | |
| 24 | Customization | CCMA vs. Syntax | Determine which aspects of customized message falls into CCMA level or syntax specific level. | TBD |
Table of Content
Relevant Documents
- [CCMA - Requirements - Comment Log]
Comment Logs
There are currently no attachments on this page.
Change Requests
There are currently no attachments on this page.
Contributions
There are currently no attachments on this page.
Presentation and Upload
There are currently no attachments on this page.
 | Upload Information In order to categorize correctly, please use the following prefix in the filenames:
|
Unable to render {include} Couldn't find a page to include called: CCMA - ODP2 - Actions And Decisions
Agendas and Meetings
Next Meeting
No content is labeled with ccma_odp2_agenda
Invitations and AgendaNo content is labeled with ccma_odp2_agenda |
NotesNo content is labeled with ccma_odp2_minutes |
Meeting Participation
[edit?]
Unable to render {include} Couldn't find a page to include called: CCMA - ODP2 - Meeting Participation
Active Members
|
Contributions
|
TrackingUnknown macro: {tracking-table}
Unknown macro: {tracking-column}
Unknown macro: {tracking-column}
Unknown macro: {tracking-column}
Unknown macro: {tracking-column} | ||||||||||||||||||||||||||||||||||||||||||
