Emerging XML Technology: Semantic Web and Electronic Business

1
Emerging XML TechnologySemantic Web and
Electronic Business

• Ching-Long Yeh ???
• Department of Computer Science and Engineering
• Tatung University
• Taipei, Taiwan
• Email chingyeh_at_cse.ttu.edu.tw
• http//www.cse.ttu.edu.tw/chingyeh

2
Content

• Web technology evolution
• Semantic Web
• Electronic Business Architecture ebXML
• RosettaNet

3
Web Technology Evolution
4
Web Technology

• WWW
• Infrastructure
• HTML, HTTP, URI
• Services
• Search engine and directory navigation
• WWW XML
• Business automation
• ebXML, RosettaNet
• Meaning processing automation
• Semantic Web (WWWOWL/RDF)
• Services automation (WWWOWL-S/RDF)

5
WWW
Information Pool
Application
Client
Web server
URL
HTML Document
HTTP

• HTTP (Hyper Text Transport Protocol)
• HTML (Hyper Text Markup Language)
• URL (Uniform Resource Locator)

• Human-to-machine interaction
• Information explosion

6
Interaction Using XML
Information Pool
Information Pool
Application
Application
SOAP server
SOAP server
XML Document
XML Document
HTTP

• XML (eXtensible Markup Language)
• SOAP (Simple Object Access Protocol)

• Machine-to-machine interaction
• Service automation

7
Web Service Architecture
8
Electronic Business

• Application-to-Application
• Business Process Automation
• RosettaNet
• ebXML

Company B
Company A
ERP
ERP
9
Semantic Web

• The Semantic Web is a vision

the idea of having data on the web defined and
linked in a way that it can be used by machines
not just for display purposes, but for
automation, integration and reuse of data across
various applications
10
Semantic Web

• The Semantic Web a Web with a meaning.

