Re: AW: Topics for W3C workshop?

Overall I concur with Robert
I saw an interesting demo at mwc for alljoyn
Much of what we speak of already exists in some shape or form.
Many platforms like alljoyn are in open source domain also ie not
propriotery

So the value add could be in terms of a unifying technology and in
connecting web technology to deeper layers of the stack ex webinos micropzp
node.js etc
Rgds
Aj
 On 24 Feb 2014 22:45, "Kleinfeld, Robert" <
robert.kleinfeld@fokus.fraunhofer.de> wrote:

> Dear all,
>
> some thoughts from us. Currently we have various IoT platforms such as
> Xively, The Thing System, Carriots, Temboo etc. There is a lack of
> connecting all these platforms and their related services and applications.
> I feel that there is a need to define unified APIs and protocols on top of
> current standards. With the challenge to motivate a hub of IoT platforms
> and not building the next new IoT platform. We need overall approaches to
> connect all these platforms. If you are looking at http://iotlist.co/ you
> will find an enormous number new devices and applications for the smart
> home and connected home domain. These implies standards for service
> discovery, pairing and session mobility across all these devices.
> Furthermore, we have an Internet of applications in mainstream
> marketplaces. Why not thinking about an Internet of services for smart home
> and connected home.
>
> Currently you will find lightweight node.js applications which are running
> on servers, microcontrollers and single-board computers. This includes
> various prototype applications with proprietary implementations for
> exposing these hardware components to the web. So we need standardized APIs
> for enabling these kind of node.js applications and hardware. Additionally
> we find a moving trend in the SmartTV domain to Web technologies. This
> grounding should be used to enable Web technologies for smart home,
> connected home and wearable device.
>
>
> Best regards / Mit Besten Grüßen
> Robert Kleinfeld
>
>
> -------------------
> Robert Kleinfeld, M.Sc.
> Senior Project Manager R&D
> Future Applications and Media
>
> Fraunhofer Gesellschaft
> FOKUS - Research Institute for
> Open Communication Systems
>
> Kaiserin-Augusta-Alle 31
> D-10589 Berlin
> -------------------
> Phone +49 (0)30 / 34 63 - 71 08
> Mobile +49 (0)163 / 3 34 78 66
> Skype robertkleinfeld
> robert.kleinfeld@fokus.fraunhofer.de
> www.fokus.fraunhofer.de
> -------------------
>
> Save the date: 4th FOKUS Media Web Symposium, May 8-9, 2014
> Be part of it: www.fokus.fraunhofer.de/go/mws
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Dave Raggett [mailto:dsr@w3.org]
> Gesendet: Dienstag, 18. Februar 2014 15:15
> An: public-web-of-things@w3.org
> Betreff: Topics for W3C workshop?
>
> I would like to encourage some brainstorming about potential areas for W3C
> to standardize and how we could explore these in the workshop we're
> planning for June.
>
> Protocols and APIs:
>
> There are many communication technologies for the IoT and this reflects
> the varying requirements. For W3C HTTP and Web Sockets are core protocols,
> but we are also working on NFC, Bluetooth, network service discovery and
> access to raw IP sockets. Should W3C consider work on script APIs for other
> protocols?  What kinds of coordination are needed across standardization
> bodies?
>
> Apps and Services:
>
> W3C has so far concentrated on standards for HTML and related formats,
> e.g. for style sheets, scripts and style sheets.  There is an increasing
> interest in the use of JavaScript for implementing services, e.g. with
> node.js on home gateways, and even subsets of JavaScripts for use on
> microcontrollers.. Is it time for W3C to coordinate standards for APIs for
> use by scripts running on servers?
>
> For a market of value added services, there will be a need for a means to
> declare what the service exposes, and what it depends upon.  Is there a
> need for work on interface definition languages for this?  Some
> requirements include the need for shared semantics (e.g. for physical
> units),  and integrity constraints that the platform can enforce for
> increased robustness. What additional requirements are there for markets of
> services, e.g. scalability, real-time services, payments, compositions of
> services, APIs for authoring tools, etc.
>
> Security, trust and privacy:
>
> What are the issues and associated requirements?  This includes: mutual
> authentication, provenance, access control and privacy policies.  What do
> we need to do to support retroactive security, e.g. support for monitoring
> and recovering from problems?
>
> The role of semantics:
>
> Shared semantics is key enabling an open market of services. The Web of
> Things can be positioned as the combination of tags, sensors and actuators
> with rich descriptions, e.g. of people, devices, places, and events to
> enable open markets of value added services, in other words, the merger of
> the Internet of things and the Web of data to create a Web of services.
> Open questions include who describes what and when, along with how to
> combine linked data and services
>
> Please contribute your ideas to this discussion.
>
> --
> Dave Raggett <dsr@w3.org> http://www.w3.org/People/Raggett
>
>
>
>
>