- From: Jonathan Rees <jar@creativecommons.org>
- Date: Thu, 22 Jan 2009 11:46:14 -0500
- To: Eran Hammer-Lahav <eran@hueniverse.com>
- Cc: "www-tag@w3.org" <www-tag@w3.org>
Thanks for doing this - it looks very good. I have a few other comments which I'll send later. I know you are staying away from discussion of whether the information in a resource descriptor is "authoritative", or at least more "authoritative" than information found through other means, and that's probably a good thing, but I know the question will come up. Until we have a consensus theory, I think we have to assume that the descriptor is, in general, not authoritative, since authority is always relative to what's being said - any particular agent can make only some statements authoritatively. For example, a statement that a piece of historic writing has a certain author is not up to me; my saying that the author is so-and-so cannot be authoritative, because I can be wrong. This is true even if I "own" a URI with which the work was named and I make the statement naming the work using that URI. You can choose to trust me when I say it, and you may be justified in doing so; but that's a different phenomenon from an exercise of "authority". The "in general" is important since particular applications, such as OpenID, might choose to take certain bits of information found in the descriptor to be authoritative, and that's OK. That's not the same as saying *all* the information is authoritative. I can't say I have a good theory of authority on the web, but in my spare time I would like to work on one or hunt one down (if it already exists). BAN logic http://en.wikipedia.org/wiki/BAN_logic might be my starting point. If anyone else has any insight let me know. For now I wanted to make sure this caution was stated. Best Jonathan On Tue, Jan 13, 2009 at 1:18 PM, Eran Hammer-Lahav <eran@hueniverse.com> wrote: > > http://tools.ietf.org/html/draft-hammer-discovery-00 > > I have recently published a draft for obtaining resource descriptors via HTTP using Link headers, Link elements (HTML, Atom), and Site-Meta [1]. The draft goal is to provide a unified view on how to use the three methods for obtaining information about resources (discovery). The draft invents very little (an extension to Site-Meta allowing it to describe individual resources and not just the overall site). > > Any feedback would be greatly appreciated and can be sent directly to me or discussed on the www-talk@w3.org mailing list. > > Thanks, > > EHL > > [1] http://tools.ietf.org/html/draft-nottingham-site-meta-00 > >
Received on Thursday, 22 January 2009 16:46:58 UTC