W3C home > Mailing lists > Public > public-html@w3.org > July 2007

Re: care with empty/template wiki topics [was: some thoughts on ...]

From: Dan Connolly <connolly@w3.org>
Date: Thu, 05 Jul 2007 12:00:52 -0500
To: Laura Carlson <laura.lee.carlson@gmail.com>
Cc: "public-html@w3.org WG" <public-html@w3.org>
Message-Id: <1183654852.7058.555.camel@pav>

On Thu, 2007-07-05 at 11:38 -0500, Laura Carlson wrote:
> On 7/5/07, Dan Connolly <connolly@w3.org> wrote:
> > On Sun, 2007-07-01 at 11:55 -0500, Laura Carlson wrote:
> > > On 6/29/07, Dan Connolly <connolly@w3.org> wrote:
> > > > First, a "No, disagree" response says
> > > >
> > > >> "Rationale based on design principles, for each and every
> > > >> dropped/added/changed element and attribute should be supplied."
> > > >
> > > > Well, perhaps it should. By all means, please do provide it.
> > >
> > > Okay, I've started justification pages* for them in the wiki and added
> > > links for them to the issues page [1]. The framework is now there.
> > > [1] http://esw.w3.org/topic/HTML
> >
> > Thanks for following up, but let's not make empty/template pages.
> > Would you please delete the ones with nothing novel in them?
> > I'll try to help.
> 
> Isn't this framework a useful start for us to begin to justify the
> differences between HTML 4 and HTML 5?

Not obviously. It took me quite a while to find any novel
information among the blank/template pages...
http://esw.w3.org/topic/HTML/AddedAttributePing

It seems likely that one justification will
apply to multiple attributes/elements; organizing the justification
as design principles and requirements (and perhaps use cases)
makes more sense to me at this point. I don't like to invest much
in templates/frameworks until *after* it is shown to work well
several examples.

I find the examples in ProposedDesignPrinciples such this
one pretty appealing:
"Don't Reinvent The Wheel
...
Example: contenteditable= was already used and implemented by user
agents. No need to invent a new feature."
 -- http://esw.w3.org/topic/HTML/ProposedDesignPrinciples

An index into the design principles/requirements by attribute/element
is perhaps worthwhile.

I'm open to various organizational structures at this point. But
let's not make empty template pages. They just clutter things up.

-- 
Dan Connolly, W3C http://www.w3.org/People/Connolly/
Received on Thursday, 5 July 2007 17:01:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:02 GMT