- From: <bugzilla@jessica.w3.org>
- Date: Thu, 20 Sep 2012 18:54:48 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18938
Travis Leithead [MSFT] <travil@microsoft.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |Ms2ger@gmail.com,
| |travil@microsoft.com
--- Comment #2 from Travis Leithead [MSFT] <travil@microsoft.com> 2012-09-20 18:54:47 UTC ---
Yes, this topic needs to be addressed. Adding ms2ger to the discussion as well.
Ms2ger has indicated that working on the WebApps' published version of DOM
Parsing and Serialization is not in his/her interest. I assume then that Ms2ger
will continue to refine and improve the spec over at
http://html5.org/specs/dom-parsing.html.
I don't believe it's in any implementor's best interest to have two divergent
specs. Therefore my goal is to keep the two specs as similar as possible in
relation to features and algorithms. Microsoft is committed to seeing
specifications advanced to Recommendations at the W3C, and hence my involvement
in the WebApps's copy.
I don't know if true convergence is possible (at least at the source level--as
these specs have different license descriptions, templates, process models,
etc.) but I'm committed to keeping this document up-to-date with any updates
that Ms2ger makes to the html5.org document.
If there's a way to resolve the current situation such that DOM Parsing and
Serialization can continue in the W3C, and with Ms2ger at the helm--then I'm
all for that (I have no particular ego investment with this spec--I'm just
trying to deliver a W3C specification the best way I know how). If there's
alternative ideas, then let's discuss them.
--
Configure bugmail: https://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, 20 September 2012 18:54:50 UTC