[Bug 13423] Remove the Editing APIs section. It's extremely incomplete and contradicts my editing spec on a lot of points, so it will confuse implementers.

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13423

--- Comment #31 from Sam Ruby <rubys@intertwingly.net> 2011-08-18 13:47:09 UTC ---
(In reply to comment #29)
> I'm happy to leave these
> sections in the W3C side (unmaintained, of course) if the working group would
> like

I disagree that any text that remains would be unmaintained. Any content that
remains in the W3C document is a valid subject of bug reports; and any such bug
reports are expected to be RESOLVED by the editor, such resolutions can be
escalated, and we will expect any decisions (amicable or otherwise) that result
from any such escalations that may occur to be applied.

> Your advice on the
> matter is welcome.

Since this is a charter issue, this will ultimately need to be decided by W3C
staff, though the co-chairs will work to ensure that the WG has ample
opportunity to provide input on the matter.

Not specific to this matter, I expect that as we move to CR we will find other
features that aren't ready to standardize just yet, and such will need to be
deferred to HTML.next.  Normally, I would expect to find that through formal
testing and an inability to demonstrate the existence of multiple
inter-operable implementations.  This particular case seems to simply have been
found earlier and through inspection and ad hoc testing, but that's certainly
OK too.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Thursday, 18 August 2011 13:47:16 UTC