A Declarative Approach to Electronic Business

1
A Declarative Approach to Electronic Business

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

2
Abstract

• EB standards provide the neutral basis of
  interoperability between trading partner
• Moving from procedural approach to declarative
  approach
• Representation of EB standards using the ontology
  technique
• Declarative approach to EB implementation

3
Electronic Commerce

• Evolution of electronic commerce
• B2C, human-to-machine, online catalogue service
• B2B, AP-to-AP,
• EB standards
• RosettaNet?ebXML?BizTalk?

Company A
Company B
Backend AP
Backend AP
4
General EB Architecture

• EB standard architecture is divided into
• Upper level Standard business processes and
  document
• Lower level Services for message transport,
  routing and packaging

• Popular standards
• Horizontal integration ebXML
• Vertical integration RosettaNet (Information
  Technology, Electronic Component and
  Semiconductor Manufacturing)
• Messaging service BizTalk Framework

5
ebXML Technical Architecture
6
ebXML Infrastructure

• EB infrastructure consists of
• Trading partners information
• Collaboration Protocol Profile (CPP) and
  Collaboration Protocol Agreement (CPA)
• Business process and information meta model
• Business Process Schema Specification
• Core component and core library functionality
• Registry functionality
• Messaging service functionality

Common BP and vocabulary
7
CPP Structure
ltCollaborationProtocolProfile xmlns"http//www.e
bxml.org/namespaces/tradePartner" xmlnsds"http
//www.w3.org/2000/09/xmldsig" xmlnsxlink"http
//www.w3.org/1999/xlink" version"1.1"gt
ltPartyInfogt lt!--one or more--gt ...
lt/PartyInfogt ltPackaging id"ID"gt lt!--one or
more--gt ... ltPackaginggt ltdsSignaturegt
lt!--zero or one--gt ... lt/dsSignaturegt
ltCommentgttextlt/Commentgt lt!--zero or more--gt
lt/CollaborationProtocolProfilegt
8
CPA Structure
ltCollaborationProtocolAgreement
xmlns"http//www.ebxml.org/namespaces/tradePart
ner" xmlnsbpm"http//www.ebxml.org/namesp
aces/businessProcess" xmlnsds
"http//www.w3.org/2000/09/xmldsig" xmlnsxlink
"http//www.w3.org/1999/xlink"
cpaid"YoursAndMyCPA" version"1.2"gt
ltStatus value "proposed"/gt
ltStartgt1988-04-07T183909lt/Startgt
ltEndgt1990-04-07T184000lt/Endgt
lt!--ConversationConstraints MAY appear 0 or 1
times--gt ltConversationConstraints
invocationLimit "100"
concurrentConversations "4"/gt ltPartyInfogt
lt/PartyInfogt ltPartyInfogt lt/PartyInfogt
ltPackaging id"N20"gt lt!--one or more--gt
lt/Packaginggt ltdsSignaturegtany combination of
text and elements lt/dsSignaturegt ltComment
xmllang"en-gb"gtany textlt/Commentgt lt!--zero or
more--gt lt/CollaborationProtocolAgreementgt
9
Working Architecture of CPP/CPA
Party A (Seller, Server)

• Any Party may register its CPPs to an ebXML
  Registry.
• Party B discovers trading partner A (Seller) by
  searching in the Registry and downloads CPP(A) to
  Party Bs server.
• Party B creates CPA(A,B) and sends CPA(A,B) to
  Party A.
• Parties A and B negotiate and store identical
  copies of the completed CPA as a document in both
  servers. This process is done manually or
  automatically.
• Parties A and B configure their run-time systems
  with the information in the CPA.
• Parties A and B do business under the new CPA.

Registry
5.
CPP(A)
1.
(Document)
(Exec. codet)
CPA(A,B)
CPA(A,B)
CPP(B)
1.
2.
3.
4.
6.
CPP(X)
CPP(Y)
CPA(A,B)
CPA(A,B)
(Document)
(Exec. codet)
CPP(Z)
5.
Party B (Buyer, Server)
10
Business Process SchemaConcept
11
Business Process Schema in XML
12
Procedural Approach to EB

• Specifications
• Not machine-readable
• Need human interpretation
• Lack of partner discovery mechanism (registry,
  CPP, CPA)
• Example RosettaNet

13
Declarative Approach to EB

• Specifications
• Machine-readable (Business Process, Document, and
  Vocabulary in either UML or XML)
• Enabling automatic code generation
• Partner discovery mechanism (registry, CPP, CPA)
• Example ebXML

14
Forming CPA by Automatic Negotiation
Basic tasks of forming CPA
matches
matches
matches
15
Rule-based Formation of CPA
Ontology (BPS, BD, CC)
RDF triples store
Inference Engine
Web Server
Rule Base
Prolog rules
Input CPP1,CPP2 Result CPA or difference
BPS Business Process Schema BD Business
Document CC Core Components
16
Two-Layer Agent-Mediated EB Architecture

• We propose a two-layer agent-mediated EB
  architecture, where
• The Upper Layer consists of agents that play the
  role of Business Collaboration and Choreography
  in ebXML,
• The Lower Layer consists of agents each of which
  accomplishes a basic Business Transaction in
  ebXML.

17
(No Transcript)
18
Interactions between BT Agents
19
Interactions between BC Agents
20
Generation of Execution Code from CPA
Rule Base
BC Agent Code
Inference Engine
CPA
BT Agent Code
21
Implementation
22
Conclusions

• EB standards are moving towards declarative
  approach.
• We propose a declarative approach to EB
  implementation
• Ontology
• Rule-based
• Generation of execution codes from specification
  documents