Lack of Semantic Interoperability

1. Semantic Interoperability withCore Components Technical SpecificationThailand e-Government Interoperability Framework Series

2. Lack of Semantic Interoperability

3. Within Application: High Integration Effort

4. Between Applications: High Integration Effort

5. Sample XML Schemas

6. Problems in Data Interoperability

7. Principle of Reusable Information Building Block

8. CCTS: Core Components Technical Specification • CCTS provides guidelines to identify, define, and name data elements with an aim to mazimize the reuse of business information to support and enhance information interoperability across organizational borders and industries. • Core Components (CC) • Standardized data elements that are used for constructing electronic business documents/messages. • Generic representations of information on UML object classes

9. Core Components and Class Diagram Core Data Types (CDT) defines data type that a BCC may contain. Aggregate Core Component (ACC) represents Object Class. Association Core Component (ASCC) represents a relation between Object Classs. Basic Core Component (BCC) represents simple properties of Object Class.

10. Core Components Overview

11. Dictionary Entry Name Person. Identification. Identifier Object Class Term Property Term Representation Term Generic Data Element Conceptual Data Element ISO 11179 Core Component Construct • Generic data elements are reusable across object classes. • Project. Identification. Identifier • Registration. Identification. Identifier • Route. Identification. Identifier • Service Charge. Identification. Identifier • Business Core Component properties are reusable across ACCs. • Project. Details • Registration. Details • Route. Details • Service Charge. Details BCC = BCC property

12. ACC: Aggregate Core Component • A collection of related pieces of business information that together convey a distinct real-world object with a specific business meaning, independent of any specific business context • DEN = “Object Class Term” + “Details” which is a suffix appended to an object class to reflect that the ACC contains all relevant and generic propoeries of the particular real-world object.

13. ASCC: Association Core Component • A complex property of a parent ACC that associate two ACCs • DEN = “Object Class Term” + “Property Term” + “Representation Term” where Representation Term of an ASCC is theObject Class Term of associated ACC

14. BCC: Basic Core Component • A singular business characteristic/property of specific ACC that can be used in any business context

15. Core Data Types • Smallest piece of business information which defines the nature of the content of the BCC: • Primitive type, e.g., decimal, integer, string, date, binary, etc. • CDT Content Component • e.g., Amount. Content • CDT Supplementary Component(s) thatcarries essential extra definition to the content • e.g., Amount. Currency. Code List Version Identifier

16. CCTS Core Data Types

17. ACC, BCCs and ASCCs???

18. Core Component Library

19. Business Context of Conceptual Core Components

20. Context Categories

21. BIE: Business Information Entities ACC • Qualifier Term (word/words) • Helps define and differentiate a BIE from its associated CC and other BIEs. • Creates controlled vocabolary that has unique semantic within a specific context • Promotes “extension by restriction” ABIE BCC BBIE ASCC ASBIE

22. BDT: Business Data Type

23. Core Components Discovery • Determine the scope and boundaries of information to be exchanged (context) • Capture, analyze and model business processusing UN/CEFACT’s Modeling Methodology • Investigate what detailed information needs to be exchanged in the transaction • Look in existing registry for BIEs and CCs which fulfill information requirements • Reuse where applicable existing BIEs and CCs • Define where necessary new BIEs and CCsaccording to CCTS Rules, then submit them for inclusion in the registry

24. Determine the scope and boundaries of information to be exchanged (context) *Case Study: Exportation of Frozen Shrimp

25. *Case Study: Exportation of Frozen Shrimp Capture, analyze and model business processusing UN/CEFACT’s Modeling Methodology

26. Investigate what detailed information needs to be exchanged in the transaction • Commercial Invoice • Packing List • Export Declaration • Declaration Accept • Declaration Reject • Payment Order • Debit Advice • Remittance Advice • Credit Advice • Bank Statement • Export License (R. 9) • Goods Transition Control List • Goods Transition Control List Accept • Goods Transition Control List Reject • Request for Port Entry (TKT. 308.2) • Equipment Interchange Report • R. 9 with information on actual quantity exported • Container Loading List • Bill of Lading • Manifest • Outward Container List *Case Study: Exportation of Frozen Shrimp

27. Look in existing registry for BIEs and CCs which fulfill information requirements Reuse where applicable existing BIEs and CCs

28. Define where necessary new BIEs and CCsaccording to CCTS Rules then submit to registry Definition Dictionary Entry Name • Start from semantic description • Must include Object Class Term, Property Term, and Representation Term • Can include context-based and qualified information (qualifier) • Be unique • Be stated in singular • Contain only commonly understood abbreviations • Be expressed without embedding definitions of other data elements • Validate DEN by reading from “right to left” A code specifying the postcode of this address. Address. Postcode. Code Object Class Term Representation Term Property Term

29. References • UN/CEFACT Core Components Technical Specification Version 3.0 (ISO 15000-5), April 2007 • UN/CEFACT – Core Components User’s Guide, March 2004 • Stuhec, G., How to Solve Business Standards Dilemma: The Context of Business Exchange, SAP Developer Network, 2005 • Stuhec, G., How to Solve Business Standards Dilemma: CCTS Key Model Concepts, SAP Developer Network, 2006

30. Thank you