[wbs] response to 'TR Design Survey'

The following answers have been successfully submitted to 'TR Design Survey'
(public) for Nick Doty.

> 
> ---------------------------------
> Group
> ----
> 
> On behalf of which W3C Working Group are you answering this survey?
> 
> 
> 
 
Tracking Protection Working Group

> 
> 
> ---------------------------------
> Sample(s)
> ----
> Paste in URLs to a representative sample (1-3 links) of your specs. If
> styling differs substantially between /TR and your editor's drafts,
> please link to both versions. 
> 
> 
 
http://www.w3.org/TR/tracking-dnt/
http://www.w3.org/2011/tracking-protection/drafts/tracking-compliance.html

> 
> 
> ---------------------------------
> Specification Processor(s)
> ----
> What spec pre-processor(s) does your WG use?
> 
> 
 
ReSpec

> 
> 
> ---------------------------------
> Group style sheet(s)
> ----
> Paste in URLs to any WG-specific style sheets you use.
> 
> 
 
We don't currently use WG-specific stylesheets.

> 
> 
> ---------------------------------
> Like
> ----
> What do you like about your current styles?
> 
> 
 
* clean display consistent with other specifications
* clear boxes for different class names/categories: issues, notes, examples

> 
> 
> ---------------------------------
> Dislike
> ----
> What do you dislike about your current styles?
> 
> 
 
* a lot of boilerplate and space at the top before the contents of the
document that readers need to see
* (previously) hard to help casual readers skip over different sections
(like options, non-normative text, issue boxes, etc.)

> 
> 
> ---------------------------------
> Complex style
> ----
> Paste in URLs to any parts of your spec that are stylistically complex or
> tricky, and we should therefore be careful not to screw up.
> 
> 
 


> 
> 
> ---------------------------------
> Table style
> ----
> The new styles will include rules for rendering data tables. These will
> be opt-in by class name, and rely heavily on good markup (use of THEAD,
> TBODY, COLGROUP, scope attributes, etc.). See Simple Example, Less Simple
> Example, and Extra-Complex Example. Paste in URLs to a sampling of any
> data tables you are using so that we can try to accommodate those in the
> styling, if practical. 
> 
> 
 
We make sparse use of tables regarding "qualifiers" to indicate certain
permitted uses of data. These tables are quite simple:
http://www.w3.org/2011/tracking-protection/drafts/tracking-compliance.html#qualifiers

> 
> 
> ---------------------------------
> CSS WG Style
> ----
> The CSSWG has made a number of minor improvements to the existing spec
> styles, which we might just adopt wholesale. Please comment on what you
> like/dislike about these styles, as demonstrated in the CSS3 Text
> specification.
> 
> 
 
It seems like there's a lot of vertical white space, especially at the top.
Being able to quickly read the content of a document is important.

> 
> 
> ---------------------------------
> Anything else?
> ----
> 
>     Is there anything else we should consider?
> 
> 
> 
 
We had previously deployed CSS and JavaScript in order to collapse/hide
non-normative sections and issue blocks so that casual readers could more
easily see just normative sections. That code was not maintained and is no
longer necessary, but that kind of functionality (different views for
different users, with the ability to drill down) may be useful in a variety
of contexts.

> 
> These answers were last modified on 10 August 2015 at 22:50:00 U.T.C.
> by Nick Doty
> 
Answers to this questionnaire can be set and changed at
https://www.w3.org/2002/09/wbs/1/tr-design-survey-2015/ until 2015-09-01.

 Regards,

 The Automatic WBS Mailer

Received on Monday, 10 August 2015 22:51:04 UTC