W3C home > Mailing lists > Public > www-talk@w3.org > January to February 2009

Re: Discovery spec draft published

From: Joseph A Holsten <joseph@josephholsten.com>
Date: Sun, 11 Jan 2009 04:39:17 -0600
Message-Id: <45FE2739-2A72-4D40-973A-26BACD1EA588@josephholsten.com>
Cc: Eran Hammer-Lahav <eran@hueniverse.com>, Dirk Balfanz <balfanz@google.com>
To: www-talk@w3.org
  Dirk Balfanz wrote:
> The terms "service discovery" and "resource discovery" are not  
> consistently formed: In the term "service discovery" (in Section  
> 4), "service" is the thing that falls out of the process of doing  
> the discovering. In the term "resource discovery", "resource" is  
> the thing that is input into the process of doing the discovering -  
> what falls out of it are the resource's attributes.
> To be more consistent, they should be called "service discovery"  
> and "attribute discovery", or "attribute discovery" and "resource  
> discovery". The former would call out the things falling out of the  
> process of discovery, while the latter calls out the things that  
> discovery is performed on.

Eran Hammer-Lahav wrote:
> Well, it is really Resource Descriptor Discovery…

Attribute Discovery would be just saying, "To find a link with a  
certain rel-type, check the document links, the link headers, and the  
site-meta for the rel-type you're looking for." Resource Descriptor  
Discovery is performing Attribute Discovery for the "describedby" rel- 
type. It's trying to find the attribute pointing to the Resource  
Description document, like an XRD (Extensible Resource Descriptor) or  
POWDER (Protocol for Web Description Resources). Typically, these  
will be used for Service Discovery, but often can describe many other  
things as well.

Have I got that right?


Received on Monday, 12 January 2009 09:25:58 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:33:07 UTC