W3C home > Mailing lists > Public > www-ws-desc@w3.org > February 2002

Re: Web Service Description: Charter Requirements

From: Jean-Jacques Moreau <moreau@crf.canon.fr>
Date: Tue, 12 Feb 2002 17:31:55 +0100
Message-ID: <3C69437B.D2E60442@crf.canon.fr>
To: Web Service Description <www-ws-desc@w3.org>
CC: FABLET Youenn <fablet@crf.canon.fr>
As further input, here are some additional requirements that come
to mind when reading the charter; to my mind at least (upon
examination, it looks like the list below has an implicit SOAP


4.2: Simplicity

Must support an open content model (charter says: "must support
distributed extensibility" and "will look into extending
interface descriptions in a decentralized fashion").

4.3 Interface description

Must describe SOAP 1.2 messages, including header, body,
encoding, fault, RPC, actor (charter says: "must describe
messages available via interface", "must describe error messages"
and "make sure SOAP 1.2 extensibility mechanism can be

Must describe SOAP 1.2 header and body's content type (charter
says: "must define [a mechanism for describing data types and
structures]  based on XML Schema" and "take into account ending
work going on in XML Protocol").

Must describe SOAP 1.2 RPC parameters types (ibid.).

Must support SOAP 1.2 intermediairies (charter says: "make sure
SOAP 1.2 extensibility mechanism can be expressed")

4.4 Description of interaction with a service

Must describe SOAP 1.2 MEP (Message Exchange Pattern) (charter
says: "must [...] describe [...] one-way messages, [...]

4.5 Binding description

Must ensure that SOAP 1.2, e.g, SMTP or BEEP bindings can be
described (charter says: "ensure that other SOAP bindings can be
Received on Tuesday, 12 February 2002 11:33:19 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:54:36 UTC