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 8368 - Remove the Communication Section 8
Summary: Remove the Communication Section 8
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Macintosh Mac System 9.x
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Keywords: NE
Depends on:
Reported: 2009-11-24 22:02 UTC by Shelley Powers
Modified: 2010-10-04 14:45 UTC (History)
7 users (show)

See Also:


Description Shelley Powers 2009-11-24 22:02:55 UTC
This section is specific to a certain type of user agent, and only within specific conditions. It has absolutely nothing to do with HTML or XHTML, or with the DOM. The focus of the section is communication between applications, and the only connection I can find to HTML, XHTML, and the DOM, is that the applications also render HTML. 

Section 8 includes material that exceeds the bounds for what a reasonable person would assume be covered in a specification devoted to HTML, XHTML, and the DOM. However, the section does include material of interest to a subgroup of HTML UAs, and as such should be preserved in a separate specification.

Since there are dependencies between this section and objects covered in Section 6, a reasonable person could assume a merger between these two sections into a separate specification.
Comment 1 Maciej Stachowiak 2009-11-24 23:10:48 UTC
Cross-document messaging and channel messaging could probably be split into a separate spec and likely would be welcomed by WebApps WG. I don't think any other part of the spec depends on the contents of section 8. Section 8 does depend on Window and on the origin concept, but so does XMLHttpRequest, and that hasn't been a problem.
Comment 2 Ian 'Hixie' Hickson 2010-01-08 09:21:34 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, 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:

Status: Partially Accepted
Change Description: split into its own subspec
Rationale: the section is no more mature than microdata, it is not widely used, and could be reused in other languages.
Comment 3 contributor 2010-01-08 09:22:25 UTC
Checked in as WHATWG revision r4548.
Check-in comment: split out communications section
Comment 4 Shelley Powers 2010-01-09 00:45:34 UTC
(In reply to comment #3)
> Checked in as WHATWG revision r4548.
> Check-in comment: split out communications section

The communication section would be better in the Web apps group. And I believe you need to discuss publishing Communication as a FPWD with the group, first.
Comment 5 Shelley Powers 2010-01-10 21:01:21 UTC
I'm mainly re-opening this bug, until there's a decision made about where the split-out section is going. 
Comment 6 Ian 'Hixie' Hickson 2010-01-11 10:12:29 UTC
That's not how the process works.