- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Thu, 15 Apr 2010 18:19:35 +0200
- To: Sam Ruby <rubys@intertwingly.net>
- CC: "public-html@w3.org" <public-html@w3.org>
On 15.04.2010 18:01, Sam Ruby wrote:
> ...
> If you like, submit multiple proposals, each of which specifies a
> consistent set of change controllers (W3C, WHATWG, OASIS, Julian
> Rescke's cat, should you happen to have one), but yes, any one given
> change proposal needs to be specific and justify why that specific
> choice was made.
> ...
I don't have a cat, but maybe I should. In the meantime I'll consider
nominating one of Ian's cat in a separate Change Proposal.
>> Also, I'm not clear what additional rational is needed. I explained why
>> I think they should be consistent. I think the question what the change
>> controller for text/html should be was already discussed and resolved.
>
> Citing that discussion could support the choice that you make.
> ...
That actually *is* in the change proposal.
Anyway, here's a new revision:
SUMMARY
In the IANA registration templates, the specified change controllers for
text/html and text/html-sandboxed differ.
RATIONALE
text/html-sandboxed is defined as a subset/profile of text/html, so it's
definition de facto is controlled by the change controller of text/html
anyway.
DETAILS
Make the specified change controllers consistent by changing the Change
Controller field in Section 12.2 ("text/html-sandboxed") to "W3C".
IMPACT
1. Positive Effects
It becomes clear that changes to most aspects of the text/html-sandboxed
media type are controlled by the change controller of text/html.
2. Negative Effects
None.
3. Conformance Classes Changes
None.
4. Risks
None.
REFERENCES
None.
Received on Thursday, 15 April 2010 16:20:14 UTC