Re: Accepting articles and bookmarks

[Sylvain Hellegouarch <sh@xxxxxxxxxx>]

Antonio Tapiador del Dujo a écrit :
> El Miércoles, 6 de Junio de 2007 15:18, Tim Bray escribió:
>   
> > On Jun 6, 2007, at 1:04 AM, Antonio Tapiador del Dujo wrote:
> >     
> > > Hi everyone,
> > > I have an implementation issue about APP.
> > >
> > > I'm writting an APP enabled CMS [1]. This CMS accepts articles and
> > > bookmarks,
> > > among other types of content. It's not clear for me how should I
> > > announce
> > > these two types in the Service Document so any client is able to
> > > distinguish
> > > them.
> > >
> > > In a thread in Atom-Syntax [2] there is consensus about
> > > representing bookmarks
> > > as Atom Entries, so I think they should be announced as
> > > application/atom+xml;type=entry. But this would prevent clients
> > > that manage
> > > both types, like Flock browser [3], to know where both types of
> > > collections
> > > are.
> > >       
> > Couldn't you have two collections, one named "Articles" and the other
> > "Bookmarks"?  -Tim
> >     
>
> Yes, this is what I have right now.
> My point is that the client is able to automatically connect the blogging 
> module with the Articles collection(s), and the favorites module with the 
> Bookmarks collection(s), after fetching the Service Document.
>   

This is more a convention than anything else IMO. I don't think having 
one media-type type parameter per use case is reasonnable. Maybe having 
a rel="" attribute within the app:collection could be a nice idea in 
such case.

<app:collection rel="bookmark">...</app:collection><app:collection 
rel="articles">...</app:collection>

But then again this is not something the WG can decide anyway and it 
will come out after some experience in the field of the common use cases 
like yours. Browser and more generally APP client vendors will 
eventually sort this out.

- Sylvain