The Automatic Discovery indeX (ADX).

| No Comments | No TrackBacks

While I was out on my latest blogging hiatus, James Snell picks up on my response to earlier discussion by Jeremy Zawodny and Diego Doval for developing a means of more robust RSS auto-discovery. He writes:

As much as I like WSIL, it's pretty much officially dead. There is no further work going into it at all. So while I like where Tim is going with this, I think an alternative approach needs to be developed.

He goes on to layout an example of a new alternate WSIL-like format he calls The Automatic Discovery indeX (ADX).

I agree with James and had suspected as much about WSIL. Given James employer is one of the authors of that spec I'll take it as fact.

I also like where he's gone with ADX. Like WSIL, it's more RESTful then UDDI (which just needs to die) and relatively simple and versatility enough to integrate numerous format pointers into one mechanism – SOAP, RSS, OPML, Atom and so on. This could also be used as a more robust and eventually a better formed and documented blogroll format.

While its a good start, ADX as James has detailed it I think it could use some refinement – mostly what I think are nits.

  • Keep the tags all lowercase. Most formats do it that way so I see nothing gained be switching to proper case tags names.
  • I like the reuse of existing RSS modules such as Dublin Core however their use seems inconsistent. For instance James uses dc:title, but does not namespace Description. Name is also not namespaced and is about the equivalent of dc:title. I realize that James was transcribing my WSIL examples, but since this is a new format we might as well clean that up. Perhaps if Dublin Core is going (and should) play such an important roll those elements should just be folded into the syntax of this format?
  • In the spirit of Dublin Core, I'd reuse this element sets naming conventions as much as possible. Service.EndPoint becomes source or perhaps the RSS standard link and so on.
  • IndexRef should be expanded to allow for additional meta data to be associated with a reference to another index. For instance, what type of index is on the other side of this link? Another ADX? Or perhaps a UDDI directory? Or perhaps a OPML file. This is also an important allowance for blogroll use.
  • For argument sake, I'd like to see an example of a WSDL file and a UDDI pointer.
  • Having a schema is good, but I think should be optional in an ADX document.
  • I'm really hesitant of the DNS Service Discovery method because most users do not have the knowledge or access to implement such a thing.

Mostly nits. So here is my riff on James' original ADX proposal where I incorporate my feedback into an example:

 <?xml version="1.0" encoding="UTF-8"?>
 <index 
   xmlns:dcterms="http://purl.org/dc/terms/" 
   xmlns="urn:temporary:uri">

  <title>News4Humans feedOnFeeds</title>
  <dcterms:modified>2003-09-12T23:45:37-00:00</dcterms:modified> 
  <source>http://news4humans.com/index.adx</source>
  <description>All the news preferred by highly evolved primates.</description>
  <language>en-us</language>
  <creator>newsfor@news4humans.com</creator>

  <service>
  <name>Latest News</name>
  <description>A syndication feed of the 15 most recent news posts.</description>
  <source>http://news4humans.com/feeds/index.xml</source>
  <format>http://purl.org/rss/2.0/</format>
  <dc:modified>2003-09-12T23:35:52-00:00</dcterms:modified>
  </service>

  <service>
  <name>Google Search</name>
  <description>A SOAP interface to the Google search engine.</description>
  <format>http://schemas.xmlsoap.org/wsdl/</format> 
  <source>http://api.google.com/GoogleSearch.wsdl</source> 
  </service>

  <!-- This was IndexRef –>
  <link>
  <title>News4Humans Technology News Feeds</title>
  <description>All the news preferred by highly evolved primates.</description>
  <source>http://news4humans.com/tech.adx</source>
  <format>urn:temporary:uri</format>
  <creator>News4Humans</creator>
  </link>

 </index>

Thoughts?

