Re these comments on the applicability of RSS, and following a f2f discussion with Andy Powell and other JISC DiVLE projects on 20-Mar:
>From: Scott Wilson [mailto:[log in to unmask]]
>Have a wander over to http://groups.yahoo.com/group/rss-dev/ and see what
>the existing RSS modules can do for you.
>You can also propose a module on the forum there and see if anyone in the
>RSS community has similar requirements or already created a module.
> From: Andy Powell [mailto:[log in to unmask]]
> I haven't... but I have often wondered if such a schema should be
> developed as an RSS module. I.e. RSS gives you the basics of the reading
> list structure - the 'readingList' module would give you the additional
> properties that you'd need over and above 'title' , 'description', 'URL'
> for each 'item' in the list.
>
> Note that there is already a DC RSS module, so some of the required
> attributes could be taken from that.
>
> Just a thought... the major advantage of using RSS as the basis, would be
> the number of existing toolkits for creating and displaying RSS channels.
I think we concluded that RSS would not do as a basis for a ReadingList schema, because the RSS content-to-presentation-channel interface cannot support the necessary attributes for ordering, structure and other 'wrapper' attributes belonging to the whole list.
However, a schema (and systems to implement it) that offered lists as RSS feeds (each identified by the course-id within institutional-namespace that would be needed anyway) would be very useful, so that a view of lists could be exposed via existing RSS channels in portals.
BTW, I would prefer the subject of the schema to be something like "Course Resource Lists", rather than "Reading Lists", to reflect the broader nature of the learning/library materials to be referenced in it; but not at the risk of suggesting this overlaps with existing schema for describing and *embedding* learning resources.
John
DELIVER Project: http://www.angel.ac.uk/DELIVER/
|