NDR 3.0 Second Public Review Released
UN/CEFACT has recently published an updated public review version of its XML Naming and Design Rules (NDR) V3 specification. The NDR is an important specification to SAP and its customers and partners. SAP uses the NDR specification in conjunction with other UN/CEFACT standards such as CCTS (link to CCTS) to define its Global Data Types which are at the heart of its business objects and service definitions.
UN/CEFACT originally released the first public review version in August 2008. Under the UN/CEFACT Open Development Process (ODP), public review is the next to final phase of its standardization process. In this phase, the standards development team has sufficiently discussed, analyzed, and decided on the proper technical solution to the point that external feedback is solicited to ensure the technical accuracy and user community acceptance of the concepts of the proposed standard. Feedback is accepted from any potential user and all feedback is reviewed and considered by the team prior to finalization of the specification.
This new public review version incorporates comments received from a wide variety of submitters. The principal change from the public review version is a refinement of the expression of data type value domains. This refinement incorporates new concepts related to the use of context methodology and breaks new ground for using code lists and identifier schemes to define value domains as alternatives to simple primitive types such as decimal, integer, binary object, string and the like. Data types will now be allowed to have different value domains defined at both design and run time using context values to identify the specific value domain to be used in a given situation.
Interested parties are encouraged to download, review, and submit comments to the NDR Version 3.0 Implementation Second Public Review. For additional information related to UN/CEFACT, the UN/CEFACT standards, or SAP’s use of these standards, you can contact either myself (firstname.lastname@example.org) or Gunther Stuhec (email@example.com).