W3C home > Mailing lists > Public > www-ws-desc@w3.org > July 2004

RE: Atom API in WSDL 2.0

From: Asir Vedamuthu <asirv@webmethods.com>
Date: Thu, 8 Jul 2004 07:23:57 -0700
Message-ID: <5B10E50E14A4594EB1B5566B69AD94072EF628@maileast>
To: 'David Orchard' <dorchard@bea.com>, WS Description List <www-ws-desc@w3.org>
Hi David,

I reviewed your example and bumped into few issues. I do not know the impact
of these issues in your analysis. Perhaps, zero impact. Or, this may
increase the number of service elements. For convenience, I attached a copy
of your atom API in WSDL 20.

Line 139, "
<service name="atom3http" http:authenticationType="basic">
 <endpoint name="atom3HTTPPOSTURI" binding="atomapi:atomHTTPPOSTURI"/>
 <endpoint name="atom3HTTPEntryURI" binding="atomapi:atomHTTPEntryURI"/>
 <endpoint name="atom3HTTPFeedURI" binding="atomapi:atomHTTPFeedURI"/>

(a) missing: service/@interface is a required attribute

(b) there are references to 3 bindings in this service element. These
bindings are for three different interfaces: atomHTTPPOST, atomHTTPEdit, and
atomHTTPFeed. This violates one of WSDL 20 Constraints,

WSDL 20 Constraint: "For each Endpoint component in the {endpoints} property
of a Service component, the {binding} property (see 2.14.1 The Endpoint
Component) MUST either be a Binding component with an unspecified
{interface} property (see 2.9.1 The Binding Component) or a Binding
component with an {interface} property equal to the {interface} property of
the Service component." [1]


Hope this helps,

-----Original Message-----
From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org] On
Behalf Of David Orchard
Sent: Monday, July 05, 2004 6:47 PM
To: WS Description List
Subject: Atom API in WSDL 2.0

My take on the Atom API in WSDL 2.0.

I'll be using this to justify a couple of issues I've raised.

As always, grateful for any corrections or comments.


Received on Thursday, 8 July 2004 10:26:53 UTC

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