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 7035 - clarify what the use case is for first illustration under "3.4 Content models"
Summary: clarify what the use case is for first illustration under "3.4 Content models"
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Depends on:
Reported: 2009-06-19 03:18 UTC by Michael[tm] Smith
Modified: 2010-10-04 14:55 UTC (History)
4 users (show)

See Also:


Description Michael[tm] Smith 2009-06-19 03:18:13 UTC
<MikeSmith> so, about your actual statement in that message, regarding the topic of "content model"
<sayrer> yeah
<MikeSmith> "I can see why this might be tempting to specify for theoretical reasons, but I can't think of a use case."
<sayrer> why does that exist?
<sayrer> that is the first illustration under "3.4 Content models"
Comment 1 Lachlan Hunt 2009-06-25 10:11:00 UTC
The diagram exists to more easily convey the relationship between each of the categories.  So, for example, a reader can see at a glance that all embedded content is also phrasing content, so they know that wherever phrasing content is allowed, embedded content is too.  It's a lot quicker and easier to understand such relationships by glancing at the diagram than having to read all of the descriptions.  It's certainly useful for me.  Before it was in the spec, I had even sketched my own for the same reason.  So I would object to its removal.
Comment 2 Ian 'Hixie' Hickson 2009-06-26 09:18:33 UTC
The diagram exists for the reason Lachlan states; someone indicated that they would like a clearer introduction to the various content models and so I provided this diagram (with the help of a couple of other people).

I'm not sure what this bug is asking for at this point.
Comment 3 Maciej Stachowiak 2010-03-14 14:48:18 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.