- From: <bugzilla@jessica.w3.org>
- Date: Thu, 06 Sep 2012 16:22:52 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15592
Robin Berjon <robin@w3.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |robin@w3.org
Resolution| |WONTFIX
AssignedTo|dave.null@w3.org |robin@w3.org
--- Comment #9 from Robin Berjon <robin@w3.org> 2012-09-06 16:22:46 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
Rationale:
Hi Dieter,
the features you describe do indeed have some value, but they are not being
defined as part of the HTML spec. As you note, some APIs are birthed in other
places.
In this case, the W3C is currently in the process of chartering two groups that
are related to what you describe:
NFC WG
http://www.w3.org/2012/05/nfc-wg-charter.html
SysApps WG (notably: Secure Elements API)
http://www.w3.org/2012/05/sysapps-wg-charter.html
In both cases, while those groups do not formally exist yet the mailing lists
that are listed in those draft charters are already up and running, and open to
the public to join. I encourage you to!
--
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, 6 September 2012 16:22:53 UTC