11754 2011-01-14 08:29:51 +0000 Should clearly indicate that Web authors don't need to bother to make their content polyglot if they don't know they have a use case 2011-08-04 05:07:35 +0000 1 1 1 Unclassified HTML WG LC1 HTML/XHTML Compatibility Authoring Guide (ed: Eliot Graff) unspecified All All RESOLVED FIXED P2 normal --- 1 hsivonen eliotgra ayg eliotgra mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 44343 0 hsivonen 2011-01-14 08:29:51 +0000 Authoring polyglot documents is harder than authoring either monoglot HTML5 or monoglot XHTML5 documents. In particular, it is a lot harder than authoring monoglot HTML5 documents. Thus, if Web author makes his/her documents polyglot when there's not a real need to do so, the Web author ends up doing useless hard works, which isn't nice. Considering the history of XHTML advocacy pushing Web authors to try (and most often fail) to make their text/html content XML-compatible without a good reason, I think there's a real risk of history repeating and authors jumping through hoops they don't need to jump through if "Polyglot Markup" is published without better guidance about its applicability. After all, if the W3C publishes something, readers will assume that the W3C is endorsing whatever is described in the publication without reservation. To avoid giving the appearance that the W3C advices Web authors in general to write polyglot documents (which in the general case leads to extra work without a return on the investment), please include text in the introduction that communicates the idea that polyglot markup is a solution to abnormal needs and if a Web author hasn't personally concluded that (s)he has use a case that is best addressed by polyglot markup, the Web author is most likely best off using monoglot HTML5 or XHTML5. 45425 1 eliotgra 2011-02-12 00:42:02 +0000 The Editor's Draft of 11 February states the following in the Introduction: ]] All web content need not be authored in polyglot markup. Polyglot markup is ideal for publishing when there's a strong desire to serve both HMTL and XML tool chains without simultaneously having to maintain dual copies of the content: one in HTML and a second in XHTML. In addition, a single polyglot markup output requires less infrastructure to produce than to produce both HTML and XHTML output for the same content. Polyglot markup is also be beneficial when lightweight processes—such as quick testing or even hand-authoring—are applied to content intended to be published both as HTML and XHTML, especially if that content is not sent through a tool chain. [[ I believe that this fulfills the requirements of this bug and so I have resolved it. Thanks for your help, Eliot 53162 2 mike 2011-08-04 05:07:12 +0000 mass-move component to LC1 53201 3 mike 2011-08-04 05:07:35 +0000 mass-move component to LC1