- From: <bugzilla@jessica.w3.org>
- Date: Thu, 06 Oct 2011 05:30:40 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14394
Henri Sivonen <hsivonen@iki.fi> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |hsivonen@iki.fi
Resolution| |WONTFIX
--- Comment #1 from Henri Sivonen <hsivonen@iki.fi> 2011-10-06 05:30:39 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:
http://dev.w3.org/html5/decision-policy/decision-policy.html
Status: Rejected
Change Description: no spec change
Rationale: If you have a private (non-browser) system that ingests HTML5 or
XHTML5, you are welcome to apply a schema language or data binding mechanism of
your choice to the output of the parser. In that sense, this is WORKSFORME.
If you meant adding XSD 1.1 data binding mechanisms to browsers, that's
WONTFIX. Browsers do not already contain XSD capabilities and XSD is rather far
off from the kind of features that browsers do provide and that are in popular
demand for browsers to provide. For this reason, it doesn't make sense for
HTML5 to attempt to add dependencies on XSD.
--
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, 6 October 2011 05:30:42 UTC