W3C home > Mailing lists > Public > public-device-apis@w3.org > September 2011

Fwd: Webinos specification publicly available

From: Dominique Hazael-Massieux <dom@w3.org>
Date: Fri, 02 Sep 2011 17:03:47 +0200
To: public-device-apis@w3.org
Message-ID: <1314975834.5921.235.camel@altostratustier>
Resending, since Claes' initial message seems to have been rejected as
"dangerous" by a large number of subscribers MTA (for some reason).


-------- Message transféré --------
De: Nilsson, Claes1 <Claes1.Nilsson@sonyericsson.com>
À: public-device-apis@w3.org <public-device-apis@w3.org>
Sujet: Webinos specification publicly available
Date: Fri, 2 Sep 2011 16:52:04 +0200



The Webinos EU research project has now made specifications publicly


For the DAP WG most relevant is the deliverable of API specifications,


Where possible Webinos just refers to an existing API specification with
first preference W3C. In some cases the existing specification does not
fulfill Webinos requirements so modifications have been specified. For
other requirements completely new API specifications have been
specified. Examples of new APIs are: Service Discover API, Generic
Sensor API, TV Control API, NFC API and Vehicle API.


See list of Webinos API specifications here:


It is Webinos’s intention to contribute Webinos results to
standardization bodies and for DAP this means that relevant API
specifications can be submitted as input proposals to DAP APIs. I have
already sent a mail to this list on the Webinos Service Discovery and
Sensor APIs,
http://lists.w3.org/Archives/Public/public-device-apis/2011Aug/0024.html. For the Service Discovery we will conduct a more careful comparison with Opera’s proposal (http://lists.w3.org/Archives/Public/public-device-apis/2011Jul/0073.html and http://lists.w3.org/Archives/Public/public-device-apis/2011Aug/0018.html) . 


Furthermore, as side note, Google has announced Web Intents:
http://blog.chromium.org/2011/08/connecting-web-apps-with-web-intents.html .. Looking at this it seems as similar to Web Introducer, i.e. it seems aimed at solving the same type of use cases, and seems to be the model currently selected by Google. 


So we need to understand these different models and understand the
similarities and differences. 


Best regards

Received on Friday, 2 September 2011 15:04:02 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:50 UTC