- From: Alex Milowski <alex@milowski.org>
- Date: Fri, 6 Jul 2007 07:43:07 -0700
- To: public-xml-processing-model-wg@w3.org
On 7/5/07, Henry S. Thompson <ht@inf.ed.ac.uk> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I expect that I will want to use p:http-request in a minimal way which > is not yet catered for: > > <p:pipeline> > <p:http-request> > <p:input port="source"> > <p:inline> > <c:http-request href="http://..."/> > </p:inline> > </p:input> > </p:http-request> > <p:xslt> > . . . > </p:xslt> > </p > > [In fact, I'd _really_ like an 'href' option on p:http-request, so I > can just write: > <p:http-request href="http://..."/> > ] That would mean we'd have to allow an empty sequence as input in this case and imply the GET method. This implies a different step signature and I'd rather have an separate step that works very similar that: * only does GET * has an 'href' option * has no inputs and produces an output. * handles the response very similar to p:http-request If we add an option to "shorten" the response for this, we should add that option to p:http-request as well. For example, the "detailed='no'" option would return only the XML received or the c:body element for non-XML content. -- --Alex Milowski "The excellence of grammar as a guide is proportional to the paucity of the inflexions, i.e. to the degree of analysis effected by the language considered." Bertrand Russell in a footnote of Principles of Mathematics
Received on Friday, 6 July 2007 14:43:13 UTC