This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 6770 - Term emphasis inconsistencies in Terminology section
Summary: Term emphasis inconsistencies in Terminology section
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Depends on:
Reported: 2009-04-03 15:46 UTC by Matt Schmidt
Modified: 2010-10-04 13:59 UTC (History)
3 users (show)

See Also:


Description Matt Schmidt 2009-04-03 15:46:08 UTC
A term is defined in nearly every paragraph in the Terminology section. Terms are formatted differently from the general text, but this format varies from paragraph-to-paragraph and, in some cases, from sentence-to-sentence.


  Sentence 2: content attributes, DOM Attributes -- bold
  Sentence 3: properties -- quoted

  Sentence 1: All terms are links with no additional format

  Sentence 1: document -- italicized

  Sentence 2: Terms are quoted and bold

I'm not sure if there is a standard for how emphasis should be placed when defining terms. IIRC from my school days, textbooks would typically have terms in bold text.
Comment 1 Ian 'Hixie' Hickson 2009-06-01 20:09:36 UTC
I've tried to make this mildly more consistent, but most of the differences have somewhat good reasons for being there. The things that are links are links to the "real" definitions elsewhere. The terms that are not quoted are being used in context, so it would be inappropriate to quote them.

If there are specific cases you think are especially egregious, please let me know.
Comment 2 Maciej Stachowiak 2010-03-14 13:18:37 UTC
This bug predates the HTML Working Group Decision Policy.

If you are satisfied with the resolution of this bug, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:

This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.