Tutorial for SC 32/WG 1 e-Business Standards Prepared for: SC Gyeongju Plenary Meeting Wenfeng Sun, Convenor ISO/IEC JTC1 SC32 WG1 (eBusiness) 27 May N2384

Contents  Brief introduction to WG1 e-Business standards  Status updates  Technical progress

Brief Introduction to WG1 e-Business Standards  ISO/IEC Information technology – Open-edi reference model  ISO/IEC 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 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. Part 11: UMM foundation modelling as

Brief Introduction to WG1 e-Business Standards  Open-edi reference model

 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-InterfaceLinguistic Human-Interface EquivalentsSpare Scope Tag ID Code Decision Code Name (English) Name (French) Name (Other) (1)(2)(3)(4)(5) (6) 1000 Business goal of business transaction- No external constraints ) 1010Business goal of business transaction includes external constraints ) 1040Persons (no external constraint) 1041Persons: Individual Individual 1042Persons: Individual Organization ) 3080ROLE ACTIONS 3085ROLE INTERNAL FUNCTION 3090ROLE DEMANDS ON OPEN-EDI SUPPORT INFRASTRUCTURE 4000INFORMATION BUNDLE ATTRIBUTES 4010IB Identifier 4020IB Name(s) 4030IB Purpose Brief Introduction to WG1 e-Business Standards

 Relations among WG1 standards Brief Introduction to WG1 e-Business Standards Open-edi =Commitment exchange “eThings” that have the 6 Open-edi characteristics Reference model BOV FSV Goal of open-edi standardization: Register of scenarios and scenario components Registration FDT Ontology View: Collabration space Constraints Internal and external On privacy On traceability Concept system Key component: coded domain Knowledge for modeling TR the link Foundation al modelling

Status updates  ISO/IEC 14662:2010 ISE/F 3 rd Edition  ISO/IEC :2002IS2 nd Edition  ISO/IEC :2006IS  ISO/IEC :2007IS  ISO/IEC :2008IS  ISO/IEC :2009TR  ISO/IEC :2009IS  ISO/IEC IS  ISO/IEC CD2  ISO/IEC IS  ISO/IEC WD  ISO/IEC CD

Technical progress  IS Information technology- Business 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  IS Information technology- Business operational view: coded domains  Key characteristics for coded domain  Support commitment exchange  IT-enablement

Technical progress  IS Information technology- Business operational view: coded domains  Support of culture adaptability, cross domain usage  Multilingual presentation of semantics  Any type of presentation of information resources

Technical progress  IS Information technology- Business 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  IS Information technology- Business operational view: coded domains  coding rules  Semantic relationship among objects  Rules shall be IT-enabled

 IS Information technology- Business 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 Technical progress

 CD Information technology- Business operational view: traceability framework  Requirement:  Legal requirements  eBusiness needs to consider these requirement Technical progress

 CD Information technology- Business operational view: traceability framework  Clauses:  Principles and assumptions  Traceability requirements  Generic traceability model  Open-edi collaboration space and traceability  Traceability attributes for Open-edi scenarios Technical progress

 WD Information technology- Business operational view: UMM foundational modolling as Open-edi decriptive technique.  Input from UN/CEFACT UMM. Technical progress

 CD Information technology- Business operational view: traceability framework  Requirments  IT-enablement of business requirements as a whole. Technical progress

 CD Information technology- Business operational view: traceability framework  Clauses  BOV interoperability  FSV interoperability  Linking the BOV to FSV representation and technology  User data interoperability  Choreography interoperability  Transport interoperability  FSV implementation considerations Technical progress