It would be nice if the schema would be completed. I would also reccomend to seperate the schemas for differnet api calls, because some element combinations should not occur in the same api response. E. g. GET /api/capabilities only contains an api element and no nodes or ways. Representing this in one xsd file might be very difficult. --Defonion 23:36, 9 May 2012 (BST)
This XSD is not compatible to the current api
It misses the
bounds tag in the header.
I will add it asap.
--Guerda 10:39, 7 October 2010 (BST)