This issue is more difficult than it seems. We're making RDF assertions,
that much is clear. The question then becomes about what. If we make them
about items with strange IDs or URIs, the problem then becomes that while,
we're using RDF, we're not making generically useful assertions -- an RDF
application has to know that if:
an assertion is made about an item
that item has a link to a URL
then that assertion is valid for that URL

The question is: How much of an issue is this? Is it a reasonable assumption
that an RDF application using RSS would be smart enough to realize this?

The other question is: What does 0.9 do? As far as I have seen, 0.9
assertions (and I use that term loosely) are really only valid for the scope
of the RSS file, or related usage. That is, I've never seen an RSS app
(although I plan to create one for RSS 1.0) that provides the RSS metadata
for a specific URL, so that you could enter in the address of a news article
and get back a title or description. Most only provide the RSS information
in the context of a specific channel. Thus, I think the ID-type usage would
be valid in this situation.

--
Aaron Swartz | me@... | http://www.aaronsw.com