The "high level" view of your standard media management object model is shaping up nicely. The only point I'm having a hard time understanding and need clarification is "The goal of a standard media management object model is to enable end-users to have their media in ONE PLACE".
In what context do you mean "ONE PLACE"?
I trying to understand what you mean by "ONE PLACE" and since you capitalized it must be inportant.
Do you mean moving the media file(s) away from the locked up 'on-line storage system' to the public Internet 'on-line storage system'. In that context "ONE PLACE" would mean public Internet.
Or does "ONE PLACE" mean one server for all my media. audio files, video files, etc.
The standard media management object model job should be to separate media storage from blog/publishing system content/html storage.
In the near future bloggers will be faced with many choices to where to store their media files on the open cloud.
Maybe vendor X has the interface I need to send audio files to my audio blog from my WIFI notebook and vendor Y has the proper protocol I need to embed photos in my blog from my cell phone camera. I also may have my own server outside my firewall that stores different media files that I upload from my home PC.
At the end of the day, my blog doesn't care where the media is. As far the blog is concerned, "my media" is no different than the media in all the other users/systems. That's the magic of the blog. Hypertext and html pull "all the media" together to make that difference transparent. The magic is performed by the blogging client tools.
Media in "ONE PLACE" in this context sounds to much like 'lock in'.
The media management object model shouldn't care if the media is my media or their media or where on the open cloud/sky the media file is.
