> * We add a 'GET /capabilities' which returns a document describing > which features this endpoints support - a feature could be optional > because it was added in a new version or because not all > deployments would be configured with it enabled. This would allow > clients to be able to query for features, rather than having a > hard-coded understanding of which minor versions support which > features. +1 We are planning on experimenting with the nascent home document standards for Marconi rather than trying to invent our own: http://tools.ietf.org/html/draft-nottingham-json-home-02 http://datatracker.ietf.org/doc/draft-wilde-home-xml/ === Kurt | irc/twitter: kgriffs