DOCSLIB.ORG

WP1 Standardization Report

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
WP1 Standardization Report FP7-611327—HTML5Apps HTML5 for Apps: Closing the Gaps HTML5APPS DELIVERABLE D1.1 STANDARDIZATION REPORT D1.1 - Standardization Report (M12) Page 1 of 298 FP7-611327—HTML5Apps HTML5 for Apps: Closing the Gaps Project Grant Agreement number 317862 Project acronym: HTML5Apps Project title: HTML5Apps: Closing the Gaps Funding Scheme: Coordination & Support Action Date of latest version of Annex I against which the assessment will May 24, 2013 be made: Document Deliverable number: D1.1 Deliverable title Standardization report Contractual Date of Delivery M12 Actual Data of Delivery: M12 Editor(s): Dr. Dave Raggett Author(s): Reviewer(s): Partipant(s): Work package no.: 1 Work package title: WebOS APIs Work package leader: Dr. Dave Raggett Distribution: PU Version/Revision: Draft/Final: Final Total number of pages (including 298 cover): Keywords: D1.1 - Standardization Report (M12) Page 2 of 298 FP7-611327—HTML5Apps HTML5 for Apps: Closing the Gaps DISCLAIMER This document contains description of the HTML5Apps project work and findings. The authors of this document have taken any available measure in order for its content to be accurate, consistent and lawful. However, neither the project consortium as a whole nor the individual partners that implicitly or explicitly participated in the creation and publication of this document hold any responsibility for actions that might occur as a result of using its content. This publication has been produced with the assistance of the European Union. The content of this publication is the sole responsibility of the HTML5Apps consortium and can in no way be taken to reflect the views of the European Union. The European Union is established in accordance with the Treaty on European Union (Maastricht). There are currently 27 Member States of the Union. It is based on the European Communities and the member states cooperation in the fields of Common Foreign and Security Policy and Justice and Home Affairs. The five main institutions of the European Union are the European Parliament, the Council of Ministers, the European Commission, the Court of Justice and the Court of Auditors. (http://europa.eu/index_en.html) HTML5Apps is a project funded in part by the European Union. D1.1 - Standardization Report (M12) Page 3 of 298 FP7-611327—HTML5Apps HTML5 for Apps: Closing the Gaps TABLE OF CONTENTS 1. Introduction . 5 2. Execution and Security Models . 7 2.1. Status of Work. 7 2.2. Trust and Permissions. 8 2.2.1. White Paper . 8 2.2.2. Paris Meeting. 9 3. Application Programming Interfaces (APIs). 13 3.1. Alarm API/Task Scheduler API . 13 3.2. Contacts API . 13 3.3. Messaging API . 13 3.4. Telephony API . 13 3.5. Raw Socket API/TCP UDP Sockets API. 14 3.6. Bluetooth API . 14 3.7. Secure elements API . 14 4. Planning Future Work . 15 5. Conclusions . 17 APPENDICES A. Whitepaper: Handling Trust and Permissions in Web Applications. 19 B. Minutes from meeting on trust and permissions for Web applications65 C. Manifest for web apps and bookmarks . 89 D. The app: URL Scheme . 107 E. Application Lifecycle and Events . 112 F. Task Scheduler API . 122 G. Contacts Manager API . 130 H. Messaging API . 142 I. Telephony API . 177 J. TCP and UDP Socket API . 210 K. Web Bluetooth . 237 L. Secure Element API . 280 D1.1 - Standardization Report (M12) Page 4 of 298 FP7-611327—HTML5Apps HTML5 for Apps: Closing the Gaps 1. INTRODUCTION This report describes the HTML5Apps project's achievements in in terms of standardizing WebOS APIs (including standardization documents). At the outset of the HTML5Apps project, HTML5 standards were designed to cope with the user visiting untrusted web sites, necessitating a cautious approach to security that narrowly limited what a particular website can do (limited access to OS, network, and browser data through browser sandbox, avoid fingerprinting of users etc.). This limited the type of apps that could be written using HTML5. It was assumed that closing the gap between HTML5 apps and native apps would require defining a runtime environment, security model, and associated APIs for building Web applications with comparable capabilities to native applications. This means stronger integration with the host platform than is the case for traditional web pages. Today’s Web operating systems such as Tizen and FirefoxOS typically include the following components for which no standardized solution exists today: • Execution Model: A description of the execution model and associated APIs for HTML5 applications, that differs from the traditional browser- based execution model. • Security Model: A description of the security model and associated APIs for HTML5 applications that differs from the traditional browser-based security model. Moreover, Web operating systems include a number of APIs which are also not standardized: • Alarm API: An API to manage the system's alarm daemon. • Contacts API: An API that enables complete management of the device's address books. • Messaging API: An API to send and receive messages (e.g. SMS, MMS, Email, and IM) as well as manage messages stored on the device. • Telephony API: An API to interact with the phone system, for instance to dial a number, pick up a call, route to voicemail, access the call log, etc. • Raw Sockets API: An API to manipulate low-level connections (e.g. TCP, UDP), including the ability to listen for incoming connections. • Bluetooth API: A low-level API to interact with the Bluetooth hardware available on some devices. • Browser API: An API that provides all the necessary items to build a Web browser that aren't otherwise available. Most notably, this provides all that is needed in order to safely instantiate a viewport onto the open Web, pretend that such a viewport is the top level window even if the browser's chrome is itself written using Web technology, etc.. D1.1 - Standardization Report (M12) Page 5 of 298 FP7-611327—HTML5Apps HTML5 for Apps: Closing the Gaps • Calendar API: An API that enables complete management of the device's calendars. • Device Capabilities API: An API that exposes the capabilities available to the device. • Idle API: An API to be notified when the user is idle. • Media Storage API: An API to manage the device's storage of specific content types (e.g. pictures). • Network Interface API: An API to manipulate network interfaces (mobile, WiFi, etc.), such as listing available networks, current strength, etc., as well as configuring and enabling them. Potential uses include offloading connections from mobile networks to WiFi, enabling high priority mobile data connections and control of other network features. • Secure Elements API: An API enabling the discovery, introspection, and interaction with hardware tokens (Secure Elements) that offer secure services such as tamperproof storage, cryptographic operations, etc. • System Settings API: An API to manage the system's settings (e.g. time/ clock settings, and personal preferences including privacy preferences). For HTML5 apps to realize their full potential as non-proprietary, open alternative to today’s native app environments, further functionality needs to be added to the relevant standards. In order to develop these standards, members of the HTML5Apps project team are filling in the role of so-called “W3C team contacts” in relevant W3C standardization Working Groups. A W3C team contact acts as the interface between the Group Chair (“Chair”), Group Members, and the W3C Team. Many of the team contact’s tasks involve helping the Chair complete his or her roles, while others involve direct action from the Contact. The team contact role is largely one of communication. This involves becoming as aware as possible of the technical requirements and issues in the group, and simultaneously being aware of the general architecture of the Web as evolving in the other work of W3C. In particular, the work of team contacts include the following tasks: • Assist Group organizers in maintaining charter and convening Group • Monitor group participation and operations • Monitor levels of active participation and address as needed. • Serve as Contact between WG and rest of the W3C Team (team contacts of other groups, marketing, management etc.) This report is structured as follows: In Section 2, we report on the status of work on the execution and security model, with particular focus on the work on permissioning. In Section 3, we report on the status of work on individual APIs. In Section 4, we give an overview of future work planning. Section 5 concludes this report. Appendices provide background materials and standardization documents. Please note that this document includes hypertext links to background materials including draft specifications. This can be followed when viewing the electronic version of this document. D1.1 - Standardization Report (M12) Page 6 of 298 FP7-611327—HTML5Apps HTML5 for Apps: Closing the Gaps 2. EXECUTION AND SECURITY MODELS 2.1. STATUS OF WORK Work started with submissions from working group participants in the W3C Systems Applications (SysApps) WG: Execution Model A description of the execution model and associated APIs for system applications, particularly how the execution model differs from the traditional browser-based execution model. Example: Strawman proposal from Google. Security Model A description of the security model and associated APIs for system applications, particularly how the security model differs from the traditional browser-based security model. Examples and further background: • Strawman proposal from Google, • B2G Security Model, • W3C Workshop in 2008 on Security for Access to Device APIs from the Web, • The WAC core security specifications • The BONDI App Security Framework • Chrome extensions security model and permissions • The webinos security model • The Widgets security model landscape analysis from 2008 • The security controls introduced by 'Gibraltar' These contributions were reworked by editors from Mozilla and Samsung into a draft specification. • Runtime and Security Model for Web Applications The draft described: • How an application is defined through an application manifest and how it can be installed, updated and packaged.
Load more

Recommended publications
  • Aalborg Universitet Mobile Platforms -An Analysis of Mobile
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by VBN Aalborg Universitet Mobile Platforms -An analysis of Mobile Operating Systems and Software development platforms Hammershøj, Allan; Sapuppo, Antonio; Tadayoni, Reza Publication date: 2009 Document Version Publisher's PDF, also known as Version of record Link to publication from Aalborg University Citation for published version (APA): Hammershøj, A., Sapuppo, A., & Tadayoni, R. (2009). Mobile Platforms: -An analysis of Mobile Operating Systems and Software development platforms. Paper presented at CMI International Conference on Social Networking and Communities, Ballerup, Denmark. General rights Copyright and moral rights for the publications made accessible in the public portal are retained by the authors and/or other copyright owners and it is a condition of accessing publications that users recognise and abide by the legal requirements associated with these rights. ? Users may download and print one copy of any publication from the public portal for the purpose of private study or research. ? You may not further distribute the material or use it for any profit-making activity or commercial gain ? You may freely distribute the URL identifying the publication in the public portal ? Take down policy If you believe that this document breaches copyright please contact us at [email protected] providing details, and we will remove access to the work immediately and investigate your claim. Downloaded from vbn.aau.dk on: November 29, 2020 Mobile Platforms -An analysis of Mobile Operating Systems and Software development platforms Allan Hammershøj, Antonio Sapuppo and Reza Tadayoni Center for Communication, Media and Information technologies (CMI) Aalborg University {allan, antonio, reza}@cmi.aau.dk The paper is developed for presentation at: CMI international conference on social networking and communities 25-26 November 2009 Copenhagen, Denmark Abstract: Mobile Social Networking is becoming a reality driven by the introduction and further development of smartphones.
    [Show full text]
  • Aalborg Universitet Mobile Platforms -An Analysis of Mobile Operating
    Aalborg Universitet Mobile Platforms -An analysis of Mobile Operating Systems and Software development platforms Hammershøj, Allan; Sapuppo, Antonio; Tadayoni, Reza Publication date: 2009 Document Version Publisher's PDF, also known as Version of record Link to publication from Aalborg University Citation for published version (APA): Hammershøj, A., Sapuppo, A., & Tadayoni, R. (2009). Mobile Platforms: -An analysis of Mobile Operating Systems and Software development platforms. Paper presented at CMI International Conference on Social Networking and Communities, Ballerup, Denmark. General rights Copyright and moral rights for the publications made accessible in the public portal are retained by the authors and/or other copyright owners and it is a condition of accessing publications that users recognise and abide by the legal requirements associated with these rights. ? Users may download and print one copy of any publication from the public portal for the purpose of private study or research. ? You may not further distribute the material or use it for any profit-making activity or commercial gain ? You may freely distribute the URL identifying the publication in the public portal ? Take down policy If you believe that this document breaches copyright please contact us at [email protected] providing details, and we will remove access to the work immediately and investigate your claim. Downloaded from vbn.aau.dk on: September 25, 2021 Mobile Platforms -An analysis of Mobile Operating Systems and Software development platforms Allan Hammershøj, Antonio Sapuppo and Reza Tadayoni Center for Communication, Media and Information technologies (CMI) Aalborg University {allan, antonio, reza}@cmi.aau.dk The paper is developed for presentation at: CMI international conference on social networking and communities 25-26 November 2009 Copenhagen, Denmark Abstract: Mobile Social Networking is becoming a reality driven by the introduction and further development of smartphones.
    [Show full text]
  • Hell Is Other Browsers - Sartre HTML5 Apps on Samsung Bada (And Other Platforms)
    Hell is other browsers - Sartre HTML5 apps on Samsung bada (and other platforms) Peter-Paul Koch (ppk) http://quirksmode.org http://twitter.com/ppk Samsung bada dev day, 3 June 2010 Creating applications Modern smartphone users want applications; bada users will not be different. Two options: 1) native apps 2) HTML5 apps Creating applications Native apps will be discussed in detail in other sessions. This session concentrates on HTML5 apps. Differences Native apps are written in C++, compiled, and installed on the phone. Pros: 1) Excellent performance, especially when it comes to graphics and animations 2) Access to device APIs 3) IDE Differences Native apps are written in Java, compiled, and installed on the phone. Cons: 1) Only available for bada; what if your target audience is larger than that? Differences HTML5 apps are written with web standards, zipped, and installed on the phone, where they run in the browser. Pros: 1) Available on any device with a modern browser and W3C Widget support Differences HTML5 apps are written with web standards, zipped, and installed on the phone, where they run in the browser. Cons: 1) Less beautiful UX 2) No (or little) access to device functionality such as camera, address book, or voice. Which one to choose? A) It's important that my app has the best UX possible, and that it can access phone functionality B) It's important that my app runs on any platform. Which one to choose? A) It's important that my app has the best UX possible, and that it can access phone functionality => Native apps B) It's important that my app runs on any platform.
    [Show full text]
  • Open Model for the Distribution of Mobile Applications on Multiple Platforms
    DIPLOMARBEIT Titel der Diplomarbeit „Concept of a distribution and infrastructure model for mobile applications development across multiple mobile platforms― Verfasserin / Verfasser Peter Bacher Angestrebter akademischer Grad Magister der Sozial- und Wirtschaftswissenschaften (Mag. rer. soc. oec.) Wien, 2011 Studienkennzahl lt. Studienblatt: A 157 Studienrichtung lt. Studienblatt: Diplomstudium Internationale Betriebswirtschaft Betreuer/: Univ.-Prof. Dr. Dimitris Karagiannis Erklärung Hiermit versichere ich, die vorliegende Diplomarbeit ohne Hilfe Dritter und nur mir den angegebenen Quellen und Hilfsmitteln angefertigt zu haben. Alle Stellen, die den Quellen entnommen wurden, sind als solche kenntlich gemacht worden. Diese Arbeit hat in gleicher oder ähnlicher Form noch keiner Prüfungsbehörde vorgelegen. Wien, 05.12.2011 ————————– Peter Bacher Page 2 Table of Contents Table of Contents ..................................................................................................... 3 1 Introduction ..................................................................................................... 10 1.1 Motivation ................................................................................................. 10 1.2 General problem statement ...................................................................... 11 1.3 Goal of the Thesis ..................................................................................... 12 1.4 Approach .................................................................................................
    [Show full text]
  • Publishing Mobile Games in a Multi-Platform, Multi-Store Environment
    Publishing Mobile Games in a multi-platform, multi-store environment by Maarten Noyons NCC Partners and founder of the IMGA Who I am o Maarten Noyons CEO of Noyons Content Consultancy (NCC) o advises Media Companies, Content Houses, Operators, handset manufacturers and government organisations, o creates the International Mobile Gaming Awards in 2004, the largest competition for Mobile Games in the World o creates the Playground festival for Real World Games in Marseille, France Contents Key figures of the Mobile Games Market, The key issues, Overview of the different paths to the consumer, Analysis, Recommendations and your questions Key Figures Installed Base Operating Systems and Platforms App Stores Trends Installed base, worldwide PC PC 850 TV TV 1900 MobileMobile phones 3300 Source: Screendigest, Gartner, GSMA Smartphones shipped as a percentage of all mobile phones worldwide (in Mln.) Smartphones 140 Mobile phones 3300 Smartphones and handheld installed base Smartphone market shares 12+ Operating Systems J2ME SUN, now Oracle BREW Qualcomm Linux Open Source Maemo Nokia, Linux based Android Google, multi-OEM Bada Samsung, Linux based Windows Mobile Microsoft PalmOS Palm OS X (iPhone) Apple Symbian Symbian Foundation MeeGo Intel and Nokia RIM OS Research in Motion Highly Fragmented RIM OS J2ME Windows Mobile Symbian Android Linux - installed base + PalmOS BREW Bada OS X (iPhone) Meamo (MeeGo) Less Fragmented In Q3 2011 we could start seeing the presence of MeeGo and Bada Source: Strategy Analytics History of App
    [Show full text]
  • W3C WIDGETS a Solution for Implementing Platform-Independent Mobile Applications
    W3C WIDGETS A Solution for Implementing Platform-independent Mobile Applications Stefan Schäfer, Stefan Christmann Application Systems and e-Business, University of Göttingen, Platz der Göttinger Sieben 5, Göttingen, Germany Svenja Hagenhoff Institute of Media Management, University of Applied Sciences St. Poelten, St. Poelten, Austria Keywords: Widget, Mobile application, Platform-independency. Abstract: The mobile internet is very heterogeneous at all levels - this is true for end devices as well as for operating systems and runtime environments of mobile applications. Therefore all software providers face the challenge of developing platform-independent applications and making them usable on a maximum number of end devices. One possible way of doing this is provided by Widgets - small software programs with a limited functional scope that are executed by a Widget-engine. This article looks at the state of development of the most important W3C Widget-standards and analyses their prospects of success. 1 INTRODUCTION 2008, p.2). Both products are mainly solutions for the existing variety of different platforms. W3C, on The mobile internet poses great challenges for the other hand, tries to counterbalance the great software providers as well as for customers, because variety of software development solutions by its it is a strongly fragmented market with a multitude Widget-standard and to find platform-independent of different producers of end devices and platforms solutions for applications with a low functional for the production and supply of software (Gartner, scope in order to access a maximum number of end 2010; Admob, 2010, p.6). Customers who change to users. a new device often find it difficult or even Jaokar and Fish (2006, p.99) define a Widget as impossible to use their former applications on the a "downloadable, interactive software object that new end device and to transfer their data.
    [Show full text]
  • Cross-Platform Mobile Development
    Medical Mobile Development Project: D4 Cross-platform mobile development March 2011 Authors Address for correspondence Gustavo Hartmann Tribal Geoff Stead Lincoln House, The Paddocks Asi DeGani 347 Cherry Hinton Road Cambridge CB1 8DH United Kingdom [email protected] Web addresses License www.mole-project.net This work is licensed under the Creative Commons www.triballabs.net Attribution-NonCommercial 3.0 Unported License. To view a copy of this license, visit http://creative- www.m-learning.org commons.org/licenses/by-nc/3.0/ or send a letter to Creative Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041, USA. This work relates to a Department of the Navy Grant N62909-11-1-1032 issued by the Office of Naval Research Global (ONRG) and funded by the U.S. Army Medical Research and Material Command, Telemedicine and Advanced Technology Research Center (TATRC) entitled Medical Mobile Development Project. Cross-platform mobile development – March 2011 1 Introduction Developing effective learning solutions for mobile delivery involves multiple disciplines and a wide range of technologies. Learning applications should be engaging, deliver a consistently meaningful user experience across different devices and work seamlessly both online and offline. This may sound simple in theory, but is in fact highly complex, technically, due to a range of factors such as the highly fragmented mobile technology landscape, rapidly evolving standards, limitations imposed by the mobile device itself (screen size, input methods, display capabilities, etc.) and also constraints of the mobile network such as high latency and low bandwidth. As mobile applications become increasingly popular and the technology moves into mainstream, the demand for sustainable practices and tools for building and supporting ongoing development becomes apparent.
    [Show full text]
  • HTML, CSS, Javascript Only  Iwebkit  Jqtouch (Jquery Touch)  Iui (Iphone User Interface)  Sencha Touch
    MLJ11 Tips, Techniques, and Tools for Mobile Learning Jason Haag, ADL Kris Rockwell, Hybrid Learning Systems Tips, Techniques and Tools HOSTED BY: Jason Haag, Advanced Distributed Learning Kris Rockwell, Hybrid Learning Systems Rule #1: Forget what you think you know Rule #2: Believe what you see, not what you read. Rule #3: Don’t start with constraints. Rule #4: Focus on context, goals, and needs. Rule #5: You can’t support everything. Rule #6: Don’t convert, create! Rule #7: Keep it simple. From “Mobile Design and Development: Practical Concepts and Techniques for Creating Mobile Sites and Web Apps” by Brian Fling Beyond Control: Hardware failure Connectivity Security Performance Fragmentation Can Be Addressed: No standardized screen size or resolution Native Apps can require many platforms to support Mobile Web Apps can require many browsers to support App Description Cost 1Password Encrypted password storage $9.99 Facebook Facebook client Free InstaPaper Offline reading Free TweetDeck Twitter client Free Yelp Augmented search Free Symbian OS from the Symbian Foundation BlackBerry OS from RIM iOS from Apple Windows Mobile 6 from Microsoft Windows Phone 7 from Microsoft Android from Google WebOS from HP Bada from Samsung MeeGo from Nokia and Intel Maemo from Nokia Limo (Linux) Integrated Development Cross-Platform Programming Language Emulator available Development Tool Cost Environment Deployment All native: BREW, Android, iPhone, Visual Studio, Mac OS Commercial licenses AirplaySDK C, C++ but no threads Emulator
    [Show full text]
  • Mobile Middleware Course Mobile Platforms and Middleware Sasu
    Mobile Middleware Course Mobile Platforms and Middleware Sasu Tarkoma Applications Middleware provides various Middleware transparencies (HW, OS, location, fault, ..) for apps. Transport LayerAPIs (TCP/UDP) for: RPC, messaging, transactions, session management, storage, directories, trading, etc. Networking Layer (IP) Underlying network (link layer, physical) The Hourglass diverse applications divergence transport layer (TCP/IP) convergence diverse physical layers Mobile Platforms Collections of central services and libraries with both reactive and proactive functions APIs typically logically centralized Distributed between elements of the environment Multi-tier client-server Peer-to-peer Hybrids The platform running on the mobile terminal and the characteristics of the device determine how service is rendered for the end user Wireless and Cloud Wireless hop is the limiting factor Bandwidth, connectivity, reachability, tail energy, costs Server side scalability can be achieved by using traditional solutions: clusters, caching, geographical distribution, load balancing, data centers Cloud computing Integration, offloading Web apps vs. native apps Mobile Service Development The mobile landscape is fragmented Heterogeneous device base Many different wireless technologies The situation is challenging for the developer Many APIs Open vs. private APIs Many middleware platforms APIs evolve over time Current challenge of the industry pertains to improving the development processes PC World Mobile World Idea Idea SW-Design
    [Show full text]
  • Mobile Applications
    ITU-T TechWatch Alert (July 2009) Mobile Applications By any measure Apple’s App Store has been a great success, passing the milestone of one billion downloaded applications (apps) in less than ten months, and reaching 1.5 billion downloads in one year.1 Indeed, the availability of a wide choice of apps can be critical to the commercial success of new smartphones. Even as more smartphones are sold, the creation of mobile applications to run on them is constrained by the fragmentation of the market between different platforms. Mobile apps are add-on software for handheld devices, such as smartphones and personal digital assistants (PDA). Among the most popular are games, social networking, maps, news, business, weather and travel information. All of these leverage at least one of the device’s technical features: communications interfaces (Wi-Fi, WiBro/mobile WiMAX, GSM/EDGE, W-CDMA/UMTS/HSPA and Bluetooth), audio and video processors, camera, sensors or GPS module. Handset manufacturers, mobile network operators and suppliers of mobile operating systems (see Table 1) are opening storefronts on-line in attempts to capitalize on growing consumer demand. High-end devices that are able to run mobile apps need an attractive and expanding range of these apps if they are to generate hardware sales and network revenues. Between 2008 and 2009, research firm Ovum expects the market for smartphones to grow by 23 per cent, against an overall decline in the total mobile phone market caused by the economic crisis.2 Smartphone shipments are forecast to reach more than 400 million by 2014, nearly all capable of running apps from at least one store.
    [Show full text]
  • Pervasive Virtual Information Exchange Platform a Federated Architecture from Sensory Swarms to Mobile Devices to the Cloud
    Pervasive Virtual Information Exchange Platform A Federated Architecture from Sensory Swarms to Mobile Devices to the Cloud Sateesh Addepalli, Advanced Architecture & Research Cisco Systems, Inc. San Jose, CA, USA [email protected] Bob DeAnna, Chief Technology Officer J.D. Stanley III, Public Sector Chief Recursion Software Technology Officer, Internet Business Frisco, TX USA Solutions Group [email protected] Cisco Systems, Inc. San Jose, CA, USA [email protected] Abstract—This paper will discuss the pervasive software Finally, various scenarios that will greatly benefit from and network architecture required to form the foundation of such a platform will be covered that span location-aware, Distributed Knowledge Networks (DKNs) and Intelligent pervasive collaboration, connected home, urban/regional Sensor Networks (ISNs) that span home and office, mobile wide platforms, emergency/first responder, and especially and embedded devices, sensors, autos, and the cloud. highly complex planet-wide intelligent sensor network and earth resources management systems. The paper will highlight how such foundations accelerate the development and adoption of immersive geo-spatial decision Keywords--pervasive software, pervasive fabric, spaces where mashed up isolated data sets from public, pervasive architecture, pervasive applications, private, and/or non-profit sources are combined with human pervasive middleware, mobile, wireless computing networking and social networking capabilities. The Emerging systems, ad-hoc networks combined effects resulting from these combinations will produce higher situational awareness, context aware option I. INTRODUCTION analysis, and interweaved collaborative environments harnessing the swarming nature of humans, machines, and Pervasive software has been discussed in sensors of distributed participatory networks. academia for some time now, but has yet to be realized.
    [Show full text]
  • Iso/Iec Jtc 1/Sc 17 N 4441
    ISO/IEC JTC 1/SC 17 N 4441 ISO/IEC JTC 1/SC 17 Cards and personal identification Secretariat: BSI (United Kingdom) Document type: Information from SC Secretariat Title: JTC1 Special Working Group (Planning): Draft Report on Mobile Applications V5 Status: Although this document does not list any specific SC17 standards, working groups may wish to consider any of their developements that might be considered in future versions of this docuement or indeed any that they are currently working on that they feel should be included. Any coments should be retruned to Chris Starr. Date of document: 2012-02-08 Expected action: COMM Email of secretary: [email protected] Committee URL: http://isotc.iso.org/livelink/livelink/open/jtc1sc17 ISO/IEC JTC 1/SWG 3 N 289 ISO/IEC JTC 1/SWG 3 Planning Secretariat: DIN Document type: Officer's Contribution Title: Draft Report on Mobile Applications V5 (clean version) Status: This document contains the fifth version of the draft report on the topic of mobile applications. It replaces the fourth version circulated as N0247 in SWG-P. Since this document was submitted too late to be formally discussed at the Tokyo meeting a decsion on its adoption will be taken at the March conference call of SWG-P. Date of document: 2012-02-08 Source: Editor Report on Mobile Applications, Mr Seungyun Lee Expected action: COMM Action due date: 2012-03-06 Email of secretary: [email protected] Committee URL: http://isotc.iso.org/livelink/livelink/open/jtc1swg3 - 1 - A standardization Initiative for Mobile Applications ISO/IEC JTC 1 SWG-Planning Background .........................................................................................................................................
    [Show full text]