> No matter what language you are using to describe schemas, an approach
> that marks the location of a schema document used for an XML namespace
> appears superior, IMHO.
That doesn't work for schema languages that do not support XML namespaces,
such as DTD, ASN.1, DMTF, etc. (I am currently most interested in the
last.)
> There is a very well established precedent that any contracts related
> to POST should appear in the app:collection.
And for GET'ing a feed or entries?
> Moreover, one can treat the proposal primarily as a way to qualify
>
> <app:accept>application/xml</app:accept>
The schema link relation does more than just tell POST'ers what it will
accept; it tells GET'ers what they can expect to receive. As I expect
readers to outnumber writers, that latter is very important.
/r$
--
Visiting Member, IBM Academy
STSM, DataPower Chief Programmer
WebSphere DataPower SOA Appliances
http://www.ibm.com/software/integration/datapower/
