The RestEchoApiDiscuss is a little divided mostly on how many of the HTTP verbs to use. The choice is to follow Tim Bray's proposal for an HTTP and XML only protocol using HTTP's GET and POST methods, or Ken MacLeod's proposal for an HTTP and XML, and any other content type, protocol using HTTP's GET, PUT, POST, and DELETE methods. Or something else... For the current status, see Joe Gregorio's draft RFC (version 5).
The problem with "Atom" appears to centre on :
ATOM
SOFTWARE FOR TELECOMMUNICATION NETWORKS CONSULTING SERVICES FOR TELECOMMUNICATION NETWORKS
78156387
Skyoptix, Inc. 125 Half Mile Road Red Bank NEW JERSEY 07701
Attorney of Record Orville R. Cockings
See AtomTradeMarkConflicts. Has anyone actually tried to contact Skyoptix?
If you want to help sort the name thing out, please start by reading ProjectNameProcess and ProjectNameGuidelines. There is now a NameFinalVote page, though it isn't clear how this (and a 15th August deadline) fits in with the ProjectNameProcess.
[Ed. I've just added "Dada" to ProjectNameProposals as it's data gone strange.]
It looks like some progress is being made on ContentProblems, which is mostly about dealing with fragments in content. Several examples have been provided showing possible solutions (one includes an SVG fragment, which is refreshing).
An interesting quote has appeared in the SuggestionBox : "Maybe I should stick my nose in and suggest a way to specify the location of an XSLT stylesheet at the top of the feed, so we don't have to do this again in another five years."
[Ed: Will we still be using XML in five years time? Won't we have "data pills" instead..?]
Recent Comments