rob yates wrote:
All,
I wanted to branch off the other thread as rather than discuss the
merits of PaceCompoundEntries I want to see if the group feels there
are implementation problems / limitations with the current treatment
of media collections as described in draft 7. I have two questions
a) does the group feel that there is an implementation problem in
draft 7. The gory details are below, copied over from the other posts.
I have also attached a couple of suggestions from Joe on how to fix.
Yes. I've run into the same problem.
b) does the group feel that there is a need to have editable meta data
associated with entries in MEDIA collections,
Absolutely. This is essential for my applications and I don't like
that I've been doing this without any standard way to edit the
metadata.
Maybe I'm off-base here, but I really need to be able to edit the
metadata for entries or *feed* in a standard and uniform way--regardless
of the content of the entry. Just because someone posts a binary
to a feed doesn't necessitate that how the metadata is handled or
the wants of the application/user is any different.
For example, just as I might want to add an [atom:]category element
to an entry, I might want to do that for the feed itself. Certainly, I
want to be able to change the title of a feed in a similar way as I
change that for an entry (binary or textual).
In the end, having a differentiation between media collections and
entries for this doesn't help me. I've gotten myself to the
point where *everything* is a media collection--including those
that just contain entries. I realize that is a bit different
from the idea of collections being promoted by the spec, but it
doesn't look like a non-compliant use.
The back-end database I use (eXist) lets me store both
binaries and XML side-by-side in a single collection. Hence the
distinction isn't useful for me. I understand how it can be
useful for other implementation choices and I just want
and inclusive model. That is, I'd like to remove the
distinction from my implementation and be able to say that
it is compliant.
--Alex Milowski
