PowerPoint Template
Download
Report
Transcript PowerPoint Template
32N2126
Tutorial for SC 32/WG 1 e-Business Standards
Prepared for:
SC 32 2011 Kona Plenary Meeting
Wenfeng Sun, Convenor
ISO/IEC JTC1 SC32 WG1 (eBusiness)
[email protected]
16 May 2011
Contents
Brief introduction to WG1 e-Business
standards
Status updates
Technical progress
Brief Introduction to WG1 e-Business Standards
ISO/IEC 14662 Information technology – Open-edi reference model
ISO/IEC 15944 Information technology - Business Operational View:
• Part 1: Business Operational aspects of Open-edi for implementation
• Part 2: Registration of scenarios and their components as business objects
• Part 3: Open-edi description techniques (OeDT)
• Part 4: Business transactional scenarios - Accounting and economic ontology
• Part 5: Identification and referencing of requirements of jurisdictional domains as
sources external constraints
• Part 6: Technical Introduction of eBusiness modelling
• Part 7: eBusiness vocabulary
• Part 8: Identification of privacy requirements as external constraints on business
transactions
• Part 9: Open-edi traceability framework
• Part 10: Coded domains.
Brief Introduction to WG1 e-Business Standards
Open-edi reference model
B
U
S
I
N
E
S
S
T
R
A
N
S
A
C
T
I
O
N
S
Open-edi Reference Model
Business Operational View
Comply wit h
Business aspects
of
business transactions
Covered by
BOV RELATED
STANDARDS
Viewed as
Int er-relat ed
Functional Service View
Information technology
aspects of
Business transactions
Comply wit h
Covered by
FSV RELATED
STANDARDS
Brief Introduction to WG1 e-Business Standards
What is Open-edi?
Characteristics of Open-edi
Actions based on predefined rules;
Commitment of the parties involved;
Communications among parties are automated
Parties control and maintain their states;
Parties act autonomously;
Multiple simultaneous transactions can be supported.
Brief Introduction to WG1 e-Business Standards
Key components of a business transaction
Person(always capitalized “P”): entity, a natural or legal person,
recognized by law as having legal rights and duties, able to make
commitment(s), assume and fulfil resulting obligation(s), and able
to be held accountable for its action(s).
Process: series of actions or events taking place in a defined
manner leading to the accomplishment of an expected result.
Data (Business transaction): representation of recorded
information that are being prepared in a form suitable for use in a
computer sytem.
Brief Introduction to WG1 e-Business Standards
Template for open-edi scenarios
IT-Interface
Scope
Decision
Tag ID Code
Code
(1)
1000
(2)
Linguistic Human-Interface Equivalents
Name
(English)
(3)
Business goal of business transaction- No external constraints)
1010
Business goal of business transaction includes external constraints )
1040
1041
1042
Persons (no external constraint)
Persons: Individual <-> Individual
Persons: Individual <-> Organization)
……
3080
3085
3090
ROLE ACTIONS
ROLE INTERNAL FUNCTION
ROLE DEMANDS ON OPEN-EDI SUPPORT INFRASTRUCTURE
4000
4010
4020
4030
INFORMATION BUNDLE ATTRIBUTES
IB Identifier
IB Name(s)
IB Purpose
Spare
Name
(French)
Name
(Other)
(4)
(5)
(6)
Brief Introduction to WG1 e-Business Standards
Relations between WG1 standards
Reference model
14662 Concept system
15944-7
Knowledge for modeling
TR 15944-6
Open-edi :
eCommerce, eLearning, eHealth, etc.
BOV
FSV
e-Things that has the 6 characteristics
Goal of open-edi standardization:
Register of scenarios and
scenario components
Constraints
15944-5
15944-1
Ontology View:
Collabration space
15944-4
On privacy
15944-8
Registration 15944-2
FDT
15944-3
Key component:
15944-10
coded domain
On traceability
15944-9
Status updates
ISO/IEC 14662:2010
ISO/IEC 15944-1:2002
ISO/IEC 15944-2:2006
ISO/IEC 15944-3
ISO/IEC 15944-4:2007
ISO/IEC 15944-5:2008
ISO/IEC 15944-6:2009
ISO/IEC 15944-7:2009
ISO/IEC 15944-8
ISO/IEC 15944-9
ISO/IEC 15944-10
IS
IS
IS
CD
IS
IS
TR
IS
FDIS
CD
FCD
E/F
2nd Edition FDIS
Periodical Review
Technical progress
FCD 15944-10 Information technologyBusiness operational view: coded domains
Definition:
domain for which
(1) the boundaries are defined and explicitly stated as a rulebase of a coded
domain Source Authority; and,
(2) each entity which qualifies as a member of that domain is identified
through the assignment of a unique ID code in accordance with the
applicable Registration Schema of that Source Authority
Examples:
“codes representation of X”
Better qualified
As an Open-edi Scenario component
Technical progress
FCD 15944-10 Information technologyBusiness operational view: coded domains
Key characteristics for coded domain
Support commitment exchange
IT-enablement
Technical progress
FCD 15944-10 Information technologyBusiness operational view: coded domains
Support of culture adaptability, cross domain
usage
Multilingual presentation of semantics
Any type of presentation of information resources
Technical progress
FCD 15944-10 Information technologyBusiness operational view: coded domains
Registry of coded domains equals to Registry of
codes, and equals to Registry of semantics
specification of codes that meets the requirements of
all coding standards
codes as the pivot for semantics
semantics have qualifiers to support commitment
exchange (legal requirements)
Technical progress
FCD 15944-10 Information technologyBusiness operational view: coded domains
coding rules
Semantic relationship among objects
Rules shall be IT-enabled
Technical progress
FCD 15944-10 Information technologyBusiness operational view: coded domains
Clauses:
Principles and rules
Identification and description of coded domains
from BOV
Rules for rulebase
Rules for IDs
Rules for HIEs
Registration
IT-enablement
[email protected]