W3C home > Mailing lists > Public > www-style@w3.org > July 2006

Re: [[css3-layout]] Dependencies and normative

From: Karl Dubost <karl@w3.org>
Date: Mon, 24 Jul 2006 10:01:49 +0900
Message-Id: <ED24B8D0-DEFE-45E0-BB08-87DD594CC2C8@w3.org>
Cc: www-style@w3.org
To: Bert Bos <bert@w3.org>


Le 22 juil. 06 à 08:42, Bert Bos a écrit :
>> 	"This CSS3 module depends on the following other CSS3 modules:""
>>
>> to add "normatively".
>
> "Depends on" already implies "normatively," in my mind, but I have no
> objection to add the word.

Then something is strange. The title is

"1. Dependencies on other modules"
and two sections
	- depends on
	- non-normative references
	
But I'm ready to remove my comment if you think it's too much.

>> Also, it might be informative to link to a document showing all
>> dependencies, a graph, drawing. for CSS 3 Framework.
>
> Yes, that would indeed be useful, but I think two things keep us from
> creating it:
>
> 1) We could generate such a graph automatically, but the result would
> probably not be very useful, because the quality of the input varies
> so much: some drafts are quite stable, others have not been reviewed
> yet at all. The reliability of the graph would equal that of the least
> reliable of its inputs.

I have the feeling is then even more important to do it. Because as  
you said it, the quality of the input is different depending on the  
specifications.
Maybe the graph should include
	- the name of the spec
	- the date
	- the status

> 2) A hand-made graph can indicate the reliability of its parts, but
> keeping the graph up to date means work, and we already have a
> shortage of time and people, so I'm afraid it won't happen any time
> soon.

hmm
    - RDF graph?
    - outline (in xhtml or xml) converted automatically?

The group is already doing it for itself to know how everything fits  
together?
http://www.w3.org/TR/qaframe-spec/#ref-define-practice


> We have the same problem with our catalogue of properties. We would
> like to have a complete catalogue of all properties, standard and
> proposed, including those of XSL and SVG. We make such a catalogue
> every once in a while, but it gets out of date so quickly, that it is
> not worth publishing (indeed harmful), until we can guarantee its
> maintenance.

There are many contenders of microformats in your CSS group. They  
usually say that it's easy to author and manage to extract metadata  
in a non hidden way. If a kind of microformats is made for the W3C  
communities to markup features, elements, and or attributes of a  
language, I think it will benefit many people. We could even add it  
to Manual of Style of Susan Lesch.

   W3C Manual of Style
   Help for Editors and Authors of W3C Technical Reports
   http://www.w3.org/2001/06/manual/

Best

-- 
Karl Dubost - http://www.w3.org/People/karl/
W3C Conformance Manager, QA Activity Lead
   QA Weblog - http://www.w3.org/QA/
      *** Be Strict To Be Cool ***
Received on Monday, 24 July 2006 01:02:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:46 GMT