- From: Dave Reynolds <der@hplb.hpl.hp.com>
- Date: Mon, 08 May 2000 17:00:59 +0100
- To: xml-dist-app@w3.org
One of the attractions to me in using an XML-based protocol is that it should be easy to exchange information already encoded in XML. For example, as part of a command I might like to be able to pass a block of metadata encoded in RDF, or a signed assertion encoded using XMLSignature, or an embedded web document fragment in raw XML. To be clear, I'm not talking about just sending such an XML packet over HTTP (an easy job) I'd like the packet to be one of a number of parameters to a service and to use some RPC mechanism to encode the other parameters. The protocols I've looked at so far (XML-RPC, SOAP 1.0 and 1.1) provide serialization algorithms for conveying standard datatypes over XML. They don't seem to include any hooks for including a datatype to represent an embedded XML node tree which I could include within the payload. Soap 1.1 would *allow* me to define such a thing by using the encodingStyle attribute but doesn't seem to have such a thing out of the box. I guess I'm looking for an <embedded-xml> element which would prevent the deserialization algorithm descending further and would expose the XML sub-tree to the client/server as a DOM (or DOM2, or jdom or whatever) node for further parsing. So: 1. Is this a reasonable sort of requirement? Am I just unusual in even trying to do this! 2. Is there some capability along these lines already available or planned? Dave Reynolds ------------------------------------------------------------------ Hewlett-Packard Laboratories | Phone: +44-117-3128165 Filton Road, Stoke Gifford | FAX: +44-117-3128924 Bristol BS34 8QZ, UK | der@hplb.hpl.hp.com
Received on Monday, 8 May 2000 11:59:41 UTC