Medical metaphor



Ontologies: anatomy
Processes: physiology
Applications: pathology 
7/1/2016 3:51:27 PM
1
Web Services

Thoughts about definitions






Dependence on protocols
Designed for machines to use
Surely not everything on the Web
Programming metaphor
Special representations to facilitate programmatic use
Steps to a definition



Metaphor and Benefits
Research Area  Semantic Web
Techniques



Possible
Current, e.g., WSDL
Old, e.g., CGI, Perl
7/1/2016 3:51:27 PM
2
Require/Emphasize

Common properties of the Web:










Asynchrony
Autonomy (discovery, trust)
Heterogeneity
Dynamic (change)
Scalable
Evolve
Self-describing (formally)
Symmetric P2P
Conversational
Depth of self-description
7/1/2016 3:51:27 PM
3
Semantic WS Scope
Worth pursuing
Std
Program
All
7/1/2016 3:51:27 PM
Formally self-described
currency.com
Amazon
html
Self-described
Hard code
People
4
Role of P2P



Platform for semantic Web
New way of organizing WS-based systems
Limits of global index?



Will P2P apply?
Is there a central location for ontologies?
Selecting services based on



Domain ontology
Tag
Natural language
7/1/2016 3:51:27 PM
increasing semantics
5
Application Classes


Information sharing
Trawling the deep Web








Dynamic, e.g., financial data
Databases
Discovery
Inter-organizational workflow (virtual enterprises and supply chains)
Provisioning
GRID: OSGA
Personal information
Software as a service (WSP: Web-Service Provider, hosted service)




Buy car
Lease car
Rent a car
Taxi
7/1/2016 3:51:27 PM
Old Web
New Web
6
Research Issues

Environment


Representation





Programming
Interaction (system)
Architecture
Utilities
7/1/2016 3:51:27 PM




Scalable, openness,
autonomy, heterogeneity,
evolving
Self-description,
conversation, contracts,
commitments, QoS
Compose & customize,
workflow, negotiation
Trust, security, compliance
P2P, privacy,
Discovery, binding, trustservice
7
Research Issues











Conversational (state-based, event-based, history-based)
Interoperability of conversational services – compose, translate,
Representations for services: programmatic self-description
Commitments, contracts, negotiation
Discovery, location, binding
Compliance
Cooperation
Transactional workflow: rollback, roll-forward, semantic
exception handling, recovery
Trustworthy service (discovery, provisioning, composition,
description)
Security; privacy vs. personalization
Quality-of-Service, w.r.t. various aspects, negotiable
7/1/2016 3:51:27 PM
8
Mike’s Humor

Services vs. Ontologies
“Well done is better than well said.”
Ben Franklin
7/1/2016 3:51:27 PM
9
SWS– Fitting in and expanding IS/DB/DM:
Or why Bhavani & George should care?
Data => services, similar yet more challenging:






Modeling
Organizing collections
Discovery and comparison (reputation)
Distribution and replication
Access and fuse (composition)
Fulfillment




Contracts, coordination versus transactions
Quality: more general than correctness or precision
Compliance
Dynamic, flexible information security and trust.
7/1/2016 3:51:27 PM
10
Problem Categories
1.
2.
3.
4.
5.
6.
7.
8.
9.
Publishing
Discovery
Selection/comparison/negotiation = decision
Composition, aggregation, customization,
abstraction
Interoperation
Fulfillment
Compliance
Security, privacy, and trust
Versioning
7/1/2016 3:51:27 PM
11
Problem Elements: 1
1.
Models and approaches for publishing w.r.t. different



2.
Organize services for discovery


3.
Architectures
Usages
Languages
Ontology of services
Attributes of providers
Service selection

Architecture


Market-based, cooperative, negotiating, …
Optimization


QoS
Others, e.g., trust, reputation
7/1/2016 3:51:27 PM
12
Problem Elements: 2
4.
Composition (aggregation, customization)




5.
Interoperability of processes and data models


6.
Architecture (e.g., agents)
Mechanisms
Humans as service components
Reasoning
Automation
Discovery
Fulfillment (contracts, coordination)



Transactions: exceptions, replications, recovery
Architecture (authorities for transaction disputes about QoS,
service-level agreements
Run-time monitoring
7/1/2016 3:51:27 PM
13
Problem Elements: 3
Compliance, enforcement
7.


Reward or penalty
Architecture
7/1/2016 3:51:27 PM
14
Questions: 1
A. What are necessary elements and principles for a WS modeling
and development framework?
B. How can a composed service be described vis à vis constituent
services?




On the fly
Composable descriptions
Decomposable descriptions
Metadata attributes, i.e., functional, execution, QoS, security
C. How can service descriptions be organized and disseminated?


Taking metadata attributes into account
Architectures, e.g., self-organizing
7/1/2016 3:51:27 PM
15
Questions: 2
D. How can abstractions for WS composition (e.g., contracts,
coordination) be described and applied?



Monitor fulfillment
Check compliance
Assign credit and blame
E. How can a collection of services interact (collaborate/compete)
to solve the needs of a service requestor?

Negotiate among providers and requestors
F. How can trust be supported in the discovery, selection,
composition, and fulfillment of Web services?

Architectures without trusted third parties
G. How can process and data models interoperate?


Automation
Discovery
7/1/2016 3:51:27 PM
16