W3C and Ambient Computing

1/13/2014

W3C and Ambient Computing

Most of the text and the pictures in this document are extracted from the public pages of the W3C web sites.

Pierre Maret January 2013

Agenda • W3C mission and organization • W3C standards classification • Situating Ambient computing in the W3C areas – – – – – –

Web of Devices Web of Design and applications Web Architecture XML technologies Web of Data Web of Services

Processes of the W3C Stakeholders

W3C • Mission – Ensure the long-term growth of the Web (“Lead the Web to its Full Potential”) – Through developing and standardizing technologies, protocols and guidelines – Make the Web work for everyone, everywhere on every device – Royalty-Free Technologies (open standards)

Stakeholder and W3C processes

• W3C team. Organizes activities • Member Organizations & their Representatives. Participate in – Working Groups (and Interest Groups, Coordination Groups, Business Groups, Community groups) – Workshops (and Symposia) – They can initiate a Member Submission Process

• Public and external Experts. Participate in – Community Groups Initiation and Participation – Experts can be invited Reference document: http://www.w3.org/2005/10/Process-20051014/

1

1/13/2014

Recommendation track From a Working Group to a W3C recommendation 1. 2. 3. 4.

5. 6.

“Editors drafts” : current view of the editors of the specification (no standing in terms of standardization). “Working Drafts” (WD): early milestones of the Working Group (WG) progress. “Last Call Working Drafts”: the specification fulfills the WG requirements. They requests feedback from the larger community. “Candidate Recommendations” (CR): implementers are invited to implement the specification and send feedback; WG is expected to show the specification gets implemented by running test suites they have developed. “Proposed Recommendations” (PR): Once the WG has gathered sufficient implementation experience; triggers the final review by W3C Members. “W3C Recommendations” (Rec): stable and completed Web standards; updated through the “Edited Recommendation” process (minor revisions).

Current strategy of the W3C in 2013

W3C method and outputs • Method – Buttom-up – Implementation (widely deployable and interoperable) – Maximize consensus

• Outputs : Technical Specifications and guidelines – Written by work groups + Associated to implementation (scenario based, definition of test suites)

→W3C standards define an Open Web Platform for application development

W3C standards Towards a Classification

• Universal use of the Web browser – The browser is the Troyan horse of the Web platform : apps platform – Satisfies ubiquitous needs – Easy to distribute

• HTML5 everywhere • Javascript

Classification of W3C standards The domains 1/2 • Web Design and Applications – Standards for building and rendering Web pages – Includes HTML, CSS, SVG, Ajax + Technologies for Web Applications (“WebApps”), Accessibility for people with disabilities (WCAG), Internationalization of pages, Pages for Mobile devices.

• Web Architecture – Foundation technologies and principles which sustain the Web (URIs, HTTP)

• Semantic Web – Build a technology stack to support a “Web of data” (linked data) – Enable computers to do more useful work, support trusted interactions – Technologies: RDF, SPARQL, OWL, SKOS... (Objects: Web Data stores, Vocabularies, Rules…)

Classification of W3C standards The domains 2/2 • XML Technology – XML, XML Namespaces, XML Schema, XSLT, Efficient XML Interchange (EXI)…

• Web of Services – Technologies HTTP, XML, SOAP, WSDL, and others. – Message-based design of applications

• Web of Devices – Technologies to enable Web access anywhere, anytime, using any device. – Web access from mobile devices, Web technology in consumer electronics, printers, interactive television, automobiles…

• Browsers and Authoring Tools – Publication of web pages and access regardless of the software, the computer, the language, etc.

2

1/13/2014

W3C Technology Stack

W3C and Ambiant computing

http://www.w3.org/Consortium/techstack-desc.html

W3C and ambient computing

Relation to W3C domains

Link with previous courses • Embedded Computing & Arduino (X. Serpaggi) Wireless Communications (J.P. Jamont) Android & Mobility (G. Picard)

• Embedded Computing & Arduino (X. Serpaggi) Wireless Communications (J.P. Jamont) Web of devices Android & Mobility (G. Picard)

– Sensors: Sound and light sensors – Mobile devices – URI, IRI, HTTP, IP

– Sensors: Sound and light sensors – Mobile devices – URI, IRI, HTTP, IP

• Context Modelling, Representation, Management (O. Boissier, A. Sorici) • Web of Things (A. Ciortea)

• Context Modelling, Representation, Management (O. Boissier, A. Sorici) • Web of Things (A. Ciortea)

– XML – Data, reasoning, ontologies (RDF, RDFS, OWL, Linked data, JSON)

– XML – Data, reasoning, ontologies (RDF, RDFS, OWL, Linked data, JSON)

• Sensors and the City (A. Fraboulet)

