A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.
To request an account, ask an autoconfirmed user on Chat (such as one of these permanent autoconfirmed members).
IETF: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Sometimes people say, "Why not IETF?" Now you have two problems. More seriously: | Sometimes people say, "Why not IETF?" Now you have two problems. More seriously: | ||
* RFCs often do not match or address implementation requirements for dealing with content on the web | * RFCs often do not match or address implementation requirements for dealing with content on the web | ||
** E.g. URL parsing does not handle spaces, despite them working and being used all over | ** E.g. URL parsing does not handle spaces, despite them working and being used all over | ||
| Line 9: | Line 7: | ||
** Registries are controlled via an elaborate process; hence x prefixes everywhere | ** Registries are controlled via an elaborate process; hence x prefixes everywhere | ||
** Registries do not actually match the real world so are useless for implementors | ** Registries do not actually match the real world so are useless for implementors | ||
* text/plain | |||
* ASCII | |||
[[Category:Spec coordination]] | [[Category:Spec coordination]] | ||
Revision as of 23:14, 22 October 2012
Sometimes people say, "Why not IETF?" Now you have two problems. More seriously:
- RFCs often do not match or address implementation requirements for dealing with content on the web
- E.g. URL parsing does not handle spaces, despite them working and being used all over
- Fixing bugs fails http://lists.w3.org/Archives/Public/www-archive/2012Jun/0044.html
- IANA
- Registries are controlled via an elaborate process; hence x prefixes everywhere
- Registries do not actually match the real world so are useless for implementors
- text/plain
- ASCII