W3C home > Mailing lists > Public > spec-prod@w3.org > October to December 2015

RE: Proposed Final Design for W3C Technical Reports style in 2016

From: Steve Glaser <sglaser@nvidia.com>
Date: Thu, 5 Nov 2015 18:27:33 +0000
To: Bert Bos <bert@w3.org>, "chairs@w3.org" <chairs@w3.org>, "spec-prod@w3.org Prod" <spec-prod@w3.org>
CC: "w3c-ac-forum@w3.org" <w3c-ac-forum@w3.org>
Message-ID: <9cd43233492846b1a0a5ef2670c3bfb6@HQMAIL103.nvidia.com>
One related example is to adjust cross references the style within a document based on media. Potential flavors are:

1.       Use the Section/Table/Figure/Equation number as the link "(See Table x-y)"

2.       Use the header name or caption as the link "(See Foo Feature)"

3.       Use both "(See Table x-y: Foo Feature)"



Another issue is external reference style.

1.       Use "[XXX99]" that points to the references section.

2.       Include the reference inline "[...bibliography stuff...]"

3.       Use "[XXX99]", and add a hover over with the full bibliography details.



Yet another issue is footnote style.

1.       Superscript number as a reference to a footnote page.

2.       Footnote inline in a different font style to distinguish it.

3.       Superscript number as a reference to a footnote page adding a hover over containing the footnote text.

4.       Click box to show/hide the footnote contents inline



One common feature of these cases is that the generation tools have all the information. If they "automatically" produced everything in the output html, we could define CSS conventions to identify the pieces and permit hiding what was not relevant for the context (and add the ":" for the both case).



The key item here would be to define CSS conventions for this up front so that the various generation tools can do the right thing.



Steveg





> -----Original Message-----

> From: Bert Bos [mailto:bert@w3.org]

> Sent: Thursday, November 05, 2015 6:56 AM

> To: chairs@w3.org; spec-prod@w3.org Prod

> Cc: w3c-ac-forum@w3.org

> Subject: Re: Proposed Final Design for W3C Technical Reports style in 2016

>

> * PGP Signed by an unknown key

>

> These comments are very good, but to me they also show that we should not

> try to hard-code the (G)UI in the document, because as many people will hate it

> as like it.

>

> I think the task of the authors, and of W3C as the publisher, is to make sure the

> documents are rich and consistent enough that all the different ways of

> navigating and interacting are possible. As long as we get the contents and

> some basic typography right, the reader can choose for himself which UA he

> wants to use and how he wants to configure it.

>

> That, after all, is the great thing about HTML: authors can concentrate on the

> contents without having to worry about the look and feel, and readers can

> consume that content with a device and software of their choosing.

>

>

>

> Bert

> --

>   Bert Bos                                ( W 3 C ) http://www.w3.org/

>   http://www.w3.org/people/bos                               W3C/ERCIM

>   bert@w3.org<mailto:bert@w3.org>                             2004 Rt des Lucioles / BP 93

>   +33 (0)4 92 38 76 92            06902 Sophia Antipolis Cedex, France

>

> * Unknown Key

> * 0x184B5BA4

-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information.  Any unauthorized review, use, disclosure or distribution
is prohibited.  If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------
Received on Thursday, 5 November 2015 18:28:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:55:21 UTC