Re: shared feed lists

"tappnel" <[email protected]>
Newsgroups gmane.network.syndication.discuss
Message-ID <[email protected]>
--- In [email protected], "Bill Kearney" <ml_yahoo@i...> wrote:
 
> Right now Syndic8 publishes my personal lists idea.  We can easily implement any
> new format for this as it's largely template driven.  I'd raised the question on
> aggregators as to how readers would react to new namespaced elements being 
used
> in OPML files.  Intial feedback seems to indicate no readers had trouble seeing
> past the added data.
> 
> As to ADX, it's as useful as anything else I suppose, here's a list in it's
> format:
> http://www.syndic8.com/genfeed.php?Format=adx&UserID=wkearney99&List=8

Very nice.
 
> Got a few rough spots, all of which are easily fixed if sufficient interest
> develops.  

Agreed.

> I'm also not entirely clear on what the IndexRef is supposed to be pointing
> toward.   Is it pointing to itself?  Or to another file?  Sort of like
> rdfd:seeAlso?  If so, it'd be helpful to allow use of a type attribute of some
> kind to let the consuming program know what format the external document is
> using.  Or is this expecting to be an ADX-only world?  (not that there's
> anything wrong with that idea).

Taking into context that James was transcribing my example in WSIL[1], IndexRef is a 
link to another directory/index. The equivalent of the <link> element in WSIL. This is 
not limited to itself.

In my feedback I note that IndexRef alone misses the opportunity to provide addition 
meta data information such as type (as you point out) or a title/name. This is also an 
important allowance for putting such a format into blogroll use. This would also 
provide the ability for large site such as Yahoo! or Amazon to create a distributed 
directory heirarchy. 

Hope that helps.

<tim/>

[1] http://www.mplode.com/tima/archives/000319.html


 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.