RE: [syndication] How the newsreader see the domain attribute of the category element

["Danny Ayers" <danny666@virgilio.it>]

Hello again Emmanuel,

> > I'm trying to implement some sort of spec related to eLearning.
> What I'd like
> to do in
> > the long run, is to see if a quiz could be build in a weblog
> and dissemated by
> RSS 2.0.
> > Its a long shot.

The dependence on the reader interpretation is the tricky bit for sure - you
could define your own module specifically for quizzes quite easily, but
having it render correctly at the receiving end is another matter.

> > Anyway, here's the crux of my question.
> >
> > What I have in the back of my mind is how the newsreader see
> the value of the
> > domain attribute. Are they automatically inferring that its an
> url and create
> a link that
> > have for value the value of the category tag?
> >
> > For example I don't want:
> > <category domain="1">question</category>
> > Parsed in a newsreader as:
> > <a href="1">question</a>

Who knows how it will be interpreted? It isn't defined rigidly enough for
aggregators to take a consistent approach. This is one of the many reasons
I'd like to see the RDF model (even if not necessarily RDF/XML - it can be
used with RSS 2.0) become the dominant one within aggregator design. The
framework makes it easy to say (and communicate) things unambiguously. Even
if there isn't a rendering specifically for the element 'category', this
term might be defined as a subclass of a commonly know class (such as
dc:subject) and the application would be able to choose an appropriate
default. You could even use emm:quiz!

fwiw, I just had a quick look and Movable Type uses
<dc:subject>Blogging</dc:subject>
but this doesn't appear to be rendered at all in Amphetadesk.

Cheers,
Danny.