W3C Domain: Web of Devices Devices: Mobile phones Tablets Laptop Computers TV Cars Game console Ebook reader Music player Camera Glasses Watch Lightbulb ... • W3C Initiatives: Mobile Web ; Voice Browsing ; Device Independence and Content Adaptation ; Multimodal Access ; Web and TV • Numerous W3C Groups – Web & Mobile Interest Group – Web & TV Interest Group – Automotive Business Group – Web-based Signage Business Group – Digital Publishing Interest Group (etc.)

• Sensors and the City (A. Fraboulet)

Web design and applications Web Architecture

XML technologies Web of data

+ Web of services

Groups in the Mobile Web Initiative Web technologies Initiative

Web design and applications

Mobile Web Initiative Community Group Core Mobile Web Platform (2012)

Working groups

Web of devices

(etc.) WG Device API (2013)

Enriching HTML5: access WG Geolocation device’s camera, addressbook, (2008) calendar…. (from the browser) Interest Group Web and Mobile WG Web Real-Time (Webmob, Sept 2013) Communications (2011) Bringing peer-to-peer audio/video connections to the Web

3

1/13/2014

Category: Sensors and hardware integration

Standards for Web Applications on Mobile •

Current state and roadmap proposed by the Web and Mobile Interest Group (based on results from the Core Mobile Web Platform 2012 report).

• Categories (addressed by different WGs) – – – – – – – – – – – –

Graphics Multimedia Device Adaptation Forms User interactions Data storage Personal Information Management Sensors and hardware integration Network Communication_and_Discovery Packaging Performance & Optimization

Features Battery status Proximity sensors Ambient Light sensor Humidity sensor Geolocation Motion sensor Camera & Mic streams NFC (Near-Field Com.)

• Mobile devices are packed with sensors → Bridge between the real and virtual worlds • Sensors: GPS, accelerometer, ambient light detector, microphone, camera, thermometer, etc. • Mobile Web applications require dedicated APIs (JavaScript) • Device APIs Working Group (+ others) – Mission : create client-side APIs that enable the development of Web Applications and Web Widgets that interact with devices services such as Calendar, Accelerometer, Camera, etc.

Sensors and hardware integration

Development of a feature

Features addressed and WGs • WG Device API – – – – –

Battery status Proximity sensors* Ambient Light sensor * Humidity sensor * Vibration (belongs to User Interaction category)

• Organization

Features

• WG Geolocation

* Use

to be included in Sensor API (generic view)

– Geolocation (location of the device) – Motion sensor: orientation and acceleration data

• WG Web Real-Time Communications + Device APIs – Camera & Microphone streams (also in Multimedia category)

• WG NFC – NFC (Near-Field Communications)

– 1 W3C group is responsible (may be 2 WGs) – Effort deployed depends of the importance of the feature (needs, proposals)

• Indicators – – – – –

Stage of the specification (W3C Recommendation track) Estimated instability of the last document (low, medium, high) Latest editors draft of the document; Recent editing activity. Availability of implementations Availability of tutorial WebPlatform Docs, on-line training courses on W3DevCampus – Links to the test suite, and git repository

• WG System Applications – Global access to sensors and hardware (including USB and bluetooth).

Feature example: Battery status

Example: Battery status Attributes

• http://www.w3.org/TR/battery-status/

– readonly attribute boolean charging; – readonly attribute double chargingTime; – readonly attribute double dischargingTime;

• WG : Device API • Status: Candidate Recommendation • Date : 2012

– readonly attribute double level; Events – onchargingchange – onchargingtimechange – ondischargingtimechange – onlevelchange Example : writes the battery level to the console each time the level changes navigator.battery.onlevelchange = function () { console.log(navigator.battery.level); };

4

1/13/2014

W3C Domain: Web design and applications • Initiatives: – – – – – – – – –

HTML & CSS JavaScript Web APIs Graphics Audio and Video Accessibility Internationalization Mobile Web Privacy Math on the Web

Specific or generic technologies for mobiles? • Technologies developed to fit mobile devices – CSS Mobile, the cascading style sheet language for mobile Web authors – SVG Tiny, Web’s scalable vector graphics format wellsuited to the capabilities of mobile devices – XHTML for Mobile, subset of XHTML

AND/BUT • Classic “Desktop” is available on mobile devices – Latest generation of mobile browsers support (HTML5, CSS 2.1 and 3, rich JavaScript APIs, …)

W3C Domain: Web Architecture • Initiatives – – – – – –

Architecture Principles Identifiers  URI, IRI, Protocols  HTTP, SOAP Meta Formats  XML, RDF Protocol and Meta Format Considerations Internationalization

• Note: ReST does not belong to W3C standard.

