RE: seeAlso

> Basically what could work here is to define a "list of feeds" class,
> say http://example.org/feeds#list and then say:
>
> <f:list xmlns:f="http://example.org/feeds#" rdf:about="">
>   <rdfs:seeAlso rdf:resource="http://example.com/myfeed.rdf"
>   dc:title="My Feed"
>   rdf:type="http://purl.org/rss/1.0/channel"/>
>   <rdfs:seeAlso rdf:resource="http://example.com/mycomments.rdf"
>   dc:title="My Comments"
>   rdf:type="http://purl.org/rss/1.0/channel"/>
> <f:list>
>
> There you go, an extensible feed list format, compatible with existing
> infrastructure... :)

Neat, and I don't even think you need the new class:

<channels 	xmlns="http://purl.org/ocs/directory/0.5/#"
		xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
		xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
  		xmlns:dc="http://purl.org/dc/elements/1.1/">
		rdf:about="">

	<rdfs:seeAlso rdf:resource="http://example.com/myfeed.rdf"
		dc:title="My Feed"
		rdf:type="http://purl.org/rss/1.0/channel"/>

	<rdfs:seeAlso rdf:resource="http://example.com/mycomments.rdf"
		dc:title="My Comments"
		rdf:type="http://purl.org/rss/1.0/channel"/>

</channels>


(I can't find the OCS RDFS - but I don't think Ian would mind this range for
channels ;-)


 

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