Cart
[Home] [By Thread] [By Date] [Recent Entries]
The problem is that different consumers require different representations, and simply supplying a URL doesn't address this. Is anyone interested in discussing a simple protocol for managing different representations over an HTTP-based URL? Just off the top of my head, I'm thinking something on the order of posting a desired MIME type and receiving the appropriate document. Thus, my application might request a schema, but when I can't get it to work I'd use my dev environment to request the HTML documentation. Or perhaps the URL returns a list of supported representations and their individual URLs. In the absence of a common understanding, we'll be doomed to struggling with ad hoc implementations. *************************************************************************** This is xml-dev, the mailing list for XML developers. To unsubscribe, mailto:majordomo@x...&BODY=unsubscribe%20xml-dev List archives are available at http://xml.org/archives/xml-dev/ ***************************************************************************
|
