- From: David Dorward <david@dorward.me.uk>
- Date: Tue, 21 Nov 2006 13:36:47 +0000
- To: www-html@w3.org
On Tue, Nov 21, 2006 at 09:46:59AM +0900, Karl Dubost wrote: > Why asking so many questions to hide answers? ;) I'm not trying to hide answers, I'm seeking them. They seem to be very difficult to find. > For the last bit which is unrelated to the issue. Specifications will > always be a land of interpretations. Perfection doesn't exist. We can > try to remove ambiguities, to make things simpler to understand, etc. > but there will be always room for interpretation. Maybe so, but XHTML is served as text/html on a great many websites. I believe effort should be made to remove as much of the ambiguity and add as much clarity as is possible to the spec for doing so. This section of the specification has raised a number of questions in my mind. Everybody I've discussed this with has had equal difficulty in understanding it. Clearly it is not up to the standard we should demand from a specification. > So I have a precise question: Did you have a practical real problem > created by the section C14? I'm trying to understand the specification *before* it causes me a problem (I got pushed at project management training a few weeks ago, they were very keen on managing risk before it turned into problems). Do you have a practical, real world problem in serving XHTML as text/html that is solved by C14? Presumably there is a use case for it in the HTML Working Group's archives. > Please give a pointer to a document online where you give your > interpretation of the problems, then we can start to discuss about > the C14. I believe that my interpretation of the problems can be inferred from my previous emails on the subject. Even if they do not, then I still believe they would make a good starting point for discussion. -- David Dorward http://dorward.me.uk
Received on Tuesday, 21 November 2006 13:37:03 UTC