Browse Space
Table of Content
1. Project Name
Conformance/Compliance Definition
Version: 1.0
2. Objectives
2.1. Purpose
The purpose of this project is to provide the global user community a set of guidelines that can be used to provide level of confidence in the alignment of available technical solutions to UN/CEFACT approved artefacts.
There are three planned phases to this project.
- The first phase of the project is to define a set of common terminology that will be used to provide clarity for this project. For example, multiple definitions exist for Compliance and Conformance, but only one set of definitions can be used for this project.
- The second phase of the project includes a review of UN/CEFACT artefacts to classify the important aspects of each artefact and it's relevance to Compliance/Conformance (as defined). The final result of this phase is a matrix that clearly outlines each artefact and is used as the basis of the third phase.
- The third phase of the project is to determine the need for levels of Compliance/Conformance. Each level will be defined and the matrix of artefacts will be tied to these levels for simplicity and clarity. This clarity is for both those interested in attaining a specific level and for the general public to understand what each level means.
2.2. Scope
The scope of the project is to review the current approved, Business Requirements Specification (BRS), Requirement Specification Mapping (RSM), UN/CEFACT Modeling Methodology (UMM),), Core Component Technical Specification (CCTS) family, and XML Naming and Design Rules (NDR) specification, determine which:
- rules are applicable to UN/CEFACT
- rules are applicable to external organizations working within UN/CEFACT
- rules are applicable to external organizations submitting contributions to UN/CEFACT, and
- rules are applicable to external organizations working independently.
As a result of this analysis, the final product will provide a clear and unambiguous definition of Compliance/Conformance at each of these levels for each of the specifications.
The definition of a Certification Program is outside the scope of this project and is not endorsed by UN/CEFACT. Private sector compliance and certification organizations who might be interested in providing such certification services are free to do so. The efforts of private organizations will not be officially sanctioned by UN/CEFACT nor will they carry any implied endorsement.
3. Deliverables
This project should result in a series of Rules and Guidelines for Compliance/Conformance. The resulting document will answer questions such as:
Stage 1:
- What is meant by Compliance/Conformance at the Message / Methodology levels
- What are levels of Compliance/Conformance
Stage 1 will be reviewed and approved by the FMG before Stage 2 commences.
Stage 2:
- Work with the PGs to define levels of and conformance for their specifications.
- The PGs will be involved to define what artefacts require a Conformance Specification; these artefacts may include: CCTS, XML NDR, UMM, CCMA, BRS, RSM, Registry Specification, etc.
4. Functional Expertise of Membership
Membership is open to experts with broad knowledge in the area of UN/CEFACT CCTS, UN/CEFACT XML Naming and Design Rules, Unified Modeling Methodology (UMM) and Unified Modeling Language (UML) as well as the functions of UN/CEFACT and its groups, and external standards development organizations. Experts in the area of Certification, Compliance and Conformance are necessary to ensure that current experience is leveraged correctly. In addition Heads of Delegations may invite technical 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.
5. Geographical Focus
The geographic focus of the project is global
6. Initial Contributions
The following contributions are submitted as part of this proposal. It is understood that these contributions are only for consideration by the project team and that other participants may submit additional contributions in order to ensure that as much information as possible is obtained from those with expertise and a material interest in the project.
The following have expressed an interest in making such contributions:
- 1 — UN/CEFACT Modelling Methodology – by UN/CEFACT - TMG
- 2 — UN/CEFACT XML Naming and Design Rules – by UN/CEFACT - ATG
- 3 — UN/CEFACT Core Components Technical Specification – by UN/CEFACT - TMG
- 4 — UN/CEFACT Core Components Message Assembly – by UN/CEFACT - TMG
- 5 — UN/CEFACT Unified Context Methodology – by UN/CEFACT - TMG
- 6 — Conformance Testing and Certification Model for W3C Specifications (W3C Working Draft 2 January 2002) – by W3C
- No. — Contribution – by Group or Organization
7. Project Management
7.1. Team
| Project Chair |  Andrew Hearn |
|---|---|
| Editor | Mark Crawford |
7.2. Milestones
Estimated Open Development Process (ODP) milestone dates:
| ODP Step | ODP Name | Estimated Completion Date | Comment |
|---|---|---|---|
| 1 | Project Proposal | 29.03.2007 | Completed |
| 2 | Requirements List | 01.07.2007 | |
| 3 | 1st Working Draft | 09.07.2007 | |
| 4 | Internal Review | 13.08.2007 | |
| 5 | Public Review | 01.10.2007 | |
| 6 | Implementation Verification | 15.10.2007 | |
| 7 | Final Release | 01.11.2007 |
8. Statement of Resource Requirements
Participants in the project shall provide resources for their own participation. The continued existence and functioning of the project team shall not require any additional resources from the UN/ECE secretariat other than:
- Establishing and maintaining the project team's public Web site pages with appropriate links, document download facilities, and items of interest;
- Establishing and maintaining the project team's public and private list servers.
Table of Content
Relevant Documents
Comment Logs
Change Requests
Contributions
Presentation and Upload
 | Upload Information In order to categorize correctly, please use the following prefix in the filenames:
|
Action Items
| Number | Action Item | Category | Start Date | Due Date | Responsible Person | Comment | Status |
|---|
Decisions
| Number | Date | Decision Name | Description | Impact | Comment |
|---|
Agendas and Meetings
Next Meeting
| Title | COD - Initial Meeting of new Project |
|---|---|
| Topic | Arrange next steps |
| Date | 26.04.2007 |
| Start Time | 10:00 – Timezone: EST |
| End Time | 11:00 – Timezone: EST |
| Join Meeting | Meeting ID: 972885  |
...
Invitations and Agenda
|
Notes
|
Meeting Participation
[edit?]
Active Members
|
Contributions
|
TrackingUnknown macro: {tracking-table}
Unknown macro: {tracking-column}
Unknown macro: {tracking-column}
Unknown macro: {tracking-column}
Unknown macro: {tracking-column} | ||||||||||||||||||||||
COD - Call for Participation
(Techniques and Methodologies Group)
COD - ODP 1 - Actions And Decisions
(Techniques and Methodologies Group)
COD - Project Proposal
(Techniques and Methodologies Group)