- From: Bjoern Hoehrmann <derhoermi@gmx.net>
- Date: Tue, 27 May 2008 18:21:16 +0200
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: "Web API WG (public)" <public-webapi@w3.org>
* Julian Reschke wrote: >- If the URL parameter can be a IRI, then somewhere later on we need to >state that it needs to be transformed to a URI before it's put on the wire. Actually that is for the HTTP specification to define, which right now does so implicitly by allowing only URIs. Restating requirements usually leads to specifications stating conflicting requirements, it's best not done at all, except in informative notes clearly limited to the known cases (e.g., "Note: Because HTTP/1.0 and HTTP/1.1 allow only URIs as request URIs, user agents will transform the IRI to an URI when creating the request message.", though I would not add this). -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de 68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
Received on Tuesday, 27 May 2008 16:21:52 UTC