RE: site-wide metadata discovery

Sorry, my mind is wandering a bit further down this path.  These are perhaps
premature questions, as if we can't do anything with robots.txt, they are
irrelevant.  But my mind's wandering anyway.  :)

So... If this is something usable, I wonder if it could be used for more
than this one discovery?  If yes, what would the best way to be to go about
it?  Would something like this work/be interesting/be useful?

Public-Feeds: myPublicFeeds.opml
Format: http://www.opml.org/spec
Title: Public Feed List

Public-Feeds: feedindex.xml
Format: http://purl.org/ocs/directory/0.5/
Title: Public Feed List

Subscriptions: mySubscriptions.opml
Format: http://www.opml.org/spec
Title: My Subscriptions

This might make it a bit easier (and clearer) to add attributes to
individual offerings, rather than trying to cram them all onto one line.
It's been mentioned a few times that this is a Bad Thing with OPML, so why
perpetuate that here if it's a feature that isn't desired?

It could also allow for multiple instances of the same data in different
formats.

Or would something like this be better:

Site-Index: default
Public-Feeds: myPublicFeeds.opml
Public-Feeds-Format: http://www.opml.org/spec
Public-Feeds-Title: Public Feed List
Public-Feeds: feedindex.xml
Public-Feeds-Format: http://purl.org/ocs/directory/0.5/
Public-Feeds-Title: Public Feed List
Subscriptions: mySubscriptions.opml
Subscriptions-Format: http://www.opml.org/spec
Subscriptions-Title: My Subscriptions

I think this might have more problems processing multiple formats, since
there is no clearly defined delimiter in between similar entries.  I also
think it looks a lot less clean than the other method.


---
Chad Everett
yahoogroups-ipyKpt5L2sG2CP6mJM4Q19i2O/[email protected]


 

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