On 6 Jul 2006, at 16:46, Alex Milowski wrote:

I added Atom protocol support to the eXist XML database.  That project
is open-source and hosted at http://www.exist-db.org

Very nice db by the way. I have heard a lot of good stuff about it.

Unfortunately, it isn't documented yet.  That documentation will
be finished for a release on July 15th.

Well that's a bummer :-)

I'll announce that again when I finish the documentation.

cool!

I have no doubt that individual <service> documents can contain a lot of information. The problem is: it is mostly the same type of information: a url pointing to a feed with some info on what mime types that feed accepts. If that is all the info there is in there, then it seems to me a little expensive to create a whole new mime type for such a document. Especially as there seems to be an obvious location to place this information: the feed itself.

Sometimes a directed syntax is more appropriate.  I've tried to fit
certain kinds of information into Atom feeds and it became unworkable.

Well as far as I can see all that is needed is an <app:accept>application/atom+xml</app:accept>
extension to the atom feed document.

Do we need really *need* anything else?

I'm not convinced that this is the case for introspection but it
doesn't bother me as long as it comes back as pointy brackets.

Ah you see. I think there is a general feeling here, that this is not needed _really_. So my point is: let's remove this, and get the spec out of the door faster!

Henry

Reply via email to