Aaron Swartz <aswartz@...> writes:

> Due to the good points brought up by Eric and Dan (thanks guys!) I'd like to
> try proposing the opposite:
>
> The rdf:about attribute of the channel element is a URL where a copy of the
> channel can be accessed.
>
> The reason I didn't propose this in the first place, is because it would be
> more difficult for RSS authors (I noticed Rael had some trouble generating
> the correct URIs for Meerkat, as did Moreover). However, I don't see this as
> a terribly difficult constraint.
>
> For reference, the current spec says this:
>
> > The {resource} URL of the channel element's rdf:about attribute *must* be
the
> > *same* as that found in each of the inchannel elements found in the image,
> > item, and textinput elements.
>
> Does this imply that it can be any arbitrary URL?
>
> Anyone have serious problems with this addition?

Yes (I think, I'm just rereading the recent articles on this while
updating the issues page).

I don't recall us concluding that we're breaking the connection
between <link> and rdf:about (if so, let me know, it's one of our
issues!)

If that's the case, <link> is definitely the URL of the site or
channel that this <channel> describes, therefore the rdf:about would
be too, and any examples to the contrary are just wrong.

(Simply point me to a msg# if this has already been discussed,
please.)

-- Ken