<?xml version="1.0" encoding="UTF-8"?><rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
> <channel><title>Comments on: HTML5 Markup Language first draft published</title> <atom:link href="http://www.webdirections.org/blog/html5-markup-language-first-draft-published/feed/" rel="self" type="application/rss+xml" /><link>http://www.webdirections.org/blog/html5-markup-language-first-draft-published/</link> <description>Just another WordPress weblog</description> <lastBuildDate>Thu, 11 Mar 2010 01:41:33 +0000</lastBuildDate> <generator>http://wordpress.org/?v=2.9.2</generator> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <item><title>By: Стас</title><link>http://www.webdirections.org/blog/html5-markup-language-first-draft-published/comment-page-1/#comment-220932</link> <dc:creator>Стас</dc:creator> <pubDate>Sun, 14 Feb 2010 07:56:52 +0000</pubDate> <guid
isPermaLink="false">http://www.webdirections.org/?p=1243#comment-220932</guid> <description>But most of the document was automatically extracted from the (then-) current draft of HTML5</description> <content:encoded><![CDATA[<p>But most of the document was automatically extracted from the (then-) current draft of HTML5</p> ]]></content:encoded> </item> <item><title>By: Mozilla Standards Blog &#187; Blog Archive &#187; On Letting Specifications Bloom&#8230;</title><link>http://www.webdirections.org/blog/html5-markup-language-first-draft-published/comment-page-1/#comment-143624</link> <dc:creator>Mozilla Standards Blog &#187; Blog Archive &#187; On Letting Specifications Bloom&#8230;</dc:creator> <pubDate>Tue, 10 Feb 2009 14:32:53 +0000</pubDate> <guid
isPermaLink="false">http://www.webdirections.org/?p=1243#comment-143624</guid> <description>[...] after it was released, it was received with cautious optimism, but also some confusion. Was it for authors (who would write web pages), or for implementers of tools? Within the listserv, [...]</description> <content:encoded><![CDATA[<p>[…] after it was released, it was received with cautious optimism, but also some confusion. Was it for authors (who would write web pages), or for implementers of tools? Within the listserv, […]</p> ]]></content:encoded> </item> <item><title>By: MIchael(tm) Smith</title><link>http://www.webdirections.org/blog/html5-markup-language-first-draft-published/comment-page-1/#comment-109611</link> <dc:creator>MIchael(tm) Smith</dc:creator> <pubDate>Tue, 25 Nov 2008 05:22:34 +0000</pubDate> <guid
isPermaLink="false">http://www.webdirections.org/?p=1243#comment-109611</guid> <description>As Lachlan points out, he&#039;s already been working on a editor&#039;s draft of an authoring guide -- &quot;The Web Developer’s Guide to HTML 5&quot; -- and the document I&#039;ve put together  -- &quot;HTML: The Markup Language&quot; -- has a quite different purpose than that guide.  My draft has as its primary purposes to precisely define what a conformant HTML document is, and to succinctly define the semantics of the set of HTML elements and attributes. And to be clear: The only Recommendation-track document that the group thus far as agreed to publish as an official deliverable of the group is the existing HTML5 specification that Ian Hickson is editing. There has been no decision by the group to take on any other Recommendation-track document as a deliverable (not the &quot;HTML: The Markup Language&quot; draft, nor the &quot;The Web Developer’s Guide to HTML 5&quot;, or anything else). I think both documents were put together in the same spirit of producing something concrete for us to discuss (in the case of &quot;The Web Developer’s Guide to HTML 5&quot;, a detailed, comprehensive, user-friendly how-to guide to HTML5 for authors and Web developers; and in the case of &quot;HTML: The Markup Language&quot;, a small, very narrowly-scoped spec just for producers of HTML content who primarily just need a precise definition of what a conformant HTML document is, but who don&#039;t want or need implementation-conformance details for how a browser or other consumer of HTML content must behave.As far as how the &quot;HTML: The Markup Language&quot; was put together: Parts of it are manually edited and parts of it are generated/copied as part of an automated build process; the generated parts are built from the same Relax NG schema used by the validator.nu HTML conformance checker, and some parts are copied over from the existing HTML5 draft (for instance, all of the Example sections). There are some more specific details:http://lists.w3.org/Archives/Public/public-html/2008Nov/0324.html</description> <content:encoded><![CDATA[<p>As Lachlan points out, he’s already been working on a editor’s draft of an authoring guide — “The Web Developer’s Guide to HTML 5″ — and the document I’ve put together  — “HTML: The Markup Language” — has a quite different purpose than that guide.  My draft has as its primary purposes to precisely define what a conformant HTML document is, and to succinctly define the semantics of the set of HTML elements and attributes. And to be clear: The only Recommendation-track document that the group thus far as agreed to publish as an official deliverable of the group is the existing HTML5 specification that Ian Hickson is editing. There has been no decision by the group to take on any other Recommendation-track document as a deliverable (not the “HTML: The Markup Language” draft, nor the “The Web Developer’s Guide to HTML 5″, or anything else). I think both documents were put together in the same spirit of producing something concrete for us to discuss (in the case of “The Web Developer’s Guide to HTML 5″, a detailed, comprehensive, user-friendly how-to guide to HTML5 for authors and Web developers; and in the case of “HTML: The Markup Language”, a small, very narrowly-scoped spec just for producers of HTML content who primarily just need a precise definition of what a conformant HTML document is, but who don’t want or need implementation-conformance details for how a browser or other consumer of HTML content must behave.</p><p>As far as how the “HTML: The Markup Language” was put together: Parts of it are manually edited and parts of it are generated/copied as part of an automated build process; the generated parts are built from the same Relax NG schema used by the validator.nu HTML conformance checker, and some parts are copied over from the existing HTML5 draft (for instance, all of the Example sections). There are some more specific details:</p><p><a
href="http://lists.w3.org/Archives/Public/public-html/2008Nov/0324.html" rel="nofollow">http://lists.w3.org/Archives/Public/public-html/2008Nov/0324.html</a></p> ]]></content:encoded> </item> <item><title>By: JimJ</title><link>http://www.webdirections.org/blog/html5-markup-language-first-draft-published/comment-page-1/#comment-108065</link> <dc:creator>JimJ</dc:creator> <pubDate>Thu, 20 Nov 2008 17:49:42 +0000</pubDate> <guid
isPermaLink="false">http://www.webdirections.org/?p=1243#comment-108065</guid> <description>But most of the document was automatically extracted from the (then-) current draft of HTML5, so ... it is the same words as the mainline draft -- just a much smaller subset, so you can focus on the markup portions.</description> <content:encoded><![CDATA[<p>But most of the document was automatically extracted from the (then-) current draft of HTML5, so … it is the same words as the mainline draft — just a much smaller subset, so you can focus on the markup portions.</p> ]]></content:encoded> </item> <item><title>By: Lachlan Hunt</title><link>http://www.webdirections.org/blog/html5-markup-language-first-draft-published/comment-page-1/#comment-108050</link> <dc:creator>Lachlan Hunt</dc:creator> <pubDate>Thu, 20 Nov 2008 16:28:46 +0000</pubDate> <guid
isPermaLink="false">http://www.webdirections.org/?p=1243#comment-108050</guid> <description>Just to be clear, that document is only an editor&#039;s draft and it has only been put forth as a proposal.  It&#039;s not yet on the recommendation track, and it&#039;s not yet clear if it ever will be.  It&#039;s also questionable whether it can actually be consisdered &quot;a web authors guide to HTML&quot;, because that&#039;s not its stated purpose.  The authoring guide is a separate document, of which I am the editor, and is being written in a much more reader friendly fashion.</description> <content:encoded><![CDATA[<p>Just to be clear, that document is only an editor’s draft and it has only been put forth as a proposal.  It’s not yet on the recommendation track, and it’s not yet clear if it ever will be.  It’s also questionable whether it can actually be consisdered “a web authors guide to HTML”, because that’s not its stated purpose.  The authoring guide is a separate document, of which I am the editor, and is being written in a much more reader friendly fashion.</p> ]]></content:encoded> </item> </channel> </rss>
<!-- This site's performance optimized by W3 Total Cache. Dramatically improve the speed and reliability of your blog!

Learn more about our WordPress Plugins: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using disk (user agent is rejected)
Database Caching 4/15 queries in 0.030 seconds using memcached

Served from: webdirections.org @ 2010-03-12 12:20:21 -->