Re: issue: collection typing

[Robert Sayre <mint@xxxxxxxxxxxxxxx>]

Dare Obasanjo wrote:

> On targetting each vendor individually:
> ---------------------------------------
>
> TypePad uses Atom for editing category lists, typed
> lists and photo albums. They have come up with a
> mishmash of extension elements some of which are taken
> from existing RSS extensions and some that are in a
> SixApart specific namespace. They have also added at
> least one new URI end point which isn't in the spec
> (CategoryURI) although I notice there's an open Pace
> about it. 
>
> It is highly unlikely that a vendor that wants to
> implement similar APIs for their own service will
> simply copy SixApart's extensions wholesale especially
> if their implementation of some of these concepts
> differs slightly from SixApart's.  

You usually stress that you don't represent Microsoft (and in the IETF, 
you don't, at least officially), but perhaps you could clue us in about 
MSN Spaces requirements. MSN Spaces is one of the more featureful 
offerings I've seen, so it's a good test.

Often, your arguments come off as arguments against the goals of the WG. 
Doing nothing is always a valid choice, but I'd like to hear feature 
requests from you--"this is what I need to make the APP work for me".

OTOH, arguing about ontologies for Photo Albums, "type lists", and 
"structured blogging" seems unproductive. These will tend to vary from 
vendor to vendor. I think we should focus on extension points and basic 
tasks. For example, a client ignorant of the MSN Spaces photo album 
features might still be able to interact with it as a collection of 
"simple resources". Does that make sense?

So, how can we make this work?

Robert Sayre