"If HTML and the Web made all the online
documents look like one huge book, RDF, schema,
and inference languages will make all the data in
the world look like one huge database Tim
Berners-Lee, Weaving the Web, 1999
11
The Semantic Web Layered Architecture
Trust
Sig
Proof
Logic
Rules
Tim Berners-Lee Axioms, Architecture and
Aspirations W3C all-working group plenary
Meeting 28 February 2001
Ontology
RDF Schema
(http//www.w3.org/2001/Talks/0228-tbl/slide5-0.ht
ml)
RDF MS
XML Schema
XML
Namespaces
URI
Unicode
12
The Big Picture of SW
(http//semanticweb.org/about.htmlbigpicture)
13
What Is in an Ontology?

• One widely cited definition of an ontology is
  Grubers Gruber 1993 A specification of a
  conceptualization.
• An ontology is a formal explicit description of
• concepts in a domain of discourse (classes
  (sometimes called concepts)),
• properties of each concept describing various
  features and attributes of the concept (slots
  (sometimes called roles or properties)), and
• restrictions on slots (facets (sometimes called
  role restrictions)).
• An ontology together with a set of individual
  instances of classes constitutes a knowledge
  base.

14
Ontology Spectrum
(From http//www.ksl.stanford.edu/people/dlm/pape
rs/ontologies-come-of-age-mit-press-(with-citation
).htm)
15
Semantic Web Languages
16
What is XML?

• Extensible Markup Language
• A Syntax for Documents
• A Meta-Markup Language
• A Structural and Semantic Language, not a
  Formatting Language
• Not just for Web pages

17
XML Standards

• DTD
• Namespace
• Schema
• DOM
• CSS, XSL-T, XSL-FO
• XLink
• XPointer

18
XML Protocol SOAP
19
RDF MS

• RDF (Resource Description Framework)
• Beyond Machine readable to Machine understandable
• RDF consists of two parts
• RDF Model (a set of triples)
• RDF Syntax (different XML serialization syntaxes)
• RDF Schema for definition of Vocabularies (simple
  Ontologies) for RDF (and in RDF)

20
RDF Data Model

• Resources
• A resource is a thing you talk about (can
  reference)
• Resources have URIs
• RDF definitions are themselves Resources
• Properties
• slots, define relationships to other resources or
  atomic values
• Statements
• Resource has Property with Value
• (Values can be resources or atomic XML data)
• Similar to Frame Systems

21
A Simple Example

• Statement
• Ora Lassila is the creator of the resource
  http//www.w3.org/Home/Lassila
• Structure
• Resource (subject) http//www.w3.org/Home/Las
  sila
• Property (predicate) http//www.schema.org/Cre
  ator
• Value (object) "Ora Lassila
• Directed graph

sCreator
http//www.w3.org/Home/Lassila
22
OWLW3C Web Ontology Language

• OWL provides three increasingly expressive
  sublanguages OWL Lite, OWL DL, and OWL Full.

23
OWLW3C Web Ontology Language
OWL Lite language constructs
RDF Schema Features Class rdfProperty
rdfssubClassOf rdfssubPropertyOf rdfsdomain
rdfsrange Individual
(In)Equality equivalentClass equivalentProperty
sameAs differentFrom allDifferent
Property Characteristics inverseOf
TransitiveProperty SymmetricProperty
FunctionalProperty InverseFunctionalProperty
Property Type Restrictions allValuesFrom
someValuesFrom
Restricted Cardinality minCardinality (only 0
or 1) maxCardinality (only 0 or 1) cardinality
(only 0 or 1)
Header Information ontology imports
24
Semantic Web Services
25
Some Motivating Tasks

• The kinds of task we expect OWL-S to enable
• Automatic Web service discovery
• Automatic Web service invocation
• Automatic Web service composition and
  interoperation
• Automatic Web service execution monitoring

26
High-level View of the Service Ontology
Service
Resource
provides
presents
supports
describedBy
ServiceProfile
ServiceGrounding
What the service does
How to Access it
ServiceModel
How it works
27
Top Level of the Process Ontology
Input Precondition Output effect
hasProcess hasProfile
Process
Profile
Condition
Atomic Process
has Grounding
computedInput computedOutput computedEffect comput
edPrecondition invocab
Composite Process
expand collapse
realizes realizedBy
Simple Process
compsedBy
Control Construct
Sequence
Repeat Until
28
Grounding a Service to a Concrete Realization
OWL-S
DL-Based Types
Process Model
Inputs/Outputs
Atomic Process
Message
Operation
Binding to SOAP, HTTP, etc.
WSDL
29
Electronic Business Architecture
30
The ebXML Framework at Work
31
Components of the ebXML Framework

• Defining how public business-process must be
  described using the ebXML BPSS standard.
• Defining the semantics of business documents that
  are exchanged in public processes using ebXMLs
  Core Component (ebCC) standard.
• Definition of services and the constraints in
  using the services using Collaboration Protocol
  Profile (CPP) defined in the ebXML CPPA standard.
• Description of the mutual agreement between the
  business partners Collaboration Protocol
  Agreement (CPA) to carry out the public
  business process. The schema for a CPA is also
  defined by ebXML CPPA standard.
• Protocols for registering, storing, and
  retrieving public business processes and
  associated business documents, and CPPs using the
  ebXML Registry standard.
• A standard way to send and receive messages
  between business partners, as defined in the
  ebXML Message specification.

32
RosettaNet
33
Background

• RosettaNet
• A non-profit consortium
• More than 500 members
• Founded in February 1998, including
• Computer and Consumer Electronics (CCE),
• Electronic Components (EC),
• Semiconductor Manufacturing (SM)
• Telecommunications (TC) industries
• the Logistics (LG) and Solution Provider (SP)
  communities
• Open e-business standards and services
• Breaking language barriers and establishing a
  global language for e-business
• Companies can realize the full potential of the
  digital economy,
• highly effective trading networks,
• operational efficiencies and
• new business opportunities

34
RosettaNet?????
????(B??)
????(A??)
?? ???? ????
???? ???? ??
Trading Partner
Trading Partner
35
RosettaNet??????

• RosettaNet???????????????,????????????????,?????
• ?????????
• RosettaNet Partner Interface Processes(PIPs)
• ???????
• RosettaNet Business Dictionary?RosettaNet
  Technical Dictionary
• ????????
• RosettaNet Implementation Framework (RNIF)
• ????????www.rosettanet.org??

36
????-PIP

• ????????,?????
• ??????????
• ???????????????????????

37
????-PIP

• ?????????????(cluster)????(segment)??

38
PIP ClassificationClusters

• Cluster 0 RosettaNet Support
• Cluster 1 Partner Product and Service Review
• Cluster 2 Product Information
• Cluster 3 Order Management
• Cluster 4 Inventory Management
• Cluster 5 Marketing Information Management
• Cluster 6 Service and Support
• Cluster 7 Manufacturing

39
PIP 2A2 Query Product Information Business
Process Model
40
PIP 3A4 Request Purchase Order Business Process
Model
41
????-PIP

• PIP????????.zip???rosettanet??,????
• ???(.doc) ???
• XML DTD???????????
• ??????
• ????????????

42
????-PIP

• ?????Open-EDI Reference Model (ISO/IEC
  14662)???????,??
• ??????(Business Operational View, BOV)
• ???????????
• ??????(Functional Service View, FSV)
• ???????????
• ??????(Implementation Framework View, IFV)
• RosettaNet???????????

43
PIP BOV
44
PIPTM3A4 ?BOV??????
Table 3-3 Business Activity Performance Controls
Acknowledgment of Receipt
Activity Name
Time to Acknowledge Acceptance
Time to Perform
Retry Count
Is Authorization Required?
Non-Repudiation of Origin and Content?
Role Name
Non-Repudiation Required?
Time to Acknowledge
Create Purchase Order
Y
2hr
24hr
24hr
3
Y
Y
Buyer
Cancel Purchase Order
Y
2hr
24hr
24hr
3
Y
Y
Buyer
Buyer
Revise Purchase Order
Y
2hr
24hr
24hr
3
Y
Y
45
PIPTM3A4 FSV????????
Purchase Order Request Dialog
Buyer
Seller


1. request(PurchaseOrderRequestAction)


1.1. signal(ReceiptAcknowledgement)

2. response(PurchaseOrderAcceptanceAction)

2.1. signal(ReceiptAcknowledgement)

46
PIPTM3A4 IFV
Purchase Order Request Dialog
Table 5-1 Business Message and Communications
Specification

Business Message Guideline
Digital Signature Required?
SSL Required?
1.
Purchase Order Request Guideline
Y
Y
1.1
Receipt Acknowledgement Guideline
Y
Y
2.
Purchase Order Acceptance Guideline
Y
Y
2.1
Receipt Acknowledgement Guideline
Y
Y
47
PIPTM3A4 XML DTD

• lt!ENTITY common-attributes "id CDATA IMPLIED"
  gt
• lt!ELEMENT Pip3A4PurchaseOrderAcceptance (
• PurchaseOrder ,
• fromRole ,
• toRole ,
• thisDocumentGenerationDateTime ,
• thisDocumentIdentifier ,
• requestingDocumentIdentifier ,
• GlobalDocumentFunctionCode ,
• requestingDocumentDateTime ) gt
• lt!ELEMENT PurchaseOrder (
• deliverTo? ,
• comment? ,
• GlobalPurchaseOrderStatusCode ,

48
PIP??
PIP???????????????????? ???????XML??
????
????
?? ???? ????
???? ???? ??
Trading Partner
Trading Partner
PIP???????????????
49
????-??
????
????
?? ???? ????
???? ???? ??
??
Trading Partner
Trading Partner
??
50
??????

• ??????? (DUNS)
• ?????
• ???? (GTIN)
• ???? (UN/SPSC)
• ???? (Dictionaries)

51
???????????

• ???????(DUNS)
• PIPsTM ????????????
• ?????(GTIN)
• PIPs??????
• ?????(UN/SPSC)
• ??????PIP (Cluster 2) ?????????

52
Technical Components - RNIF
????
????
RNIF???XML?MIMI???????,????????
?? ???? ????
???? ???? ??
Trading Partner
Trading Partner
53
Technical Components - RNIF
RNIF 1.1
RNIF 2.0
Attach- ments
RosettaNet Business Document
Service Content
Service Header
Preamble Header
Service Header




MIME Packaging
S/MIME Envelope
Encrypted Payload Container
Digital Signature
RNIF Version ID
Service Message
Preamble Header
Delivery Header
Digital Signature





MIME Packaging
RosettaNet Object (RNO)
RosettaNet Business Message
54
RosettaNet vs. ebXML

• ebXML is a meta-Model of EB Architecture
• RN can be seen as an instance of ebXML
• Business Processes
• PIPs in process models
• PIPs are the basic dialogues for creating
  business collaborations.
• Representation using business process language in
  ebXML, BPSS
• Vocabulary
• Both technical and business dictionaries RNTD,
  RNBD
• Convert to Core Components
• No partner profile, but having implicit agreement
• Using CPP and CPA
• Message service RNIF
• ebXML message services
• No registry
• ebXML registry and repository

55
Conclusions

• Automation of meaning processing on the Semantic
  Web
• EB automation based on XML technology
• Integration of EB standards using the meta-model,
  ebXML
• Managing corporate EB using ebXML RR
• EB as e-Services based on the Semantic Web
  Services