OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

regrep-semantic message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [Fwd: Semantic Web Services Architecture Committee Requirements Document]


Just announced: The Semantic Web Services Initiative (SWSI) has released
architecture requirements for Semantic Web Services. Highlights are
included below - including service lifecycle and ontology management.

[1] http://www.daml.org/services/swsa/swsa-requirements.html

Thanks,
Joe

HIGHLIGHTS:

(1) Semantic Web Services are viewed as a way to extend the capabilities
of web services in the direction of dynamic interoperability, thereby
making it possible for clients to successfully utilize web services
without prior arrangements between people that are realized in rigid
software protocols, and immutable ontologies or meta-data. 

(2) The functions addressed by the Semantic Web Services Architecture
will include:

* Dynamic Service Discovery: The capability for a software agent to
identify candidate services for particular objectives; includes
candidate service matchmaking and brokering functions.

* Service Selection and Composition: The capability to dynamically
select and compose services to achieve some objective; includes failure
recovery and compensation mechanisms, as well as choreography
interpretation and execution. Also includes ontology translation
services.

* Negotiation and Contracting: Ability for two agents to mutually
formulate a shared agreement in terms of performance to be provided;
includes dispute resolution and compliance.

* Semantic Web Community Support Services: Capabilities associated with
sharing semantic descriptions, ontologies, ontology mappings, and
service catalogs within and across communities, and managing these items
as well.

* Semantic Web Service Lifecycle and Resource Management Services:
Capability to management the lifecycle of Semantic Web Services.

* Other: Includes QoS requirements (time, cost, reliabilty, operational
metrics, etc.), and the capability to discover a service based on these
factors.

-------- Original Message --------
Subject: Semantic Web Services Architecture Committee Requirements  
Document
Resent-Date: Thu,  3 Jun 2004 11:28:16 -0400 (EDT)
Resent-From: public-sws-ig@w3.org
Date: Thu, 03 Jun 2004 11:28:06 -0400
From: Mark Burstein <burstein@bbn.com>
To: public-sws-ig@w3.org


The Architecture Committee of the Semantic Web Services Initiative
(SWSI) 
has spent the last few
months putting together an overview of the functional requirements that
a 
comprehensive approach to architectures for semantic web services should 
include.  While different communities will need more or
less of some of the features covered, we felt it was worthwhile to try
to 
take a longer term view in this exercise.

The document is available for review and comment from the SWSA committee 
home page at
http://www.daml.org/services/swsa/

The document itself is located at

http://www.daml.org/services/swsa/swsa-requirements.html

Comments can be sent to public-sws-ig or to me personally at the address
below.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]