Allowing for naive/simple p:http-request

-----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://..."/>
]

Crucially, what I want _out_ of p:http-request is a sequence of actual
documents, or death, no c:http-response stuff that I don't understand
how to deal with.

So, I propose an option for p:http-request called 'detailed', default
'yes', so I can write the above as

  <p:http-request detailed="no" href="http://..."/>

Alternatively, we could change our minds from today's telcon and add
p:load to the list of things which do non-XML-media-type fixup. . .

If we _don't_ do that, then we should make clear the p:http-request
must handle file: URIs, which is not obviously the case.  What about
ftp:?

OK, I've talked myself around to the opposite position -- forget all
the above, we should add media-type-determined cleanup to p:load.

ht
- -- 
 Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
                     Half-time member of W3C Team
    2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
            Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                   URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged spam]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFGjRcOkjnJixAXWBoRAvIUAJ0WqXkDhz6xU9adBcKgouy2LZncBACeJC1f
T2f1sWyoH2rzkGFIpg/bXEI=
=ko/+
-----END PGP SIGNATURE-----

Received on Thursday, 5 July 2007 16:06:50 UTC