From michael at digital.com.au Thu Feb 24 21:45:17 2011 From: michael at digital.com.au (Michael Elliot) Date: Thu Feb 24 21:45:36 2011 Subject: [uf-new] Available Resources Index File Message-ID: Hello, I've just typed up a sample implementation of a draft specification I'm working on called an "Available Resources Index". Rather than using the link element in the HTML document to reference various resources such as a favicon or RSS feed URL etc., I thought that a more specific approach would be a better solution and provide more flexibility. The name isn't necessarily fixed in stone, either. This page (http://www.digital.com.au/ari-sample/) references an ARI file using a link element. The ARI file can be found here: http://www.digital.com.au/ari-sample/ari.json I'm posting this here to garner critical feedback about and to discuss this implementation. Some benefits to users and notes that come to mind are: * A browser menu option or associated shortcut key to compose an email to a site's correct support department. * A small Twitter icon in the status bar indicating that this site has a Twitter account. Clicking this navigates to their account page. * More flexibility with the JSON format and smaller document size. * External file allows for caching and avoids resending the same inline data on different page requests. * Written specifically for its intended purpose rather than piggy-backing off an existing format. I initially wrote this because I wanted a way for sites to discover other site's JSON RPC URL so that they can communicate between each other and I didn't really like the link element approach. Looking forward to any and all feedback. Regards, Michael Elliot Network Digital From mail at tobyinkster.co.uk Fri Feb 25 14:57:17 2011 From: mail at tobyinkster.co.uk (Toby Inkster) Date: Fri Feb 25 14:56:50 2011 Subject: [uf-new] Available Resources Index File In-Reply-To: References: Message-ID: <20110225225717.7b4eedec@miranda.g5n.co.uk> On Fri, 25 Feb 2011 13:45:17 +0800 Michael Elliot wrote: > I initially wrote this because I wanted a way for sites to discover > other site's JSON RPC URL so that they can communicate between each > other and I didn't really like the link element approach. Looks to me like you're re-inventing the wheel. http://www.google.com/search?btnI=1&q=w3c+powder+primer http://www.google.com/search?btnI=1&q=host-meta -- Toby A Inkster