2006/4/26, David M Johnson <[EMAIL PROTECTED]>:
> On Apr 24, 2006, at 1:16 PM, James M Snell wrote:
> > http://www.intertwingly.net/wiki/pie/PaceMediaEntries
> >
> > The WG seems to be in agreement that the current definition of Media
> > Collections is horribly broken.
>
> Actually, the draft 8 definition works for me. The blog server I'm
> working on, Roller, every blog has a collection of entries and a
> collection of uploaded files. And currently, Roller does not store
> any metadata for uploaded files.

What are you returning in the "media collection feed" in atom:title,
atom:id, atom:updated, atom:author?
atom:title and atom:updated can quite easily be built from the file
name and "mtime", if you store them as files on a file system of
course; but for atom:id and atom:author?

> > The key advantage of this approach is that it works seamlessly with
> > existing *casting style applications.  It also resolves all of the
> > issues that have been raised in relation to media collections.
>
> The draft 8 approach supported podcasting too.

So using atom:content is "supporting podcasting"? That's good news.

> So, for those that are OK with media collections as they stand today,
> what are the advantages of your proposal? Seems to me the advantages
> are: a more consistent and easy-to-understand model and the ability
> to edit metadata for media files. I'm +1 to both of those.

As I already said, I'm not sure using an enclosure and an additional
atom:link/@rel is "a more consistent and easy-to-understand model".
I haven't had time yet to write an alternate Pace, I'll try to do it
tomorrow, or at least before this week end…

> Question: without media-types, how do clients discover which types
> the different collections allow?

James told me this could very well be supported by an extension (note
that there would then be a primary collection for each collection type
– defined by the extension –, and a "primary primary" collection –
defined by the APP –; it works for me, just thought it should be said
;-) )

--
Thomas Broyer

Reply via email to