RE: Why is "name" required on service and endpoint?

Yes, the names are for component references, which are needed by RDF.

BTW, name is optional when using the service type to transmit endpoints in 
messages.

Arthur Ryman,
Rational Desktop Tools Development

phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
intranet: http://labweb.torolab.ibm.com/DRY6/



<paul.downey@bt.com> 
Sent by: www-ws-desc-request@w3.org
12/15/2004 11:26 AM

To
<dbooth@w3.org>, <www-ws-desc@w3.org>
cc

Subject
RE: Why is "name" required on service and endpoint?







ISTR last hearing them mentioned during discussions 
around component designators and the RDF mapping, 
if that rings any bells ..

-----Original Message-----
From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org]On
Behalf Of David Booth
Sent: 15 December 2004 16:09
To: www-ws-desc@w3.org
Subject: Why is "name" required on service and endpoint?



Does anyone remember why we made the "name" attribute required on both
the service and the endpoint elements?  Does WSDL 2.0 actually use them
anywhere?

-- 

David Booth
W3C Fellow / Hewlett-Packard