RE: Feed List Format

> Actually figure out what we want, before we decide how to implement it.
>   This sounds better in theory, but often leads to paralysis by
> analysis.  If we go this way, the right next step is exactly what Dave
> Winer previously suggested: more use cases.  The end result may end up
> being OPML.  It may not.  If we go this route, such a decision is
> premature.

This sounds eminently reasonable ;-)

A use case I'd like to add in passing is for the user, when presented with a
list of channels, be able to click on a 'creator' link which will yield info
about the channel author from their FOAF profile, along the lines of
Technorati profiles, FOAF Explorer or simply an exhaustive list of data
along the lines of the semantic planet crawler:

http://www.technorati.com/profile/rubys/3038/3a919498e748ce9fcc6e2523c03cef9
9

http://xml.mfd-consult.dk/foaf/explorer/?foaf=http%3A%2F%2Fwww.ecademy.com%2
Fmodule.php%3Fmod%3Dnetwork%26op%3Dfoafrdf%26uid%3D1

http://www.semanticplanet.com/sources/91/

btw, I just looked at the OCS spec after reading the DataModelRequirements,
and there's a spooky amount of fit. OCS *syntax* does look over the top, but
most of the ugly seems to be around the containers (Alt, Bag) which could
probably be simplified following the updated W3C specs. I'm sure Ian Davis
(the OCS maintainer) would be willing to take on board any suggestions.

http://internetalchemy.org/ocs/directory/0.5/

http://www.intertwingly.net/wiki/fdml/DataModelRequirements

Cheers,
Danny.


 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/