- From: Marcos Caceres <w3c@marcosc.com>
- Date: Fri, 11 Nov 2011 17:06:38 +0100
- To: Robin Berjon <robin@berjon.com>
- Cc: Vincent Hardy <vhardy@adobe.com>, "spec-prod@w3.org Prod" <spec-prod@w3.org>, "fantasai.lists@inkedblade.net" <fantasai.lists@inkedblade.net>
On Friday, November 11, 2011 at 2:53 PM, Robin Berjon wrote: > > The action that Vincent and Fantasai got is indeed strictly stylistic. There is a completely separate project to provide rich tools for specifications. That one is up for whoever wants to grab it. I don't think that use cases and requirements are the way to go for this at this stage I don't want to use the "polish a turd" metaphor, but I think I just did :) Without stylistic design goals, making things pretty won't get us nowhere. Each stylistic change should be motivated by a design goal that meets some requirement (otherwise, it's not "design", it's just mindless styling). I know Fantasai and Vincent have specification experience and know all this already, so of course they won't do that (i.e., they will work with some requirements and goals in mind). I just want to make sure we know what they are, so we can make sure as many of the requirements as possible are covered. > — I think the scratch the itch methodology would work much better :) True. But I wanna know what's itching', why, and how it's going to be scratched… and evidence that the itching has been reduced to a tolerable level (or gone all together). So, we know that the largest weeping sore in a spec is the SoTD: looking forward to seeing some ointment being applied to it. I think the current "BIG FAT RED BOX - THIS IS CHANGING!!!!" used by HTML5 is a good start to healing that: http://www.w3.org/TR/html5/ -- Marcos Caceres
Received on Friday, 11 November 2011 16:07:20 UTC