Specification for Information Exchange (SIX) Language

Transcription

1 Specification for Information Exchange (SIX) Language Mr. Thomas Lee Center for E-Commerce E Infrastructure Development The University of Hong Kong Web Wide Web Consortium One-day Semantic Web Symposium Hong Kong University of Science and Technology 12 April 2005 (Tue)

2 Information interoperability Information interoperability is a key to electronic commerce and logistics activities Heterogeneous systems use different syntaxes to represent data XML as canonical data syntax language Another level of interoperability problem: Different styles to define XML schemas A lot of mapping efforts required SIX as canonical info model language 12 April 2005 W3C One-day Semantic Web Symposium, HKUST 2

3 SIX as Canonical Model Language XML schema Data dictionary SIX model DB schema CSV spec 12 April 2005 W3C One-day Semantic Web Symposium, HKUST 3

4 Reference Technologies ISO Information technology Specification and standardization of data elements Part 2: Classification for data elements ebxml Core Components Technical Specification a methodology for developing a common set of semantic building blocks that represent the general types of business data in use today and provides for the creation of new business vocabularies and restructuring of existing business vocabularies Entity Relationship Model Semantic Object Model (alternative to E-R model for DB schema) Unified Modeling Language Why not directly use UML? 12 April 2005 W3C One-day Semantic Web Symposium, HKUST 4

5 SIX Language A formal schema language to specify semi- structured information models for data exchange Harmonizes and extends mainstream modeling technologies Information models specified by SIX are independent of data representation syntax SIX model schema can be translated to different syntax schemas (e.g. XSD) 12 April 2005 W3C One-day Semantic Web Symposium, HKUST 5

6 Key Concepts Info Entity Object Class Entity vs. Value Domain Entity Relationship Specialization by restriction vs extension Association Document Component Label Package and Library 12 April 2005 W3C One-day Semantic Web Symposium, HKUST 6

7 Value Domain Entity Represents a value space (not lexical space) of a particular data type Lexical space for a Boolean can be T, F, true, false Value space for a Boolean is the meanings of true and false Data types: Binary Boolean DateTime Numeric String URI XML 12 April 2005 W3C One-day Semantic Web Symposium, HKUST 7

8 Value Restrictions Binary Boolean DateTime Default Fixed Default Fixed Default Fixed Enumeration MinInclusive MinExclusive MaxInclusive MaxExclusive Pattern String URI XML Default Fixed Enumeration Length MinLength MaxLength Pattern Default Fixed Enumeration Pattern Default Fixed Schema Schema Numeric Default Fixed Enumeration MinInclusive MinExclusive MaxInclusive MaxExclusive TotalDigits FractionalDigits Restriction expressions are given in the XSD lexical format in SIX Schema 12 April 2005 W3C One-day Semantic Web Symposium, HKUST 8

9 Example 1. <InfoEntity name="languagecode"> 2. <Content datatype="string"> 3. <Restriction type="length"> 4. <Number>2</Number> 5. </Restriction> 6. <Restriction type="enumeration"> 7. <String>EN</String> 8. <String>JA</String> 9. <String>ZH</String> 10. </Restriction> 11. </Content> 12. </InfoEntity> 12 April 2005 W3C One-day Semantic Web Symposium, HKUST 9

10 Object Class Entity Represents a class of objects that share a set of properties Each property has a Multiplicity multiplicitymin (default is 0) multiplicitymax (default is infinity) Entity type References another info entity already defined 12 April 2005 W3C One-day Semantic Web Symposium, HKUST 10

11 Object Class Entity Example 1. <InfoEntity name="text"> 2. <Property name="content Content" entitytype=" ="TextContent" minmultiplicity="0"/> 3. <Property name="language Language" entitytype=" ="LanguageCode" minmultiplicity="0" multiplicitymax="1"/> 4. </InfoEntity InfoEntity> 12 April 2005 W3C One-day Semantic Web Symposium, HKUST 11

