Status of Collaboration with UN/CEFACT

1. Status of Collaboration with UN/CEFACT Tim McGrath UBL Plenary Stockholm Sept 24 2007

2. UN/CEFACT/OASIS Cooperation Agreement • Paragraph 2c: "The parties will appoint representatives to jointly develop and recommend an OASIS-UNECE-UN/CEFACT project alignment and coordination plan, addressing areas of common technical interest, including: i) Harmonization of core data components, UBL, other business data entity libraries etc. ii) Naming and Design Rules iii) Mechanisms for business process specification iv) Adoption and promotion efforts for the ebXML specifications v) Identity, addressing and e-signature functionalities with potential for interoperability across UNeDocs, Universal Postal Union practices, and other trade facilitation ID and e-signature instances.”

3. UBL XCBL X12 EDIFACT UBL’s Continuity UN/CEFACT ebXML CBL XML EDI

4. The Players • Any agreements are between OASIS and UN/CEFACT. • Not the UBL Technical Committee • The UBL TC advises OASIS and UN/CEFACT as to how the collaboration is undertaken. • The UBL TC does not “own” UBL, OASIS does. • The UBL TC is an committee of volunteers • Like UN/CEFACT • Not like RosettaNet, OAG, Swift, etc.

5. Collaboration Agreement • UN/CEFACT recognizes UBL 2 as appropriate first-generation XML documents for eBusiness. • Future UN/CEFACT deliverables constitute the upgrade path for UBL. • Maintenance of UBL 2 remains with OASIS. • In the expectation that UN/CEFACT will produce its own integrated set of XML schemas within a period of three years, OASIS will produce no further major versions of UBL past UBL 2. • OASIS will grant UN/CEFACT a perpetual, irrevocable license to create derivative works based on UBL. Agreed in April 2006.

6. 1. Recognition “UN/CEFACT recognizes UBL 2 as appropriate first-generation XML documents for eBusiness.” • Until UN/CEFACT offer an alternative then UN/CEFACT agree UBL is a worthy solution. • A question of timing… • Need solution today = use UBL • Need solution sometime in the future = await UN/CEFACT deliverables • incorporating the UBL upgrade path • UBL is the useable stepping stone towards a unified UN/CEFACT standard. • “Future UN/CEFACT deliverables constitute the upgrade path for UBL” • It is in everyone’s interest to make this happen.

7. 2. Maintenanceof UBL “In the expectation that UN/CEFACT will produce its own integrated set of XML schemas within a period of three years, OASIS will produce no further major versions of UBL past UBL 2.” • What is meant by “major version”? • What is meant by an “integrated set of XML Schemas”?

8. UBL Major Versions • A major version is one that breaks backward compatibility with a previous version. • In UBL, compatibility means validation by XML schema. • If a document created with a previous version is not valid according to the new version’s XML schema then the new version is a major release. • For example, version 3.0, 4.0, 5.0, etc.. • If a document created with a previous version is valid according to the new version’s XML schema then the new version is a minor release. • For example, version 2.1,2.2,2.3, etc..

9. UBL Minor Versions “Maintenance of UBL 2 remains with OASIS” • Maintenance covers minor version releases: • New document types. • Extensions to existing documents. • Extensions to existing ABIEs. • New Data Types. • Non-normative edits: • Errata • Documentation enhancements • This includes changes to Dictionary Entry Names • The UBL TC is currently working on these for UBL 2.1 • Targeted for released in 2008

10. 3. Deliverables “In the expectation that UN/CEFACT will produce its own integrated set of XML schemas within a period of three years…” • A set of documents that cover the Buy-Ship-Pay process supported by UBL • i.e. a legitimate alternative to UBL • Functionally equivalent and stable • The current UN/CEFACT candidate releases of XML schemas… • Not an integrated set. • Cross Industry Invoice, e-Tendering documents, etc • Single process design, not integrated. • Version synchronization • All documents must be at the same release level. • Needs to be completed before April 2009.

11. 4. Intellectual Property “OASIS will grant UN/CEFACT a perpetual, irrevocable license to create derivative works based on UBL.” • OASIS are not transferring IPR. • UBL will continue to exist as an OASIS Technical Specification. • The UBL Technical Committee may continue to exist as an OASIS Technical Committee. • Maintenance and support.

12. This means… • If you want a solution today then use UBL. • Adopting UBL is not contravening UN/CEFACT’s strategic direction. • UBL is a stepping stone towards a unified UN/CEFACT standard. • You can use UBL for today and for tomorrow.

