Return-Path: X-Original-To: apmail-incubator-callback-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-callback-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 04F1ADFAE for ; Fri, 19 Oct 2012 21:25:35 +0000 (UTC) Received: (qmail 39883 invoked by uid 500); 19 Oct 2012 21:25:34 -0000 Delivered-To: apmail-incubator-callback-dev-archive@incubator.apache.org Received: (qmail 39848 invoked by uid 500); 19 Oct 2012 21:25:34 -0000 Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: callback-dev@incubator.apache.org Delivered-To: mailing list callback-dev@incubator.apache.org Received: (qmail 39838 invoked by uid 99); 19 Oct 2012 21:25:34 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Oct 2012 21:25:34 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of brian.leroux@gmail.com designates 209.85.215.175 as permitted sender) Received: from [209.85.215.175] (HELO mail-ea0-f175.google.com) (209.85.215.175) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Oct 2012 21:25:28 +0000 Received: by mail-ea0-f175.google.com with SMTP id c1so277739eaa.6 for ; Fri, 19 Oct 2012 14:25:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=pE71QiP7zyUJZFZNU1O6VL3AfY8Jmxn3PmTOOEqwums=; b=yy72xaU/peA9q4C+LscJjUYKjnDqvkYakdtWD0v2bEZ6nB0gSlDHCtWPiyyJri0tHG zKDo8XjRrYvSrnHQ/ZjSjf1Xwzd4vtLNY721NNrmRy2qt1wrNEzzsjOx0S9RxYvMPSSL y6X8022hXjaDnn38KcJwGshAAop+0ou5JSCiwGaYy+gAnUxJVnwMEe7SaWdsoKEoj1JP acVPhKTM69USyVSdpyVQ9Xi7924BjE9BroBTmDGQXcJfrk+UgZB9rhgSLucB/x911kby i4KZQoVzWi8Jnt6ppa9mIz74Gx4rcs8UR3wagqYNqU/76L507BBfD2z183hLik7b9X/L rvqw== MIME-Version: 1.0 Received: by 10.14.172.195 with SMTP id t43mr3693284eel.17.1350681908280; Fri, 19 Oct 2012 14:25:08 -0700 (PDT) Sender: brian.leroux@gmail.com Received: by 10.14.177.198 with HTTP; Fri, 19 Oct 2012 14:25:08 -0700 (PDT) Date: Fri, 19 Oct 2012 14:25:08 -0700 X-Google-Sender-Auth: qSiJARDx2ySlpjKcJnq6LVy8gUs Message-ID: Subject: capabilities api From: Brian LeRoux To: callback-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Community member Ian has noticed our lack of a capabilities api, and ignoring the snipe at our foresight, I do agree its a missing piece in the web platform. [1] There is some prior art. - Media queries have a couple of interesting APIs (matchMedia [2], window.devicePixelRatio, and potentially a future navigator.supportsCSS). - Flash has a comprehensive capabilities API. [3] - The W3C has a somewhat unwieldy take on this issue. [4] It should be noted that a new working group at the w3c called sysapps will be addressing this. - Tizen has a System Info API (which I'd link to but cannot). Does anyone have any thoughts on how we should structure / develop out the ability for our users to query the device capbilities? [1] https://twitter.com/iandevlin/status/259309546969903104 [2] https://developer.mozilla.org/en-US/docs/DOM/window.matchMedia [3] http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/system/Capabilities.html [4] http://www.w3.org/TR/2007/WD-CCPP-struct-vocab2-20070430/