2008/12/16 Ian Hickson <span dir="ltr"><ian@hixie.ch></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
I tried following this thread but I can't find what I would need to change<br>
in the spec to address the feedback so far. If this feedback relates to<br>
requests for the spec, please elaborate on exactly what it is that should </blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">change -- thanks!</blockquote>
<div></div><div>I thought later on this topic and i arrived to conclusion that we cannot forbid or delete completely the HTML serialization, but there are no real use cases for this in server generated web pages. Even in case of user-generated content an application must parse it server-side prior to publish, and in the worst case may use the spec's algorithm to build a standard-compliant DOM tree, then serialize it producing valid XML code (therefore an application can always provid valid XHTML)</div>
<div></div><div>In my opinion, we should allow content to be sent as text/html, but HTML serialization and associated technologies (DOMDocument.write or DOMElement.outerHTML) should be marked deprecate, since there are stricter and more performant way to do same thing.</div>
<div></div><div>Giovanni Campagna</div><div></div><div></div><br>