W3C and Ambient Computing Public Pages of the W3C Web Sites

1/13/2014

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

Pierre Maret January 2013

Agenda W3C

• W3C mission and organization • Mission • W3C standards classification – Ensure the long-term growth of the Web (“Lead • Situating Ambient computing in the W3C areas the Web to its Full Potential”) – Web of Devices – Through developing and standardizing – Web of Design and applications technologies, protocols and guidelines – Web Architecture – Make the Web work for everyone, everywhere on – XML technologies every device – Web of Data – Royalty-Free Technologies (open standards) – Web of Services

Processes of the W3C Stakeholder and W3C processes Stakeholders • 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 W3C method and outputs 1. “Editors drafts” : current view of the editors of the specification • (no standing in terms of standardization). Method 2. “Working Drafts” (WD): early milestones of the Working Group – Buttom-up (WG) progress. – Implementation (widely deployable and interoperable) 3. “Last Call Working Drafts”: the specification fulfills the WG requirements. They requests feedback from the larger community. – Maximize consensus 4. “Candidate Recommendations” (CR): implementers are invited to • implement the specification and send feedback; WG is expected Outputs : Technical Specifications and guidelines to show the specification gets implemented by running test suites – Written by work groups they have developed. + 5. “Proposed Recommendations” (PR): Once the WG has gathered Associated to implementation (scenario based, sufficient implementation experience; triggers the final review by definition of test suites) W3C Members. →W3C standards define an Open Web Platform for 6. “W3C Recommendations” (Rec): stable and completed Web standards; updated through the “Edited Recommendation” application development process (minor revisions).

W3C standards Current strategy of the W3C in 2013 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 Classification of W3C standards The domains 1/2 The domains 2/2 • Web Design and Applications • XML Technology – Standards for building and rendering Web pages – XML, XML Namespaces, XML Schema, XSLT, Efficient XML Interchange – Includes HTML, CSS, SVG, Ajax + Technologies for Web Applications (EXI)… (“WebApps”), Accessibility for people with disabilities (WCAG), • Web of Services Internationalization of pages, Pages for Mobile devices. – Technologies HTTP, XML, SOAP, WSDL, and others. • Web Architecture – Message-based design of applications – Foundation technologies and principles which sustain the Web (URIs, • Web of Devices HTTP) – Technologies to enable Web access anywhere, anytime, using any • Semantic Web device. – Build a technology stack to support a “Web of data” (linked data) – Web access from mobile devices, Web technology in consumer – Enable computers to do more useful work, support trusted electronics, printers, interactive television, automobiles… interactions • Browsers and Authoring Tools – Technologies: RDF, SPARQL, OWL, SKOS... (Objects: Web Data stores, – Publication of web pages and access regardless of the software, the Vocabularies, Rules…) 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) • Embedded Computing & Arduino (X. Serpaggi) Wireless Communications (J.P. Jamont) Wireless Communications (J.P. Jamont) Android & Mobility (G. Picard) Android & Mobility (G. Picard) Web of devices – Sensors: Sound and light sensors – Sensors: Sound and light sensors – Mobile devices – Mobile devices Web design and – URI, IRI, HTTP, IP – URI, IRI, HTTP, IP applications • Context Modelling, Representation, • Context Modelling, Representation, Web Architecture Management (O. Boissier, A. Sorici) Management (O. Boissier, A. Sorici) • Web of Things (A. Ciortea) • Web of Things (A. Ciortea) – XML – XML XML technologies – Data, reasoning, ontologies – Data, reasoning, ontologies (RDF, RDFS, OWL, Linked data, JSON) (RDF, RDFS, OWL, Linked data, JSON) Web of data • • Sensors and the City (A. Fraboulet) Sensors and the City (A. Fraboulet) + Web of services

W3C Domain: Web of Devices Groups in the Mobile Web Initiative

Web design and Web of Devices: Mobile phones Tablets Laptop Computers TV Cars Web technologies applications devices Game console Ebook reader Music player Camera Glasses Watch Lightbulb ... Initiative Mobile Web Initiative • W3C Initiatives: Mobile Web ; Voice Browsing ; Device Independence and Community Group Core Mobile Web Platform Content Adaptation ; Multimodal Access ; Web and TV (2012) (etc.) • Numerous W3C Groups WG Device API (2013) WG Geolocation Enriching HTML5: access – Web & Mobile Interest Group Working groups (2008) device’s camera, addressbook, calendar…. (from the browser) – Web & TV Interest Group Interest Group Web and Mobile – Automotive Business Group WG Web Real-Time (Webmob, Sept 2013) Communications (2011) – Web-based Signage Business Group Bringing peer-to-peer audio/video – Digital Publishing Interest Group (etc.) connections to the Web

3 1/13/2014

Category: Sensors and hardware Standards for Web Applications on Mobile integration • Current state and roadmap proposed by the Web and Mobile Interest Group (based on results from the Core Mobile Web Platform 2012 report). • Mobile devices are packed with sensors → Bridge • Categories (addressed by different WGs) between the real and virtual worlds – Graphics • Sensors: GPS, accelerometer, ambient light – Multimedia detector, microphone, camera, thermometer, etc. – Device Adaptation – Forms Features • Mobile Web applications require dedicated APIs – User interactions (JavaScript) – Data storage Battery status – Personal Information Management Proximity sensors • Device APIs Working Group (+ others) – Sensors and hardware integration Ambient Light sensor – Mission : create client-side APIs that enable the – Network Humidity sensor – Communication_and_Discovery development of Web Applications and Web Widgets Geolocation that interact with devices services such as Calendar, – Packaging Motion sensor – Performance & Optimization Camera & Mic streams Accelerometer, Camera, etc. NFC (Near-Field Com.)

