- From: Hugo Haas <hugo@w3.org>
- Date: Mon, 30 Sep 2002 18:22:25 +0200
- To: www-ws-arch@w3.org
* Christopher B Ferris <chrisfer@us.ibm.com> [2002-09-27 16:27-0400] > I want to emphasize that Heather is talking about ROLES here, not > things, not mechanisms. A role is an abstraction as are the other > nodes (roles) in the triangle diagram. The problem with using a role with the top node is that, at least to me, it feels like this is a third entity different from the others, and registry has this feel of centralized thing. If we ended up settling for a role, I think that the following would need to be very clearly underlined: - the publication/discovery role is an abstract role which may be fulfilled by the service provider itself. - there is no claim made as to how it is performed: it could be achieved using any number of solutions, be it centralized or not. Ideally, the word used would carry all that, which IMO registry does not. Hence my preference is to use the description of an action: Publish/Discover, or Publication and Discovery Mechanisms, or Advertizing and Discovery Mechanisms to quote DaveH. Regards, Hugo -- Hugo Haas - W3C mailto:hugo@w3.org - http://www.w3.org/People/Hugo/
Received on Monday, 30 September 2002 12:23:12 UTC