Mobile Web Related specifications – Mobile Web Authoring – Device Independence Authoring – CSS Mobile – SVG Tiny – XHTML For Mobile – Mobile Web Applications – Mobile Web for Social Development – Geospatial

Mobile web applications Best practice WG • List of 32 Best Practices (W3C Recommendation, 2010) -Do not Send Cookie Information Unnecessarily -Preserve Focus on Dynamic Page Updates -Make Telephone Numbers "Click-to-Call" For each : What it means? How to do it? • Main contributors from Vodafone (2), dotMobi, W3C (2), Rochester Institute of Technology http://www.w3.org/TR/2010/REC-mwabp-20101214/

ReST: Representational State Transfer • REST is not a "standard“. Proposed in a PhD thesis (2000) • Uses HTTP requests (Create/Read/Update/Delete, like the Web) to connect between machines. Stateless, clientserver communication. • Lightweight mechanism. Avoids complex mechanisms such as CORBA, RPC or SOAP to connect between machines. • Inspiring the W3C – “Reconciling Web Services and REST Services” (Haas, W3C Web Services Activity Lead, 2005) – “Architecture of the World Wide Web” (Jacobs, Head of Marketing and Communications, 2003)

http://rest.elkstein.org/

5

1/13/2014

W3C Domain: Web of Data Semantic web

W3C Domain: XML Technologies Nothing special related to Ambient Computing Thanks for being here!

Initiatives: – – – – –

Vocabularies Linked Data Query Inference Vertical Applications

Web of Data Models for Ambient Computing?

Specifications produced • • • • • • • • • • • • • •

OWL Web Ontology Language SKOS RDF, RDF Best Practices, RDFa RDF Relationship to Other Formats GRDDL POWDER Semantic Annotation for WSDL and XML Schema Provenance RDB2RDF Linked Data SPARQL RIF Rule Interchange Format Health Care and Life Sciences (Semantic Web) Government Linked Data, eGovernment

Not specific to Ambient computing

• Modeling knowledge and reasoning – Ontologies: OWL, SKOS, RIF

• Sharing, integrating – RDF, RDFa

• Model for distributed data/knowledge – Linked Data Sensor Sensor

Data collection

Sensor

Semantic Sensor Network • Context – Collection of avalanches of data about the world – Too much data and not enough knowledge

• Proposal : Sensor data can be annotated with semantic metadata (ontologies, linked data, rules) – increases interoperability between heterogeneous sources, provides integration – provides contextual information essential for situation awareness (discovery, reasoning, classification)

• Incubator group (2009-2011)

Integration Representation Knowledge extraction

Semantic Sensor Network • Incubator group proposal – an ontology to describe sensors and sensor networks for use in sensor network and sensor web applications – Recommendations for using the ontology to semantically enable applications http://www.w3.org/2005/Incubator/ssn/XGR-ssn20110628/#Surveys_of_Sensor_and_Observation_ontologies

• SSN Ontology – Mapping with the Open Geospatial Consortium (OGC) standards. – High-level specifications to describe, manage, query, understand and control sensors and sensed data – Encoded in OWL; Has to be specialized for each case

6

1/13/2014

SSN ontology

Community groups (2012-..) • Semantic Sensor Network CG – Continues the work of the SSN IG – Access point for ontologies and technologies developed for semantic sensor networks.

• Web of Sensors CG – Interaction Web platform Sensors – For instance, how do we hook up an Arduino and interact with it through the Web platform? – Safe exposition of sensor data to Web platforms, Protection of user's privacy

Other recent topics

Next topics

• JSON LD http://www.w3.org/TR/json-ld/ – RDF model (linked data) serialized in JSON – Proposed by RDF WG in November 2013 – Reduced size of messages (avoids closing markups)

• PROV Provenance http://www.w3.org/TR/prov-overview/

(till 2013)

– Producing of data (or things) requires assessments about its quality, reliability or trustworthiness – It’s about entities, activities, and people, and heterogeneous environments – Next step: Mixing Provenance and SSN

• Browser stack, SW stack, XML stack, SOAP stack… – Developer’s choice. Where to start? too much choice?

• Constrains of devices. What will be applicable (storage, CPU) • Dealing with data streams

W3C Domain: Web of Services • W3C Initiatives and specifications – Protocols • HTTP • SOAP • Web Services Addressing / Web Services Architecture

– Service Description • • • • • • •

WSDL Web Services Choreography Web Services Policy Semantic Annotation for WSDL and XML Schema XML Schema Service Modeling Language (SML) Web Services Resource Access

– Security

Conclusion • W3C – Organism for standard development – Based on consensus and royalty-free

• W3C and Ambient computing – Transversal domain – Many opportunities for applications – Many opportunities for research

• XML Encryption / XML Signature / XKMS

– Internationalization

7