W3C home > Mailing lists > Public > www-ws-desc@w3.org > January 2003

RE: Minutes: 22 Jan 2003 WS Description FTF

From: Jeffrey Schlimmer <jeffsch@windows.microsoft.com>
Date: Mon, 27 Jan 2003 09:58:36 -0800
Message-ID: <2E33960095B58E40A4D3345AB9F65EC109E4BD50@win-msg-01.wingroup.windeploy.ntdev.microsoft.com>
To: <www-ws-desc@w3.org>

FWIW, here is my summary of the requirements-related actions from our
face-to-face discussion on the morning of 22 Jan.

Reword R118 to "The description language SHOULD provide for reuse of a
group of Interfaces."
[Done]

Reword R058 to avoid specifying a design.
[Reworded to "The description language SHOULD provide for extension of a
group of Interfaces."]

Retain non-requirements.
[Preserved in XML but not displayed by current style sheet.]

Include as a non-requirement R126: "The description language SHOULD
provide for validation of WSD documents that are entirely abstract and
MUST not contain non-abstract information and provide for validation of
WSD documents that are entirely concrete and MUST not contain abstract
information."
[Done]

Add new requirement re: using Schema (or comparable) to describe message
content.
[Added R127 "Message definitions MUST describe constraints on Message
content using a machine-readable type-description language such as XML
Schema."]

Add new requirement re: constraints on service location URIs.
Add new requirement re: message "parts" in the SOAP Body and/or in
service location URI.
[Added R128 "InterfaceBindings SHOULD provide for mapping Message
content to service location URIs."]

Suggest wording for requirement to be able to specify MIME types.
[Added DRAFT R129 "The description language SHOULD allow specifying the
MIME media type of message content."]

Remove R110
[Done]

Identify existing (or open new) issue re: optional parts with HTTP URL
replacement.
[Opened Issue 71.]

Add new requirement re: optional message content.
[Added R130 "The description language SHOULD allow describing messages
with optional content.]

Suggest wording for requirement to define a construct to use within a
message to reference WSDL constructs.
[Added DRAFT R130 "The WG SHOULD define components that may be used
within Messages to refer to other WSDL components."]

--Jeff

> -----Original Message-----
> From: Jonathan Marsh
> Sent: Friday, January 24, 2003 11:44 AM
> To: www-ws-desc@w3.org
> Subject: Minutes: 22 Jan 2003 WS Description FTF
> 
Received on Monday, 27 January 2003 12:59:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:22 GMT