Sensors and hardware integration Development of a feature Features addressed and WGs • WG Device API Features • Organization – Battery status – – Proximity sensors* 1 W3C group is responsible (may be 2 WGs) – Ambient Light sensor * – Effort deployed depends of the importance of the feature * Use to be * (needs, proposals) – Humidity sensor included in – Vibration (belongs to User Interaction category) Sensor API • Indicators (generic view) • WG Geolocation – Stage of the specification (W3C Recommendation track) – Geolocation (location of the device) – Estimated instability of the last document (low, medium, high) – Motion sensor: orientation and acceleration data – Latest editors draft of the document; Recent editing activity. • WG Web Real-Time Communications + Device APIs – Availability of implementations – Camera & Microphone streams (also in Multimedia category) – Availability of tutorial WebPlatform Docs, on-line training • WG NFC courses on W3DevCampus – NFC (Near-Field Communications) – 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 – readonly attribute double level; Events • Status: Candidate Recommendation – onchargingchange – onchargingtimechange • Date : 2012 – 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 Mobile Web applications Related specifications • Initiatives: – Mobile Web Authoring – HTML & CSS – Device Independence Authoring – JavaScript Web APIs – CSS Mobile – Graphics – SVG Tiny – Audio and Video – – Accessibility XHTML For Mobile – Internationalization – Mobile Web Applications – Mobile Web – Mobile Web for Social Development – Privacy – Geospatial – Math on the Web

Specific or generic Mobile web applications technologies for mobiles? Best practice WG • Technologies developed to fit mobile devices • List of 32 Best Practices (W3C Recommendation, 2010) – CSS Mobile, the cascading style sheet language for -Do not Send Cookie Information Unnecessarily mobile Web authors -Preserve Focus on Dynamic Page Updates – SVG Tiny, Web’s scalable vector graphics format well- suited to the capabilities of mobile devices -Make Telephone Numbers "Click-to-Call" – XHTML for Mobile, subset of XHTML For each : What it means? How to do it? AND/BUT • Main contributors from Vodafone (2), dotMobi, • Classic “Desktop” is available on mobile devices W3C (2), Rochester Institute of Technology – Latest generation of mobile browsers support http://www.w3.org/TR/2010/REC-mwabp-20101214/ (HTML5, CSS 2.1 and 3, rich JavaScript APIs, …)

W3C Domain: Web Architecture ReST: Representational State Transfer

• Initiatives • REST is not a "standard“. Proposed in a PhD thesis (2000) – Architecture Principles • Uses HTTP requests (Create/Read/Update/Delete, like the – Identifiers  URI, IRI, Web) to connect between machines. Stateless, client- server communication. – Protocols  HTTP, SOAP • Lightweight mechanism. Avoids complex mechanisms such – Meta Formats  XML, RDF as CORBA, RPC or SOAP to connect between machines. – Protocol and Meta Format Considerations • Inspiring the W3C – Internationalization – “Reconciling Web Services and REST Services” (Haas, W3C Web Services Activity Lead, 2005) – “Architecture of the World Wide Web” (Jacobs, Head of Marketing • Note: ReST does not belong to W3C standard. and Communications, 2003) http://rest.elkstein.org/

5 1/13/2014

W3C Domain: Web of Data W3C Domain: XML Technologies Semantic web Nothing special related to Ambient Computing Initiatives: – Vocabularies Thanks for being here! – Linked Data – Query – Inference – Vertical Applications

Web of Data Models for Specifications produced Ambient Computing? • OWL Web Ontology Language • SKOS • RDF, RDF Best Practices, RDFa • Modeling knowledge and reasoning • RDF Relationship to Other Formats • GRDDL – Ontologies: OWL, SKOS, RIF • POWDER • Semantic Annotation for WSDL and XML Schema • Sharing, integrating • Provenance • RDB2RDF – RDF, RDFa • Linked Data • SPARQL • Model for distributed data/knowledge • RIF Rule Interchange Format • Health Care and Life Sciences (Semantic Web) – Linked Data • Government Linked Data, eGovernment Sensor Data Integration Sensor Not specific to Ambient computing collection Representation Sensor Knowledge extraction

Semantic Sensor Network Semantic Sensor Network

• Context • Incubator group proposal – Collection of avalanches of data about the world – an ontology to describe sensors and sensor networks for use in sensor network and sensor web applications – Too much data and not enough knowledge – Recommendations for using the ontology to semantically • Proposal : Sensor data can be annotated with semantic enable applications http://www.w3.org/2005/Incubator/ssn/XGR-ssn- metadata (ontologies, linked data, rules) 20110628/#Surveys_of_Sensor_and_Observation_ontologies – increases interoperability between heterogeneous • SSN Ontology sources, provides integration – Mapping with the Open Geospatial Consortium (OGC) – provides contextual information essential for situation standards. awareness (discovery, reasoning, classification) – High-level specifications to describe, manage, query, • Incubator group (2009-2011) 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