Get documents about "Thailand Interoperability Framework
Document Sample
Semantic Interoperability with
Core Components Technical Specification
Thailand e-Government Interoperability
Framework Series
1
Lack of Semantic Interoperability
2
Within Application: High Integration Effort
3
Between Applications: High Integration Effort
4
Sample XML Schemas
5
Problems in Data Interoperability
6
Principle of Reusable Information Building Block
7
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
8
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.
9
Core Components Overview
10
ISO 11179 Core Component Construct
Dictionary Entry Name
BCC
Person. Identification. Identifier
Object Class Term Property Term Representation Term
Conceptual Generic = BCC property
Data Element Data Element
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
11
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.
12
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 the
Object Class Term of
associated ACC
13
BCC: Basic Core Component
A singular business characteristic/property of specific ACC that
can be used in any business context
14
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) that carries essential extra
definition to the content
e.g., Amount. Currency. Code List Version Identifier
15
CCTS Core Data Types
Amount A number of monetary units specified in a currency where the unit of the currency is
explicit or implied
Code A character string (letters, figures or symbols) that for brevity and/or language
independence may be used to represent or replace a definitive value or text of an
Attribute together with relevant supplementary information.
Identifier A character string to identify and distinguish uniquely, one instance of an object in an
identification scheme from all other objects in the same scheme together with
relevant supplementary information.
Indicator A representation of a situation that has exactly two mutually exclusive Boolean values
Measure A numeric value determined by measuring an object along with the specified unit of
measure.
Numeric Numeric information that is assigned or is determined by calculation, counting, or
sequencing. It does not require a unit of quantity or unit of measure.
Quantity A counted number of non-monetary units possibly including fractions.
Text A character string (i.e. a finite set of characters) generally in the form of words of a
language.
Binary Object A set of finite-length sequences of binary objects.
Date Time A particular point in the progression of time together with the relevant supplementary
information.
16
ACC, BCCs and ASCCs???
17
Core Component Library
18
Business Context of Conceptual Core Components
19
Context Categories
Context Category Description Example
Business Process The type of business process as described in UN/CEFACT Ordering
Catalogue of Common Business Processes Delivery
Product Classification Factors influencing semantics that are the result of the Parts
goods or services being exchanged, handled, or paid for, Consumer Goods
etc.
Industry Classification Semantic influences related to the industry or industries of Aerospace
the trading partners Agriculture
Geopolitical The location of the partmers International
Europe
Official Constraints Legal and governmental influences on semantics, e.g., the US Law
legislation that applies EU Law
Business Process Role The actors conducting a particular business process as Buyer
described in UN/CEFACT Catalogue of Common Business Seller
Processes
Supporting Role Semantic influences related to non-partner roles (e.g., Shipping Agent
data required by a third-party shipper in an order
response going from seller to buyer.)
System Capabilities This context category exists to capture the limitations of EAN.UCC System
systems (e.g. an existing back office can only support an SAP
address in a certain form)
20
BIE: Business Information Entities
ACC
ABIE
BCC BBIE
ASCC
ASBIE
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”
21
BDT: Business Data Type
22
Core Components Discovery
1. Determine the scope and boundaries of information to be
exchanged (context)
2. Capture, analyze and model business process using
UN/CEFACT’s Modeling Methodology
3. Investigate what detailed information needs to be exchanged in
the transaction
4. Look in existing registry for BIEs and CCs which fulfill
information requirements
5. Reuse where applicable existing BIEs and CCs
6. Define where necessary new BIEs and CCs according to CCTS
Rules, then submit them for inclusion in the registry
23
Determine the scope and boundaries of
information to be exchanged (context)
*Case Study: Exportation of Frozen Shrimp
24
Capture, analyze and model business process
using UN/CEFACT’s Modeling Methodology
*Case Study: Exportation of Frozen Shrimp
25
Investigate what detailed information needs
to be exchanged in the transaction
1) Commercial Invoice
2) Packing List
3) Export Declaration
4) Declaration Accept
5) Declaration Reject
6) Payment Order
7) Debit Advice
8) Remittance Advice
9) Credit Advice
10) Bank Statement
11) Export License (R. 9)
12) Goods Transition Control List
13) Goods Transition Control List Accept
14) Goods Transition Control List Reject
15) Request for Port Entry (TKT. 308.2)
16) Equipment Interchange Report
17) R. 9 with information on actual
quantity exported
18) Container Loading List
19) Bill of Lading
20) Manifest
21) Outward Container List
*Case Study: Exportation of Frozen Shrimp
26
Look in existing registry for BIEs and CCs
which fulfill information requirements
Reuse where
applicable existing
BIEs and CCs
27
Define where necessary new BIEs and CCs
according to CCTS Rules then submit to registry
Definition Dictionary Entry Name
A code specifying the postcode of
Address. Postcode. Code
this address.
Object Class Term Representation Term
Property Term
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”
28
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
29
Thank you
30
