Re: Requiring http/https

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alex Milowski writes:

> We need to deleted dynamic error XC0021.
>
> http://www.w3.org/XML/XProc/docs/langspec.html#err.C0021
>
> We can't require https because some implementations may not support
> encryption but we shouldn't require it to be http/https if an implementation
> can support another scheme (e.g. a GET request on a "file" scheme).

Hmm.  I agree we should make https support implementation-defined, but
I'm not sure about allowing 'file'. . .  All the options and so
much of the syntax of c:http-request and c:http-response is geared to
managing headers and encoding and so on.  What's the use case that
p:load doesn't address?

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)

iD8DBQFG3YXbkjnJixAXWBoRAoJ1AJ9lVbxNCE+GuTg+Up4xy4wCNVsgtwCfRqAJ
mECyvbBBTEQZgCylQSQAiCA=
=fVTh
-----END PGP SIGNATURE-----

Received on Tuesday, 4 September 2007 16:20:56 UTC