On 06/18/2008 6:25 PM, Bob Wyman wrote: > On Wed, Jun 18, 2008 at 4:52 PM, Blaine Cook <[EMAIL PROTECTED]> wrote: >> XRDS for this seems like massive overkill. >> Whatever happened to good 'ol <link rel>? >> It works fantastically for RSS feeds, which are >> alternate representations of presented data, >> just like messaging endpoints. > > I think we may risk over using "good 'ol <link rel>". There is an issue here > of "separation of concerns" or proper modularization. While <link rel> might > "work", it does not seem right to rely on this mechanism for all links to > all resources -- no matter how indirectly they may be related to the page in > which they are found. I suggest that <link rel> should really only be used > to link to resources that have a particular direct relationship to the HTML > page in which the links are found. Links to Atom or RSS syndication files > are typically links to alternative representations of the HTML files in > which they are found and thus would fit the rule that I suggest. > > The JID that should be used in sending a message to the "owner" of a page is > only indirectly related to an HTML page itself.
How is contacting the page owner / creator less "direct" than finding an alternative representation of the content? If the web is to be truly social then ISTM that it's completely appropriate to provide links to content creators, discussion forums, microblogging feeds, and anything else of interest. > Thus, it seems reasonable to > use a mechanism which is explicitly intended to store links to persons or > things with identity -- i.e. the XRDS file. > > Today, there aren't many things that get put in XRDS files. The result is > that XRDS files often seem over designed for the limited purpose of > providing links to OpenID services, etc. However, I think we'll find in the > future that users will have a need to associate a broad set of linked > resources to their identities. As this set of commonly linked resources > grows, it will become less and less reasonable to stuff them all into HTML > embedded <link rel>s. It should also be noted that it is quite likely that > in many applications, XRDS files won't actually be maintained as static > files on disk. They will, in fact, be generated on-demand and as a result > will be able to accommodate potentially changing data. (my XRDS file might > contain a link to the resource that describes my current location...) > Forcing links to be stored in HTML would have the effect of discouraging the > use of dynamic sets of links and, even if implemented via various templating > systems, the use of dynamically changing links in HTML files would tend to > make a mess of caching schemes -- even though the changes are not related to > the HTML content itself. > > Use <link rel> for what it was intended to be used: Links to resources which > are related to the containing HTML page. Use XRDS files for links that > relate to things which have identity. Says who? Can't a link point to any URI, not just a web page? I don't see any such restriction in the HTML 4.0 spec. Peter -- Peter Saint-Andre https://stpeter.im/
smime.p7s
Description: S/MIME Cryptographic Signature