12 Specialization of Info Entity An entity can be defined by specializing (or further constraining) another entity Entity B specializes entity A B is a specialization of A and A is the generalization of B E.g. entity Woman specializes entity Human Two ways to specialize By restriction (the restricted entity can always be represented by the generalized entity) By extension (for object class entities only) 12 April 2005 W3C One-day Semantic Web Symposium, HKUST 12

13 Restriction of Value Domain Entity <InfoEntity name="asia_languagecode Asia_LanguageCode" restricts=" ="LanguageCode"> <Content datatype="string"> <Restriction type="enumeration"> <String>JA</String> <String>ZH</String> </Restriction> </Content> </InfoEntity InfoEntity> A new restriction is added 12 April 2005 W3C One-day Semantic Web Symposium, HKUST 13

14 Restriction of Object Class Entity An object class entity B can be defined by restriction of another object class entity A Every property in B is restriction of a property in A with some rules applied If some properties in B do not restrict any property in A according to the rules during specialization, B can only extends A 12 April 2005 W3C One-day Semantic Web Symposium, HKUST 14

15 Restriction of Object Class Entity 12 April 2005 W3C One-day Semantic Web Symposium, HKUST 15

16 Specialization of Object Class Entity (Example) 1. <InfoEntity name="a"> 2. <Property name="x" entitytype="h" multiplicitymin="2" multiplicitymax="8"/> 3. <Property name="y" entitytype="j" multiplicitymin="0" multiplicitymax="3"/> 4. </InfoEntity InfoEntity> 5. <InfoEntity name="b" restricts="a"> 6. <Property name="x1" restricts="x" entitytype="h1" multiplicitymin="3" multiplicitymax="4"/> 7. <Property name="x2" restricts="x" entitytype="h2" multiplicitymin="2" multiplicitymax="3"/> 8. <Property name="y1" restricts="y" entitytype="j1" multiplicitymin="1" multiplicitymax="2"/> 9. </InfoEntity InfoEntity> 12 April 2005 W3C One-day Semantic Web Symposium, HKUST 16

17 Association Between Info Entities Association between two or more entities Each associated entity may be assigned a role An association may contain properties 12 April 2005 W3C One-day Semantic Web Symposium, HKUST 17

18 Association (example) 1. <Association name="assignment"> 2. <InfoEntity entitytype="worker" role="worker" multiplicitymin="1" multiplicitymax="1" /> 3. <InfoEntity entitytype="task" role="task" multiplicitymax="1" multiplicitymax="1" /> 4. <Property name="startdate StartDate" entitytype="date" multiplicitymax="1" /> 5. <Property name="enddate EndDate" entitytype="date" multiplicitymax="1"/> 6. </InfoEntity InfoEntity> 12 April 2005 W3C One-day Semantic Web Symposium, HKUST 18

19 Document A package of info entities for data exchange A collection of components With names and multiplicities A component Info entity or Contains sub-components (with names and multiplicities) Components are not for reuse and cannot be referenced individually outside the document 12 April 2005 W3C One-day Semantic Web Symposium, HKUST 19

20 Example 12 April 2005 W3C One-day Semantic Web Symposium, HKUST 20

21 Example 1. <Document name="purchaseorder PurchaseOrder"> 2. <Component name="header" multiplicitymin="1" multiplicitymax="1"> 3. <Component name="documentdetails DocumentDetails"> 4. <Component name="docid DocID" entitytype=" ="DocumentID" multiplicitymin="1" multiplicitymax="1"/> 5. <Component name="docdatetime"entitytype DocDateTime"entityType=" ="DateTime" multiplicitymin="1" multiplicitymax="1"/> 6. </Component> 7. <Component name="supplierdetails SupplierDetails" entitytype="supplier ="Supplier" multiplicitymin="1" multiplicitymax="1"/> 8. <Component name="customerdetails CustomerDetails" entitytype="customer" multiplicitymin="1" multiplicitymax="1"/> 9. </Component> 10. <Component name="body" multiplicitymin="1" multiplicitymax="1"> 11. <Component name="lineitem LineItem" entitytype=" ="GoodsItem"/> 12. </Component> 13. </Document> 12 April 2005 W3C One-day Semantic Web Symposium, HKUST 21

