Current discussion topics:

See also: SyntaxExtensionMechanism, EchoExample, EchoSchema, EchoFeed, EchoInDublinCore, EchoRssExample

[TimBray] I would recommend that the specification take the following form:

[GeorgBauer] One more idea: I would like to get a specification much in the line of the W3C HTML specs. A DTD (or Schema or whatever formal definition you like), a commented DTD (or Schema or ... you get it) and maybe something like they did with the Creative Commons License: put a boiler page in front of it where you state what you are meaning. So people could dive into the format in layers: first contact is the "read this and you know what we want" and formal specifications later.

And, of course, build a validator for this new format as soon as the first tag is available. Better have an official validator up and running as soon as possible.

[WWW] I agree with Tim and Georg's suggestions but would also recommend that the specification also includes material how it is intended to be used with other models and formats (use namespaces is not enough). Wikis and Creative Commons are examples. It could just be as simple as saying that e.g. a postID corresponds to a topic id (in XFML), a resource (in RDF) or a primary key (in RDBMS). Personally I strongly believe we would benefit in the long run from a formal definition (UML or OWL), see ExtraInterop and RdfAndEcho. Validator as soon as possible - a very big yes!

See SyntaxExtensionMechanism

[DougRansom RefactorOk] I would like to see the separation of items from how we get them. I suggest WSDL be used to specify a couple interfaces to get new items. A pull interface would give new items since some checkpoint (similar to etag in http) and possibly older ones as well. Not WSDL does not necessarily imply soap. A push interface would push new items to subscribers via HTTP, SMTP, or some P2P protocol. I think a huge win would be to get away from everyone reading the items directly from the publishers web server -- it would be nice to have syndication occur at the application protocol layer or at the soap layer somehow. Then all sorts of people could publish content without requiring large bandwidth available, or even a fixed ip address.

Old poll: