Michael A. Puls II wrote: > [...] > If it doesn't solve any problem ditch the RFC. Might I respectfully suggest the opposite approach ? If the RFC does not cause any intractable problems, then adopt it without hesitation. Reasoning : RFCs were here long before HTML 5 was ever dreamed of, and will be here (perhaps in a modified form) long after HTML 5 is dead and forgotten. They do not exist as an academic exercise, but rather to /ensure/ interoperability (which is one of the primary raisons d'etre for HTML 5). Therefore, if an RFC makes a recommendation, HTML 5 (and all similar standards) should adopt that RFC as a given. If this results in an intractable problem, then that problem should be raised with the relevant RFC authorit{y|ies) rather than being swept under the counter and the offending RFC ignored. Philip TAYLORReceived on Thursday, 2 April 2009 09:38:24 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:40:29 GMT