22 Label An application can attach a set of labels to SIX components E.g. InfoEntity,, Property, Package, Library Programs can be designed to use the labels to generate multiple application-specific data schemas 12 April 2005 W3C One-day Semantic Web Symposium, HKUST 22

23 Example 1. <InfoEntity name="us_person US_Person" " specializes="person"> 2. <Label app= "RDBMS" type="table"> 3. <rdbms:tablename>us_person</ </ccts:tablename> 4. </Label> 5. <Label app="xsd" type="xsdcomplextype XSDComplexType"> 6. <xsd:complextypename>us_person.type</ </xsd:complextypename> 7. </Label> 8. <Property name="name" entitytype=" ="US_PersonName.Text"> 9. <Label app="rdbms" type="xsdcomplextype XSDComplexType"> 10. <rdbms:fieldname>us_personname</ </rdbms:fieldname> 11. </Label> 12. <Label app="xsd" type="xsdelement XSDElement"> 13. <xsd:elementname>personname</ </xsd:elementname> 14. </Label> 15. </Property> <Property name="birthdate BirthDate" entitytype=" ="US_Person.BirthDate"/> 16. <Property name="us_officialaddress US_OfficialAddress entitytype=" ="US_Person.US_Residence.US_Address"/> 17. <Property name="us_residence US_Residence entitytype=" ="US_Person.US_Official.US_Address"/> 18. </InfoEntity InfoEntity> 12 April 2005 W3C One-day Semantic Web Symposium, HKUST 23

24 Library and Package A library is a collection of model components for a particular purpose A library contains packages that classify info entities by function / context A package is assigned a path name Info entities in different packages can be translated to different data sub-schemas schemas Fully qualified reference for an info entity: LibraryName:/Package/Path/Name/InfoEntity 12 April 2005 W3C One-day Semantic Web Symposium, HKUST 24

25 Library and Package (Cont ) UBL:/Common/ /Common/ReusableDataTypes/CCTs/ ReusableDataTypes/CCTs/Amount.Type Library Name Package Name Entity Name UBL /Common/ReusableDataTypes/CCTs ReusableDataTypes/CCTs/ Amount.Type /Common/ReusableDataTypes ReusableDataTypes/Specialized/ 12 April 2005 W3C One-day Semantic Web Symposium, HKUST 25

26 Real World Problems to Solve Canonical enterprise information model XML Schema RDBMS Schema Data dictionary Unified model for different XML modeling methodologies UN/CEFACT Universal Business Language HK Government XML Schema Design Guide Applied in several industry projects 12 April 2005 W3C One-day Semantic Web Symposium, HKUST 26

27 XML Schema Design and Management Guide XML schema modeling methodology for developing e-govt applications Based on ebxml Core Components & UBL approach Standardized Common Schemas person s s name, HKID#,, address, etc. Central Data Registry Already applied in real cases Center for Health Protection Dangerous goods declaration Weather info publishing One of OASIS egovernment best practices 12 April 2005 W3C One-day Semantic Web Symposium, HKUST 27

28 12 April 2005 W3C One-day Semantic Web Symposium, HKUST 28

29 Future Research: Universal Data Adaptor SIX schema XML Docs DBMS Data Universal Adaptor Software CCTS XLS Java Objs 12 April 2005 W3C One-day Semantic Web Symposium, HKUST 29

30 Center for E-Commerce E Infrastructure Development (CECID) HK University R&D center established in full time staffs Focus: Open Source B2B and EAI Technology A leader in ebxml open source software Primarily funded by HK Govt (US$( US$3M) Additional industry sponsorship ~US$ M M (cash and software) Commercial revenue R&D outsourcing and consultancyc R&D productization Received awards from Hong Kong IT Excellence Awards Asia Pacific Information & Communications Technology Awards 12 April 2005 W3C One-day Semantic Web Symposium, HKUST 30

31 Thank you Thomas Lee URL: