Questions on the Origin of BLOCKQUOTE

View: New views
4 Messages — Rating Filter:   Alert me  

Questions on the Origin of BLOCKQUOTE

by Sean B. Palmer :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Dan,

I'm investigating why BLOCKQUOTE was introduced to HTML. The two
earliest mentions of the element occur in a message and a document by
you:

(1)

“I'm trying to keep up with all sorts of HTML ideas.  Some things can be
added to html.dtd without significant changes to W3 code (like adding a
BLOCKQUOTE tag for a new paragraph style). But for things that will
require changes to the architecture, I'm developing a separate DTD from
the descriptive html.dtd.”

http://lists.w3.org/Archives/Public/www-talk/1992NovDec/0159
Re: The spec evolves...
Dan Connolly (connolly@...)
Fri, 04 Dec 92 18:07:49 CST

(2)

<!ENTITY % bodyelement
         "P | A | %heading |
         %list | DL | HEADERS | ADDRESS | PRE | BLOCKQUOTE
        | %literal">

http://suika.fam.cx/gate/cvs/*checkout*/test/html.dtd?rev=1.3
Document Type Definition for the HyperText Markup Language
as used by the World Wide Web application (HTML DTD).
$Id: html.dtd,v 1.3 1993/01/07 00:38:36 connolly Exp $

Revision 1.2 of html.dtd dates to 1.2 1992/12/03, the day before the
message just quoted at (1), where it seems that you were trying to
keep up with suggestions for changes to HTML, and that BLOCKQUOTE was
one of those suggestions. On 7th January 1993, you checked in the new
html.dtd with BLOCKQUOTE included (2).

Neither of these mentions, however, reveal who suggested BLOCKQUOTE
and why. Was there any discussion surrounding its inclusion? What did
TimBL and others think of it? And how fast was W3 code updated? Why
was BLOCKQUOTE included whereas, perhaps, other suggestions fell by
the wayside?

What I'm trying to understand is how BLOCKQUOTE came to be included,
partially in order to better understand why and how it should be used
now. For example, one could easily have eschewed BLOCKQUOTE in favour
of usual typographical conventions:

<p>“First quoted paragraph.</p>
<p>“Second quoted paragraph.”</p>

An argument against this now is that BLOCKQUOTE gives you independence
of styling. Independence of styling was, however, not an option in
late 1992 when CSS was yet to be invented. Indeed, there are even
potential signs that BLOCKQUOTE did not win favour with users very
early on. In May 1993, Dave Raggett was asking whether people were
actually using the element:

“I am drafting an extended verion of the HTML standard and would
like to know if anyone is using the <BLOCKQUOTE> element for quoted
paragraphs. This element has a name greater than 8 characters
which could cause problems with some SGML parsers.”

http://1997.webhistory.org/www.lists/www-talk.1993q2/0269.html

He suggested renaming it to QUOTE, and after apparently receiving no
reply on www-talk he actually called it BQ in HTML 3:

http://www.w3.org/MarkUp/html3/blockquotes.html

But then in HTML 3.2 it was back to BLOCKQUOTE, perhaps because by
this point there was an established user base and the SGML 8 character
problem had either been fixed, a workaround found, or was deemed
irrelevent:

http://www.w3.org/TR/REC-html32#bq

My suspicion is that BLOCKQUOTE follows the pattern of other early
elements, which try to introduce some level of independence from
style, giving a few suggestions as to how user agents may render it,
whilst still trying to provide a kind of reasonably well understood
meaning. Consider, for example, what HTML 2 says about BLOCKQUOTE:

“A typical rendering might be a slight extra left and right indent,
and/or italic font. The BLOCKQUOTE typically provides space above and
below the quote.

“Single-font rendition may reflect the quotation style of Internet
mail by putting a vertical line of graphic characters, such as the
greater than symbol (>), in the left margin.”

http://www.w3.org/MarkUp/html-spec/html-spec_5.html#SEC5.5.4

Indentation was perhaps not available using any other element, but <I>
and <EM> were added to html.dtd v.1.2 along with BLOCKQUOTE, so those
at least could have been used instead for one of the suggested
renderings. The meaning of the element and the diversity of possible
stylings seems quite likely to have been important at that stage.

This original prominent approach to element design seems to have
fallen by the wayside due to consensus of styling amongst user agents
narrowing the diversity with which an element is styled. So with
BLOCKQUOTE, it came to be associated in authors' minds with
indentation rather than its meaning as an extended quotation: by HTML
4.01, there is a warning in the specification that people are using it
merely for indentational formatting with non-quotation semantics.

At any rate, much of this research is speculation, filling in the dots
between a few scant references in the record. Even if the dots are
filled in correctly, there may be extra rationale that I've missed. I
was hoping therefore that you might be able to piece together some
more information given your clearly very central involvement in the
subject.

Kindest regards,

--
Sean B. Palmer, http://inamidst.com/sbp/


Re: Questions on the Origin of BLOCKQUOTE

by Alexander Christiaan Jacob :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Sean B. Palmer schreef:
> What I'm trying to understand is how BLOCKQUOTE came to be included,
> partially in order to better understand why and how it should be used
> now.
A blockquote adds semantic value to the document.
> For example, one could easily have eschewed BLOCKQUOTE in favour
> of usual typographical conventions:
>
> <p>“First quoted paragraph.</p>
> <p>“Second quoted paragraph.”</p>
>  
Actually, it is a typographical convention to distinguish a block quote
from the surrounding text by variation in typeface (italic versus roman,
serif versus sans-serif), type size, or by indentation. This is easily
realized with the use of an extra container element.
> An argument against this now is that BLOCKQUOTE gives you independence
> of styling. Independence of styling was, however, not an option in
> late 1992 when CSS was yet to be invented.
But then the default rendering already included special margins (that
you mention later on). This is also a convention in typesetting, and
impossible to pull off without the use of images, tables or css.

Greetings,


ACJ


Re: Questions on the Origin of BLOCKQUOTE

by Sean B. Palmer :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Sat, May 2, 2009 at 5:25 PM, ACJ <ego@...> wrote:

> This is easily realized with the use of an extra container element.

But in 1993, you couldn't choose the style.

What I meant is that there was already a minimal implementation for
quoting blocks of text, and you didn't have to introduce anything into
html.dtd v.1.2 for that.

Of course there are endless typographical abilities that could, and
often were, added to HTML subsequently. That says nothing about which
were most valuable.

You say that BLOCKQUOTE adds semantic value. Well all kinds of things
could add semantic value to HTML: take the things added latter, or
much of the stuff in DOCBOOK and TEI and so forth. That doesn't
explain why BLOCKQUOTE specifically was added, nor why it was added
when it was.

--
Sean B. Palmer, http://inamidst.com/sbp/


Re: Questions on the Origin of BLOCKQUOTE

by David Woolley (E.L) :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Sean B. Palmer wrote:

>
> Indentation was perhaps not available using any other element, but <I>
> and <EM> were added to html.dtd v.1.2 along with BLOCKQUOTE, so those
> at least could have been used instead for one of the suggested
> renderings. The meaning of the element and the diversity of possible
> stylings seems quite likely to have been important at that stage.

I don't believe it was ever the original intent of HTML that it should
dictate a presentation, so BLOCKQUOTE is actually much more consistent
with the HTML philosophy than I or B.  HTML was supposed to be a
universal information language, not a universal page description language.

>
> This original prominent approach to element design seems to have
> fallen by the wayside due to consensus of styling amongst user agents
> narrowing the diversity with which an element is styled. So with

Essentially, the market wanted something for writing advertising copy,
i.e. it was the market for PDF, not for HTML.  As such there was
pressure on browsers to provide consistent rendering, and, in turn, a
tendency to use elements based on their rendering, rather than their
meaning.  CSS is an attempt to free HTML from that misuse by giving
sufficient power to control rendering that you can use HTML that
reflects meaning and still achieve a particular rendering.

> BLOCKQUOTE, it came to be associated in authors' minds with
> indentation rather than its meaning as an extended quotation: by HTML
> 4.01, there is a warning in the specification that people are using it
> merely for indentational formatting with non-quotation semantics.

As I say, that is because commercial authors (and vanity authors) didn't
really buy the HTML philosophy and wanted a page description language.
The world may have been very different if Adobe had provided free basic
authoring tools, and internet capabilities, for PDF, before Mosaic got a
foothold.


--
David Woolley
Emails are not formal business letters, whatever businesses may want.
RFC1855 says there should be an address here, but, in a world of spam,
that is no longer good advice, as archive address hiding may not work.