On 2/11/06, Reto Bachmann-Gmür <[EMAIL PROTECTED]> wrote: > > Hi Danny
Hi Reto > No sure what you are referencing to with app:collection, just another > name for x:Directory? Yes. > Spontaneously I don't see the motivation for x:Resource, rdf:Resource instead? and I'm > wondering if rdf:type couldn't be used instead of x:format : I'd wondered about that - having a class :Rss1.0Feed, :AtomFeed etc. Still not really sure how you reconcile the resource/representation thing though: what if the instance of :AtomFeed also has a HTML representation? > But I'm unsure about the requirements: > > - Is blogroll / directory ordered? Not sure, I don't think there's any kind of consistent pattern out there, so I'd be inclined to say no (unless an ordering was expressed some other way). > - Should the items be allowed to have titles that are specific to their > function in the directory, i.e. should it allow to reference to a > resource as "my best friend's blog" without asserting that this is the > title of that resource? Hmm, tricky. The person that creates the list is usually pretty important. But maybe that could be handled on top (if required) of a title kind of property. > I was doing something a bit similar recently when implementing webdav > support in KnoBot, the vocabulary is minimalistic: Resource (again), > Collection, member, no ordering, no role-titles. Ah, webdav, why do I always forget webdav..? ;-) How did you end up doing it in KnoBot? Cheers, Danny. -- http://dannyayers.com
