Re: RSS 1.1

A couple of late evening comments to my late first look at "RSS 1.1"

- I don't think that it is a good ideas to have urls as literal, use
named resources
- what's the link element for? I assume when used as property of Image
if should describe the link on that image, but what's the good as
property of Channel or Item?
- the image property has an xml:lang attribute, but this is not legal in
RDF as only plain-literals may have an xml:lang
- the image property is missing in the ontology (at least its not there
with a label)
- +1 for capitalizing all classes
- Why can a channel have only one title? I'm used to give them a title
property for every available language, same for description - and why
shouldn't multiple images be possible?

Regarding the design of the spec I would prefer to start with a
serialization independent definition of the ontology, and define the
concept of "RSS - Document" in a second section. This is to make clear
that usage of the RSS-Vocabulary is not limited to RSS Documents, does
not necessarily imply some specific serialization and is independent of
XML. By contrast an RSS-Document is an XML Document following the
defined syntax which happens to interpretable as RDF/XML as a graph
using RSS - like this people only interested in the vocabulary would not
be discouraged by irrelevant details.

reto






 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/rss-dev/

<*> To unsubscribe from this group, send an email to:
    [email protected]

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