Code Management Project
other
| Submitted date | Last Update Date | Version | Project Proposal Status | Project Page |
|---|---|---|---|---|
|
Draft
|
Project Purpose
Codes are an essential component of any Machine-To-Machine information flow. Codes have been developed over time to facilitate the flow of compressed, standardized values that can be easily validated for correctness to ensure consistent semantics. Many international, national and sectoral agencies create and maintain code lists relevant to their area. If required to be used within an information flow, these code lists will be stored in their own environment and referred to as external code lists. The project’s purpose is define the procedures and methodologies for code list creation, management and maintenance. The resulting rules and guidelines will primarily be mandated for all UN/CEFACT deliverables but also applicable to external organisations.Project Scope
The project will define the procedures, rules and methodologies for the following identified issues. Existing rules, such as those defined in the Core Components Technical Specification, CCTS, should be taken into account and if applicable be respected. The project should take into account any UN/CEFACT deliverable that apply codes. The primary target audience is UN/CEFACT Experts developing deliverables using coded representations but guidance to end users should be added when appropriate. 1. Version compatibility The ability to use the latest possible version of a code list in association with any version of a message, i.e. decoupling the versioning of code lists from the business message versions 2. Extending code lists Evaluate if permanent extensions are possible and desirable 3. Restricting code lists Provide rules and methodology for restricting code lists for use within specific context. Users of the UN/CEFACT libraries may identify any subset they wish from a specific code list for their own community requirements. 4. Code list validation rules Provide rules and methodology for how to validate instance documents against an XML Schema or UN/EDIFACT message type in respect to code lists 5. Temporary codes Provide rules and methodology for the inclusion of temporary codes that will be replaced by a permanent code at the next UN/CEFACT standardised release. 6. Externally maintained code lists Define rules and procedures for referencing code lists maintained by organisations external to UN/CEFACT, e.g. ISO, ICC, W3C.Project Deliverables
The deliverables from the project will be: a) A Technical Specification which describes how to manage codes and code lists. b) Updates to existing Technical Specifications, if rules and/or guidelines in the new Technical Specification proposed in point a) contradicts existing rules/guidelines The resulting Technical Specification will be applied for new development. Updates of existing code lists will have to be evaluated on a case-by-case basis.Exit Criteria
a) The Code Management Technical Specification approved by the Bureau b) New version of existing Technical Specifications approved by the Bureau, if applicable c) Procedures for code management approved by the BureauProject Team Membership and Required Functional Expertise
The project team is open to UN/CEFACT Experts with broad knowledge and experience in the area of code list management and related activities as well as in modelling techniques. Experts are expected to contribute to the work based solely on their expertise and to comply with the UN/CEFACT Code of Conduct and Intellectual Property Rights policy.Head of Delegation Support
India Japan Morocco Spain SwedenGeographical Focus
The geographic focus of the project is global.Initial Contributions
Resource Requirements
Project Leadership
Milestones
DELIVERABLE NAME | Project Inception | Expected Completion Date | Requirements Gathering | Expected Completion Date | Draft Development | Expected Completion Date | Public Review | Expected Completion Date | Project Exit | Expected Completion Date | Publication | Expected Completion Date | Maintenance | Expected Completion Date |
| YES | YES | YES | YES | YES | YES | YES | ||||||||
| YES | YES | YES | YES | YES | YES | YES | ||||||||
| YES | YES | YES | YES | YES | YES | YES |
Project Proposal Files