13. Convergence Status

14. CEFACT Plenary (Shareholders) Bureau (Board of Directors) Forum Forum Management Group (Board of Management) TMG (CCTS, UMM) TBG (1-19) ICG Permanent Groups (Corporate Divisions) ATG (1-2)

15. Organizational Structures OASIS Membership (Shareholders) CEFACT Plenary (Shareholders) Bureau (Board of Directors) Board (Board of Directors) Forum Forum Management Group (Board of Management) Technical Committees (Corporate Divisions) Permanent Groups (Corporate Divisions)

16. Joint Statement from Previous Forum • At the UN/CEFACT Forum in Dublin (26-30 March 2007), work continued to foster integration on a common set of electronic business document standards based on the input and experience of UBL. This involved constructive meetings with working groups focused on harmonization, supply chain, e-procurement, e-government and technical methodologies. • A cross-domain project has been approved to further review public sector e-procurement requirements, providing a path for input from an envisaged workshop on "Implementation of electronic public procurement in Europe" (CEN/ISSS WS/ePPE). This will include profiles developed in the context of implementations of UBL in Northern Europe and Spain. • We see the first candidate release of UN/CEFACT's Cross Industry Invoice schema as an opportunity to further this collaboration

17. Work Areas • The major issues to be resolved in planning for a transition of UBL to UN/CEFACT are: • Library convergence • Domain-specific work items • Schema design (NDRs) • Code Lists • Production Strategies

18. Library convergence

19. Core Component Library • TBG17 interpretation has problems: • Outlined at Dublin Forum meeting. • Next slides • If we change our submission: • They would not be UBL • What would we achieve? • Need a reasoned debate about the technical merits of the different approaches and reach a consensus. • Schedule meeting this week

20. Core Component Library • TBG17 – Harmonization. • UBL and UN/CEFACT are attempting to converge our two efforts into a "best of breed" solution. • Converge the UBL library with the CEFACT library. • UBL has defined requirements for the CEFACT library to support the Business Information Entities of UBL. • Submitted in April. • Reached an impasse: • “technical errors”. • differences in interpretation of CCTS.

21. TBG17 UBL Suggestion Qualifiers for ABIEs Always used Not used Cardinality of BCCs Allows repeating occurrences of certain types of BCC Normalized (except translations of text) How this affects BBIEs Used for number of different BBIEs and also occurrences of each BBIE. BBIEs may be the same or restrict occurrences Qualifiers for Association Property term used for role. Adds role or context to property Special Property Terms Identification. Identifier Identifier. Identifier Keep it simple Context Levels for CCs Less context in UBL Geographical Coordinate. Latitude. Measure and Geographical Coordinate. Longitude. Measure Location Coordinate. Degrees. Measure Generalize CCs where their structure and value domain are the same “ Tax. Jurisdiction. Text Tax Scheme. Address “ Charge. Indicator Indicator. Indicator More context in UBL Party. Details Customer Party. Details Extensions are new ACCs (that include intension ACC) Design Differences

22. UBL TBG17 Truncation of Property Terms Property Term is not the same as the third part of the name. Currency Code. Code Currency. Code Object Class + Property Term gives meaning Representation term (or associated Object Class) only defines the presentation (what it looks like) Object Class + Property Term + Representation Term (or associated Object Class) gives meaning Secondary Representation Terms Name is a legitimate representation term Country. Name Country. Name. Text CCTS Differences

23. Domain-specific work items

24. Supply Chain Documents • “International Supply Chains consist of integrated and coordinated flows of information, goods & payments” • Source: UN/CEFACT International Supply Chain Reference Model • TBG14 – Business Process Modelling • Incorporate UBL process models as part of International Supply Chain Reference Model. • Opportunity for accepting products not developed using UMM

25. eBGT Initiative • electronic Business, Government and Trade • A new support team for the FMG • Bring together end-to-end global core of interoperable standards for buy-ship-pay model in support of e-business, e-government and e-trade • stage one (three months): Stockholm (this week) • launch projects on core deliverables and tools • stage two (six months): focus on priority developments • stage three (three months): triage review of progress • stage four (three months): focus on demos / case studies • stage five (three months): evaluate / formulate next steps

26. Government, Business & Trade?