<p>While I was out on my latest blogging hiatus, James Snell picks up on my response to earlier discussion by <a href="http://jeremy.zawodny.com/blog/archives/000967.html">Jeremy Zawodny</a> and <a href="http://www.dynamicobjects.com/d2r/archives/002324.html">Diego Doval</a> for developing a means of more robust RSS auto-discovery. He <a href="http://www.snellspace.com/blog/archivesNew/000065.html">writes</a>:</p>
<blockquote>
<p>As much as I like WSIL, it&#39;s pretty much officially dead. There is no further work going into it at all. So while I like <a href="http://www.timaoutloud.org/archives/000319.html">where Tim is going with this</a>, I think an alternative approach needs to be developed.</p>
</blockquote>
<p>He goes on to layout an example of a new alternate WSIL-like format he calls The Automatic Discovery indeX (ADX). </p>
<p>I agree with James and had suspected as much about WSIL. Given James employer is one of the authors of that spec I&#39;ll take it as fact. </p>
<p>I also like where he&#39;s gone with ADX. Like WSIL, it&#39;s more RESTful then UDDI (which just needs to die) and relatively simple and versatility enough to integrate numerous format pointers into one mechanism &#8211; SOAP, RSS, OPML, Atom and so on. This could also be used as a more robust and eventually a better formed and documented blogroll format.</p>
<p>While its a good start, ADX as James has detailed it I think it could use some refinement &#8211; mostly what I think are nits.</p>
<ul>
<li>Keep the tags all lowercase. Most formats do it that way so I see nothing gained be switching to proper case tags names.</li>
</ul>
<ul>
<li>I like the reuse of existing RSS modules such as Dublin Core however their use seems inconsistent. For instance James uses <code>dc:title</code>, but does not namespace <code>Description</code>. <code>Name</code> is also not namespaced and is about the equivalent of <code>dc:title</code>. I realize that James was transcribing <a href="http://www.timaoutloud.org/files/diego/index2.wsil">my WSIL examples</a>, but since this is a new format we might as well clean that up. Perhaps if Dublin Core is going (and should) play such an important roll those elements should just be folded into the syntax of this format?</li>
</ul>
<ul>
<li>In the spirit of Dublin Core, I&#39;d reuse this element sets naming conventions as much as possible. <code>Service.EndPoint</code> becomes <code>source</code> or perhaps the RSS standard <code>link</code> and so on. </li>
</ul>
<ul>
<li><code>IndexRef</code> should be expanded to allow for additional meta data to be associated with a reference to another index. For instance, what type of index is on the other side of this link? Another ADX? Or perhaps a UDDI directory? Or perhaps a OPML file. This is also an important allowance for blogroll use.</li>
</ul>
<ul>
<li>For argument sake, I&#39;d like to see an example of a WSDL file and a UDDI pointer. </li>
</ul>
<ul>
<li>Having a schema is good, but I think should be optional in an ADX document.</li>
</ul>
<ul>
<li>I&#39;m really hesitant of the DNS Service Discovery method because most users do not have the knowledge or access to implement such a thing.</li>
</ul>
<p>Mostly nits. So here is my riff on James&#39; original ADX proposal where I incorporate my feedback into an example:</p>
<pre>
&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
&lt;index
xmlns:dcterms=&quot;http://purl.org/dc/terms/&quot;
xmlns=&quot;urn:temporary:uri&quot;&gt;

  &lt;title&gt;News4Humans feedOnFeeds&lt;/title&gt;
  &lt;dcterms:modified&gt;2003-09-12T23:45:37-00:00&lt;/dcterms:modified&gt; 
  &lt;source&gt;http://news4humans.com/index.adx&lt;/source&gt;
  &lt;description&gt;All the news preferred by highly evolved primates.&lt;/description&gt;
  &lt;language&gt;en-us&lt;/language&gt;
  <a href="mailto:<creator>newsfor&#64;news4humans&#46;com</creator>">&lt;creator&gt;newsfor&#64;news4humans&#46;com&lt;/creator&gt;</a>

  &lt;service&gt;
  &lt;name&gt;Latest News&lt;/name&gt;
  &lt;description&gt;A syndication feed of the 15 most recent news posts.&lt;/description&gt;
  &lt;source&gt;http://news4humans.com/feeds/index.xml&lt;/source&gt;
  &lt;format&gt;http://purl.org/rss/2.0/&lt;/format&gt;
  &lt;dc:modified&gt;2003-09-12T23:35:52-00:00&lt;/dcterms:modified&gt;
  &lt;/service&gt;

  &lt;service&gt;
  &lt;name&gt;Google Search&lt;/name&gt;
  &lt;description&gt;A SOAP interface to the Google search engine.&lt;/description&gt;
  &lt;format&gt;http://schemas.xmlsoap.org/wsdl/&lt;/format&gt; 
  &lt;source&gt;http://api.google.com/GoogleSearch.wsdl&lt;/source&gt; 
  &lt;/service&gt;

  &lt;!-- This was IndexRef &#8211;&gt;
  &lt;link&gt;
  &lt;title&gt;News4Humans Technology News Feeds&lt;/title&gt;
  &lt;description&gt;All the news preferred by highly evolved primates.&lt;/description&gt;
  &lt;source&gt;http://news4humans.com/tech.adx&lt;/source&gt;
  &lt;format&gt;urn:temporary:uri&lt;/format&gt;
  &lt;creator&gt;News4Humans&lt;/creator&gt;
  &lt;/link&gt;

 &lt;/index&gt;
</pre>
<p>Thoughts?</p>

No TrackBacks

TrackBack URL: http://appnel.com/mt/pings/127

tima points to a proposal from James Snell for what he calls The Automatic Discovery indeX (ADX). Sounds mostly reasonable,... Read More

Leave a comment

About this Entry

This page contains a single entry by Timothy Appnel published on October 14, 2003 10:45 AM.

An Example of RSS Auto-Discovery in WSIL. was the previous entry in this blog.

ADX Part Duex. is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.

Pages

Powered by Movable Type 4.2rc2-en