This wiki has been archived and is now read-only.

TPAC2012 KDDI Input

From Web-based Signage Business Group
Jump to: navigation, search

Mapping functions for websignage

Map and Signage

  • It might become BG's common recognition that the map is one of the important and indispensable component for signage.
  • Because the map has such various use cases, "The map" itself may be considered to be one of the general-purpose use casess of websignage.
  • KDDI proposes that BG agrees that Mapping Functions for Signage is one of the important themes (use cases or requirements), and establish it as one of BG's objectives.

Map and Disaster Relief and Signage

  • Needless to explain it in detail, map will be the most important information phenotype helping disaster relief.
    • ITU's action
      • As the grounds above, ITU announced that they will encourage establishment of the mechanism for the disaster relief based on map. And, as mechanism for the map, the SVG-based web technology is expected.
      • And they are carrying it out in form of lianson to W3C.
        • Input Document
          >ITU-T Focus Group on Disaster Relief Systems, Network Resilience and Recovery (FG-DR&NRR) would like to inform you that we have started work on “Requirements on mobile systems for Disaster Relief by guidance”.
        • Attachment 
          DisasterReliefMap.JPG Explanation slide of use cases
        • Note: To view documents, needs free guest account:Instructions
  • Disaster Relief and Signage
    • On the other hand, according to the summary of websignage workshop, disaster is one of the important use cases for this BG.
      >Security of content on sign (who is it from, is it "disaster-proof", etc.)
      >Participants identified these use cases: Disaster information/Notice board
  • Importance of the map for disaster relief on websignage
    • This will be clear by considering above two matters.
  • KDDI proposes that BG agrees that Mapping Functions for Signage is one of the important themes as aspect for disaster relief use case, and establish it as one of BG's objective.

Progress report of standardization at W3C

  • KDDI is working on standardization about Web Mapping at W3C which was expressed at former Workshop. The standardization activity is in progress mainly in SVGWG to make WWW browser the native mapping platform.
  • Below is its current progress report.
    • In March 2012, the new charter of SVGWG was established. In this charter, promotion of the standardization of the mapping function was specified. Furthermore, possibility to standardize some of these as basic functions of SVG2 was suggested in that charter. This shows the possibility that mapping functions are implemented on every browsers on HTML5 generation.
      • > In order to meet the specific needs of content creators using SVG for mapping applications, the SVG WG intends to form an SVG Mapping Task Force
        > In addition, some of this functionality will benefit non-mapping applications such as high resolution photographic or medical imagery, so could be placed in the main SVG2 specification.
    • In the last F2F held in September 2012, SVGWG agreed to standardize a part of the mapping functions as a part of basic functions of SVG2 by generalizing it. Though this function is not yet all of mapping functions, it is key and has high implementation difficulty. Therefore, this may be notable progress for the aim mentioned above.

Summary of agreed functions

  • Dynamic loading of cascading linked documents
  1. Level Of Detail : Depending on the resolution of the canvas, UA loads suitable graphics dynamically. ( explanation )
  2. Tiling : Depending on clipping area with the zooming, UA loads suitable graphic tiles dynamically. ( explanation-1 explanation-2 )
  3. Layering : Depending on the instructions of the publisher and user, UA loads a suitable layers and composes them on a canvas. ( explanation )
  • This function provides the characteristics such as ad hoc mash up and off-line operation that is necessary for mapping system at the time of disaster.
  • Furthermore, for signage with a variety of screen size and shapes, functions of Level Of Detail and Tiling may be particularly effective.

KDDI's Proposal

  • In the W3C, only SVGWG works on mapping now. If we need native and disaster tolerant mapping functions for HTML, this activity will be an appropriate candidate.
  • KDDI proposes that BG agrees that examination of Mapping Functions for Signage by SVG is one of the important themes, and establish it as one of BG's objective.
    • Examples of the examination theme
      • Examination of a use case peculiar to signage
      • Output of the implementations
      • Output of the issues based on above implementation
      • Examination of the theme that should be considered in other WG
        • Geolocation
        • Performance

Relation to System Applications WG

Summary of SystemAppWG

  • Sys App WG Charter
    • Technologies related to developing Web application that integrate closely with a host operating system
    • Target Devidces: Desktop computers, laptop computers, smart phones, tablets, TVs, cameras, and other connected devices.

APIs planned to be created in SystemAppWG

  • Phase1
    • Execution Model
    • Security Model (How the execution or security model differs from the traditional browser-based execution model.)
    • Alarm API (manage the alarm daemon)
    • Contacts API (device's address books)
    • Messaging API (e.g. SMS, MMS, Email, IM)
    • Telephony API
    • Raw Sockets API (manipulate low-level connections (e.g. TCP, UDP))
  • Phase2
    • Bluetooth API
    • Browser API
    • Calendar API
    • Device Capabilities API
    • Idle API (notified when the user is idle)
    • Media Storage API
    • Network Interface API
    • Secure Elements API (enabling the discovery, introspection, and interaction with hardware tokens)
    • System Settings API

Relationship between SysApp and Signage

  • Definition of websignage's device properties
    As SysAppWG is going to cover all the aspects on connected devices, Digital Signage should be in line with the WG
  • Interconnection of websignage and other devices
    We can ask for the necessary APIs to connect the web-based signage to the other devices (e.g. SmartPhone) -> What use cases should be considered for this?
    • Related APIs:
      • Raw Sockets API: An API to manipulate low-level connections (e.g. TCP, UDP), including the ability to listen for incoming connections.
      • (Note: Content distribution model, e.g. how to push a content from the server to the signage UA, must be clarified. If a content can be transmitted and controlled remotely through HTTP(S) and/or WebSocket?, Raw Socket API might be unnecessary.)
      • (Note: If functionality of remote debugging can take a role of content push and control, Browser Testing and Tools WG could be related, too.)
      • Secure Elements API (e.g. NFC)
  • Security model peculiar to websignage
    Trust is one of the most important aspects for Digital Signage. This may fall into the scope of SysApp WG
  • The other examples (the other use cases?)

KDDI’s interest in SysAppWG

  • KDDI has high interests in its work and decided to contribute to the SysApp? WG because of aiming at the following subjects:
    • Dealing with a variety of devices in integrated manner
    • Provision of service environment at the equivalent level of the Native applications beyond existing Web services
    • Dealing with operator's services such as mobile telephony and messaging
  • KDDI will contribute to the followings:
    • Development of APIs for efficient Network utilization
    • Construction of Security model