Necho and MetaPub appear to be the current front-runners in ProjectNameProposals.
Suggestions that there is WikiChaos suggest that those who know the answers maybe should take a break from expressing them and do a bit of refactoring for a while.
The "lots of buttons" question mentioned here earlier has been moved from UnansweredFAQ to FAQ. Essentially : no need for buttons when you've got AutoDiscovery.
There is a report of "violent flux" over whether the format should be element-centric (as in the 2003-07-01 snapshot) or "attribute-centric" (as in this version). Cast your vote at VoteOnEchoFormat.
(from 2003-07-11)
The use of Echo for BackUp is suggested. The idea of using the format for weblog archives has been around a while (RSS 1.0 can be used directly, Dave Winer did some extension stuff for RSS 2.0 which could be looked at using 'blogbrowsers' - anyone got refs?) but this doesn't appear to have come up in the Echo discussions until now.
Note also that the list of UseCases continues to grow.
On ProjectAdvertising the interesting power (law) point We don't need 50% of webloggers to convert to get 50% of the traffic on nEcho, we only need the top 5% to convert. gets the response that all we really need is the toolmaker's support.
A novel form of personal metadata is proposed by AdamRice, TasteData : Any kind of data that reveals a person's tastes, but is not content created by that person.
There is a suggestion that Related-style functionality can be included in the XML content, but this page is desperately in need of refactoring (and perhaps joining with all the other similar cases to come up with a consistent, unified SyntaxExtensionMechanism).
IsEntryIDanID is now WhatIsEntryId (Discussion on whether or not to make the id attribute in
Discussion on Identity continues.
RogersCadenhead appears to have been nominated Keeper of the Sacred Mushrooms.
The Wiki appears to have slowed down for the weekend, which suggest that many people are contributing instead of doing their day job. Viva la Revolution!
]]>Obviously this is still preliminary, but it's a great start.
]]>Source code is available and comes with 225 test cases.
]]>
Apparently it's the first time he's used RelaxNG, but he's joined the church : "...having now done one serious (albeit small) project with RelaxNG, I really REALLY wonder why anyone would use anything else?" (xml-dev)
(elsewhere, there's also an OWL ontology)
]]>The answers to that aren't too difficult, but ProjectAdvertising department need to deal with this UnansweredFAQ :
Is this what it's coming to:
Is this where it's all headed? Will we be making little buttons for each of these?
PS. There's now a FAQ entry. Essentially : no need for buttons when you've got AutoDiscovery.
This post sponsored by Dutch Cut tobacco - "stick that in your pipe and smoke it"
]]>The ListOfFeeds putting out a test version of Necho is growing. There's a link on the right for this, for future ref.
Issues relating to embedding/referring to Necho feeds in (X)HTML are being discussed at ExtraInterop.
The ViewSourceClan are discussing Design Patterns.
Some pages are begin to look like (pretty good) tutorials and glossary entries, e.g. RestAndRpc, CommonGatewayInterface. Is there a book deal here perhaps?
The RdfOwlVocabulary (for interoperability with Semantic Web systems) is probably ready for initial testing.
The EchoExampleYaml is probably ready for testing. (on teletypes?).
Despite some dissent, the current thought on EchoInDublinCore seems to be to use the DC definitions, folded into the Necho definitions (i.e. one namespace fits all).
In the lively XmlRpcDiscussion the +1, -1 and 0 votes seem to be tied, but support is growing for :
Proposal: Let's first create an API in the REST Architectural Style. The SOAP and XML-RPC APIs can then easily be derived from that.
Evangelism has found its way onto the agenda on the ProjectAdvertising page. A promising statement by
AsbjornUlsberg
I work in the Norwegian BroadCasting Corp. and we will use Echo when it's finished. I'll tell "our guys" in BBC about the format when it is mature enough, and when it is necessary for us to receive it from, or send it to them. I think "the word" will spread fast enough. I wouldn't worry about this yet.
MarkCicade appears to have got tired of typing RefactorOk and has added a page named RfOk.
The SuggestionBox is starting to fill.
"Curry" has been added to the ProjectNameProposals (fee to be decided).
]]>RSS2Necho is "...a quick and dirty implementation in php that parses a basic RSS feed and turns it into a basic necho one."
To try it out, just point your browser to http://www.tnl.net/channels/rss2necho/*****
replacing the stars with the URL for your own feed.
Here is Sam's RSS 2.0 feed thus processed.
]]>Web Service guru Rich Salz has a good article about the project at xml.com :Vox Populi: Web Services From the Grassroots.
Guru's guru Aaron Swartz has set up a blog for the same purpose as this one - Echo News (he launched about a day ahead of me, thus demonstrating that although great minds may think alike, some do it quicker).
The project without a name gets a namecheck at MSNNEWS in an article on Wikis.
Adam Curry is spending money on paid ad placements to try and discourage uptake of Necho, to back up a previous financial investment he made in an RSS-based product. Comments range from support (links please) through questioning the sense to hoary old adages.
Sam commented : " I respect that. For the record, I have no plans of stopping support my support for the multiple flavors of RSS. And I am following SSF-DEV."
SSF-DEV is the list set up by Rogers Cadenhead to tighten up the RSS 2.0 spec (Rogers also has some interesting comments re. Adam's action).
The powerful thing is that XML-RPC factors all this work so that the developer has only to deal with the data (and some function calls).
Mark Pilgrim has just posted a snippet of Python code for publishing a post using the RESTful approach in Joe Gregorio's API draft. This is followed by an example using the XML-RPC-based prototype by Georg Bauer.
Mark titles the post "On Simplicity" - in terms of simplicity, the Python code for each version is fairly similar.
This basically covers JY's point ...the developer has only to deal with the data (and some function calls).".
But there is the additional complication in the XML-RPC version of elements that bear no relation to those of the Echo language. "View source" is harder. In terms of elegance, the Gregorio version is a clear winner, the material sent down the wire is the same kind of syntax that would be sent from the server to subscribers.
It will be interesting to see how JY and other XML-RPC proponents respond.
PS. The primary criticism is that new code (xmltramp++) would be required on all different platforms, whereas XML-RPC kits are already available. This argument isn't considered too convincing by the other lobby, and it looks like the XML-RPC lobby has a new problem - timezones aren't included in XML-RPC. The saga continues.
On the Wiki : XmlRpc, XmlRpcDiscussion, SampleXmlrpc, RestAndRpc.
Voting is taking place on the EscapedHtmlDiscussion.
The XmlRpcDiscussion has gone to the vote but appears to be inconclusive at the moment - the Proposal: Let's first create an API in the REST Architectural Style. The SOAP and XML-RPC APIs can then easily be derived from that. is popular but there is dissention and the process is being questioned, notably from Mark Bernstein who says "I think we may need a summit, or a conference call, to reassure developers and remove doubts about the integrity of the process."
A subsequent proposal is Proposal: Let's first create a list of API needs, then sketch versions of each in XML-RPC and REST.
The REST version (RestEchoApi and RestEchoApiDiscuss) has an RFC and various additional material has been added in support of starting with REST.
In support of the XML-RPC approach there is now sample of a post.
Discussion on PostIdSpec is "all over the place" and still rather in the air.
New material - discussion of how to include a Blogroll has started.
My idea of linking to the blogs of Fechers (supporters of Fecho) and Fechless (those largely against) turns out to be a non-started, I can only find Dave Winer as being strongly against the project, and even he is giving nominal support.
Suggestions welcome!
]]>