- From: Ian Hickson <ian@hixie.ch>
- Date: Wed, 28 Jan 2009 02:25:02 +0000 (UTC)
- To: HTML WG <public-html@w3.org>
- Message-ID: <Pine.LNX.4.62.0901280218350.952@hixie.dreamhostps.com>
On Wed, 28 Jan 2009, Lachlan Hunt wrote: > Karl Dubost wrote: > > Le 27 janv. 2009 à 19:40, Jonas Sicking a écrit : > > > That is one question. Another question would be if it's useful and > > > practical to do so. > > > > From discussions in different *web designers* and *webmasters* fora > > and venues, yes very useful to only have the markup language. > > Given the fact that there are now 2 drafts being worked on specifically > for authors by myself and DanC, what benefit is Mike's draft, especially > since it's content is clearly not optimised for such an audience? Not optimised nor indeed _intended_ for such an audience. The draft is clear that it is intended to be a "tutorial" or "how to" authoring guide. Web designers and Webmasters aren't asking for a normative specification with lines like: aria-dropeffect = "none" | list{ "copy", "move"?, "reference"? } | list{ "copy", "reference"?, "move"? } | list{ "move", "copy"?, "reference"? } | list{ "move", "reference"?, "copy"? } | list{ "reference", "copy"?, "move"? } | list{ "reference", "move"?, "copy"? } ...or: date = A valid full-date, as defined in RFC 3339 [RFC3339], with the additional qualification that the year component is a nonzero-date-fullyear. ...both of which are from Mike's draft. My experience discussing this with such authors is that by and large they are looking for approachable texts in the form of an easy-to-read reference guide (a list of all elements and APIs, with clear explanations of how to use them, with examples) and selections of topical tutorials ("How to write a comment form", "How to mark up a blog", "How to embed video", etc). -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 28 January 2009 02:25:38 UTC