ECHO multi-media blogging technical issues
Because I find Sam Ruby's ECHO wiki slow at times and hard to follow for the occasional reader, I've decided to cover on this blog some of the conversations I've engaged in there and key observations as they relate to multi-media blogging.
I invite the RSS and ECHO community to correct my technical interpetation about RSS and ECHO features if they are wrong. I have no intention to stir the RSS versus ECHO pot, so please no comments or questions from that direction (because I won't answer them). I am trying to understand and communicate the technical decisions being made in ECHO that will impact multi-media bloggers.
The core design. In my opinion it is starting to look like the design of the core of ECHO is to model the core of RSS, no more, no less. Even though the semantics and syntax are different, the main idea seems to be, emulate all core RSS features and functionality based on present use.
The multiple content type issue: When it comes to entries (which are similar to items in RSS) there is some division on a entry child tag named "content". It seems some want to limit one content per entry while others like myself would like to see one or more content tags supported.
How will ECHO model the content by reference feature supported in RSS with the tag enclosure with only one content per entry? This feature is presently used by bloggers and supported by Radio.
In the case of an audioblog item (which I state here I have a bias for) in RSS, I can today put the file reference in an enclosure along with its mime type and file size. Along with that, I can have all the other attributes of item which includes a chunk of html description data that I believe would presently qualify as a second content entry type in ECHO.
The content by reference issue: To address content that is best served by referencing it's file with an URI (such as audio, video, photos), many are in support of implementing content by reference. Others believe including this feature is somehow adding a feature not needed in ECHO 1.0 even though we get this feature in RSS with enclosure.
If these issues are not addressed, in my opinion ECHO could mean less not more for audio, video and photo bloggers.
Note: I would like put some of these comments on Sam's wiki but I have not been able to reach it all afternoon.
Ref: Content types discussion at Sam Ruby's ECHO wiki: http://www.intertwingly.net/wiki/pie/content
6:41:45 PM
|