Re: Proposal for developing HTML 5 materials for Web *authors*

I haven't heard anyone say that we don't need materials for HTML5 Web authors.

So instead of just debating the details, how do we get this ball rolling?  What is the process for getting this task force started?

Over in WAI, when we do task forces, we usually work up some type of task force statement that includes things like objectives, communication methods, and participation expectations.  The task force work statement is then approved by the WG.

I'd be happy to help draft something.

- justin


******************
Justin Thorp
US Library of Congress
Web Services - Office of Strategic Initiatives
e - juth@loc.gov
p - 202/707-9541

>>> Karl Dubost <karl@w3.org> 11/21/2007 1:21:14 AM >>>

ACTION-5 Make a proposal on the mailing list for the creation of a  
task force for developer community outreach  [3]

Hi,

During the last F2F at the Technical Plenary in Cambridge, we had a  
lively discussion on [HTML 5 for authors][2] and more precisely the  
lack of materials for people developing and designing Web sites. The  
traditional readers of HTML Specifications were by large the Web  
development community. The [HTML 5 Editor draft][1] has been written  
with the implementers in mind. Then the usual community is at lost  
reading the document.

There is a need for reference materials for helping authors to develop  
and write HTML 5.

HTML 5 author materials can only be a subset of what is defined in  
HTML 5 document. This document will not promote techniques or syntaxes  
which are illegal in HTML 5. Web designers, webmasters, Web  
developers, teachers collectively may decide that a stricter subset of  
HTML 5 is useful in their practices of the Web.

People have during the F2F expressed a will to participate to such  
materials. There is a few possibilities:

* W3C Working Group Note
* Dedicated wiki with pages having some locked sections (peer process  
review) and free editing sections for example, etc.



Some issues arose during the F2F and corridors discussions.

* Shall the syntax style be stricter than the one recommended by HTML  
5 specification.
   example:
   <p class=intro>Readable Markup
   <p class="intro">Readable Markup</p>

* Banning the use of some elements and/or proposing better techniques.
   <font size=+2>

* What about authoring tools and validators?

* How this material will be marketed to the community?

* What to do if people try to enforce them on others?




I put Roger Johansson in Cc: because a few months ago, we started a  
document on what could be an HTML 5 for authors. It was very  
preliminary work and with nothing much into it. We wanted this  
document to be written by the community itself and we define a  
template of things which could fit in such document.

     [NAME] element

     A short description of what is the element and the
     requirements defined in the specification.

     Best Practices
     Think about the best way to use this element, not only for
     its semantics content, but also for the current practical
     benefits, it creates. For example, using the blockquote
     element to create a quote and how to reuse it an engine
     extracting quote from the Web or a personal Web site. If you
     have script share them. When the list of Best Practices is
     too long, please create a separate document with detailed
     explanation. @@contribution license here@@

     Accessibility
     If there are specific requirements or techniques for
     accessibility, share in this section.

     Internationalization
     If there are specific requirements or techniques for
     internationalization, share in this section.

     Examples
     Some practical simple examples that you are using in a
     professional context to illustrate the element





[1]: http://www.w3.org/html/wg/html5/ 
[2]: http://www.w3.org/2007/11/09-html-wg-minutes.html#item02 
[3]: http://www.w3.org/html/wg/tracker/actions/5 

--
Karl Dubost - W3C
http://www.w3.org/QA/ 
Be Strict To Be Cool

Received on Wednesday, 21 November 2007 14:48:18 UTC