27. UBL for Government • OIOUBL • subset based on UBL (buy, ship, pay) • NES • subset based on UBL (incorporating OIOUBL) (buy, ship, pay) • CODICE • extension of UBL (EU e-tendering) • CEN/ISSS WS/BII • UBL candidate core components for UN/CCL • NES and CODICE documents based on candidate core components • Interoperable with OIOUBL/NES and CODICE • UN schemas for Government e-procurement (eBGT) • UBL core components incorporated into UN/CCL • customizations of CEN/ISSS documents based on UN/CCL

28. Government • TBG19 • "Further review on current procurement requirements for e-Government" project. • Involves TBG6, TBG1, NES and CODICE. • CEN/ISSS workshop (WS/BII) kicked off May 11th. • Strategic opportunity and a proving ground for CEFACT collaboration. • Potential eBGT deliverable.

29. Government Adoption OIOUBL NES CEN/ISSS CODICE

30. UBL for Business • TBG1 - Supply Chain • Cross Industy Invoice schema at release candidate stage. • Expect approval in Stockholm • Convergence for new set of BRSs covering sourcing to payment incorporated requirements from UBL (for 2008) • Agreed to revisit the approved BRSs (Invoice and Remittance Advice) for UBL input.

31. UBL for Business • TBG6 – Construction • 21 schemas for tendering • Not suitable for EU requirements • CODICE is the UBL based alternative

32. UBL for Trade • TBG3 – International Trade • Joint TBG2 submission to TBG17 • Approved IFTM BRS ? • Starting document modeling • all to be based on IFTM BRS • UBL to collaborate on Status document. • TBG2 – Digital paper • BRS for UN/eDocs approved • Duplicates much of the work of UBL • UN/Layout Key project • needs cooperation with TC154 for UN/TDED

33. Schema design (NDRs)

34. Naming and Design Rules • ATG2 • Developing NDR 3.0 • Dependent on CCTS 3.0 • UBL completed UN/CEFACT/UBL XML Naming and Design Rules Analysis • Submitted to ATG2 on 9th August • 200 rules and UBL Disposition • http://lists.oasis-open.org/archives/ubl/200708/msg00034.html

35. Local vs Global • UBL Statement: • UBL NDR now appreciates the business requirements for the hybrid approach, and we will support its incorporation into the next version of CEFACT NDRs as soon as CEFACT formally adopts it and there is support for it in a released version of CCTS. • ATG2 response: • It is already in the NDRs and supported in CCTS 2.01.

36. “Accepting” ATG2 NDRs • Means we are comfortable with UN/CEFACT adopting the item in question • We don't disagree with it But • This represents no commitment on the part of the UBL TC • because at this stage we have no intention of producing further revisions of the UBL 2 NDR.

37. Customization • ATG2 • Use of xsd:any • ATG2 members all use some type of 'extension' point at the root level • Like UBLExtension • TMG Context Methodology • Work-in-progress

38. Code Lists

39. Code Lists • Information Content Group (ICG) • Maintain CEFACT code lists • Project for UN code list formalization • identified task to "gain understanding of genericode" • ATG2 proposed rule [R33] • “Reusable Code List schema modules MUST be created to convey code list enumerations.” • TBG17 • “What we need is a clear convention how to use ISO 3166 in CCTS uDT and qDT.” • UBL code list approach is based on OASIS Code List Representation TC • TC currently being incorporated. • Uses genericode format for values. • Separates representation from verification.

40. Development Strategies

41. The CEFACT Process TBG3 Transport SC TBG6 UBL Library BRS+RSM Sent to TBG17 Procurement SC BRS+RSM Sent to TBG17 Library BRS+RSM Sent to TBG17 TBG1 Creates RSM TBG1 Creates BRS TBG17 Harmonization Other submission to TBG17 Verified by ICG UBL NDRs Customization Library Schemas ATG2 Generates Schema Next step Usage

42. Deliverables (revisited) • A set of documents that cover the Buy-Ship-Pay process supported by UBL • A legitimate alternative to UBL • The current UN/CEFACT candidate releases of XML schemas… • Cross Industry Invoice, e-Tendering documents, etc • Not an integrated set. • Single process design, not co-ordinated. • Also means version synchronization • All documents at the same release level. • Needs to be completed before April 2009.

43. Different Strategies Order Invoice Catalogue Invoice Despatch Advice Tendering Order Waybill Despatch adv. Despatch adv. Despatch adv. Receipt Advice Parallel development Near-serial development CEFACT UBL

44. Goals for this week • TBG1 • Martin, Peter • TBG3 • Andy,Tim • TBG19 • Adam • TBG17 • Tim, Andy, Martin, Tommy, Kim • ATG2 • Mavis, Mike • ICG/TMG • Ken?