- From: Bjoern Hoehrmann <derhoermi@gmx.net>
- Date: Wed, 13 Oct 2010 00:11:03 +0200
- To: blueroofmusic@gmail.com, msweet@apple.com
- Cc: www-archive@w3.org
Hi,
http://www.ietf.org/id/draft-mcdonald-ipps-uri-scheme-00.txt in
section 7 notes:
IPPS URIs MUST use [RFC3986] encoding, as do their equivalent HTTPS
URIs [RFC2818]. Characters other than those in the "reserved" set
[RFC3986] are equivalent to their ""%" HEX HEX" encoding.
This does not work as a definition as the %xx encoding encodes octets,
not characters. You would have to specify the character encoding to
encode characters.
In Appendix A you have
Author/Change controller:
IEEE-ISTO Printer Working Group (http://www.pwg.org)
As this is a standards track document IESG approval is required and per
RFC 4395 the change controller would thus be the IESG, see section 5.3
of RFC 4395.
In section 6 it would be useful to clearly identify the registry, e.g.
by referencing the BCP number for RFC 4395.
In section 4.5 the ABNF lacks two closing "]".
regards,
--
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
Received on Tuesday, 12 October 2010 22:11:43 UTC