Outbrief of SWSI Architecture Committee F2F Sat, April 12, 2003 Miami, FL

1
Outbrief of SWSI Architecture CommitteeF2FSat,
April 12, 2003Miami, FL

• Mark H. Burstein
• BBN Technologies

2
Potential Requirements for SWS(the big picture)

• For WS, interpretation of XML seems essential.
• For SWS, Agents must be able to
• Interpret OWL (or equiv)
• Or bridging by providing semantics for
  non-semantic agents
• Incorporate of new classes, descriptions
  dynamically
• Formulate goals that can be satisfied by
  discovery (or possibly composition) of remote
  services
• Access internal knowledge to supply information
  required for service requests (e.g. credit card
  info)
• Utilize internal or external translation
  capabilities

3
WSMF and Oracle EI approach
Internet
SWIFT
WSMF
WSMF
VAN
4
Content and Process Mediation

• Process Mediation
• Anticipate and provide processes to handle
  ordering constraints between mediated parties
• Semantic Mediation
• Large semi-automated message format and term
  mapping system
• Mappings are necessarily PARTIAL
• Teams of people to maintain them due to
  continuous version changes

S E M A N T I C MAP ING
OAGIS PO
SAP PO
OAGIS ACK
OAGIS POA
SAP POA
OAGIS ACK
Process mediation
5
Relevant Agent Architectures to Consider As
Participating in the Semantic Web

• FIPA
• CoABS Grid
• Cougaar
• Retsina
• OAA
• Scientific Grid

6
Architectures for Semantic Integration(Whose
ontologies are these anyway?)

• Holy Grail Ontological Negotiation
• Status Quo
• (manual mappings, limited interlingua)
• Global Ontologies
• Manual Mapping
• Interlingua Ontologies
• Community Ontologies

7
(No Transcript)
8
(No Transcript)
9
Near-term Objectives

• Develop full use cases in different environments,
  domains
• Use cases with people interacting with services
  and not, providing ontology maintenance support
  at different points in the architecture
• Review and determine feasibility of building on
  top of W3C WS Architecture
• Build some small feasibility prototypes
• Tools is the key issue

10
Possible Architectural Use Cases

• Interacting w. traditional web services
• (Amazon, Travel, Shopping) C2B2B, composed C2B
• Large-scale B2B commerce
• like Oracle EI
• Pervasive Computing
• Smart space environment
• services appropriate to a room
• convert a file to make it printable, then print
  it
• MyGrid computing
• Semantics for long-lived distributed computing

11
In our spare time
Disjunctive
Disjunctive
Input Dataset 1
Ouput Style 1
Requestor Process P1
Server Process P1
Condit Output
Input Dataset 2
Ouput Style 2
Has input (under condition)
Input Dataset 3
Ouput Style 3
Has grounding (with argument bindings
translations)
Has grounding (with argument bindings
translations)
Message
Message