Sam Ruby recently launched
a wiki for the Echo
Project (which needs to be renamed) which has
the following goals
- We want a weblog
authoring tool to be able to post log entries
to all sort of weblog engines.
Prerequesites:
- common API to the weblog
engine
- common markup for the entries
- common meta information such as
author, time, place, etc.
- We want to read weblogs using a variety of
means, including various transformations by
software. Prerequesites:
- standard output formats such as
RSS with a specified list of optional
well-defined modules (and plain HTML, of
course)
- common API if the queries are
allowed (eg. all log entries in a specific
time period)
Although people like
Sjoerd Visscher and
Ben Trott have mentioned why the "Echo: The
Syndication Format" is different from RSS, no one
has actually bothered to state why the why "Echo:
The Weblog API" which is supposedly the primary
reason for Echo existing would be better than the
status quo (the
MetaWeblog
API and others)
Below is a more in-depth exposition of
my earlier post describing the limitations of
current weblog posting technologies and the
problems Project Echo is supposed to fix.
Specifically, I will tackle the MetaWeblog APIs
since certain parties who are personally invested
in it have engaged in a FUD campaign and have given
the impression that there is little if anything
fundamentally wrong with it.