W3C

- DRAFT -

Digital Signage Breakout

28 Oct 2015

See also: IRC log

Attendees

Present
Kiyoshi_Tanaka(NTT), Shigeru_Fujimura(NTT), Futomoi_Hatano(Newphoria), Katsuya_Hino(Toshiba), Oley_Mezhvynskyi(IQP), Tomohiro_Yamada(NTT), Roy_Kawada(KDDI), Atsushi_Nakadaira(NTT), Hiroki_Watanabe(NTT), Shinji_Fukatsu(Keio_Univ.), Hiroto_Inoshita(Keio_Univ.), Hiroyuki_Aizu(Toshiba), Stephan_Steglich(Fraunhofer_FOKUS), Ryoya_Kawai(AMEI), Yoshiharu_Dewa(Sony), SungHei_Kim(ETRI), Wook_Hyun(ETRI), Takashi_Toyoshima(Google), Yasuhiko_Miyazaki(NTT), Jay_Kishigami(AB), Kaz_Ashimura(W3C), Satoru_Takagi(KDDI), Motoharu_Watanabe(TT), Tadashi_Adachihara(Sony), Koichi_Maruyama(NTT), Kazuhiro_Hoya(Fuji-TV), Yoshiaki_Ohsumi(Panasonic), Riko_Yahyu(Observer), Kei_Takegami(NTT), Toshiro_Kubota(NTT), Yasuji_Eguchi(DSC), Yoshiyuki_Kato(Mitsubishi), Atsushi_Hori(Mitsubishi), YoungJae_Shin(SoftBank), Takeshi_Katsuno(Softbank), Sangwhan_Moon(Opera), Youngha_Kim(TTA), Hyejin_Lee(HTML5_Convergenced_Technology_Forum), Roy_Kawada(W3C/KDDI), Tetsuro_Tokunaga(NTT)
Regrets
Chair
Kiyoshi_Tanaka
Scribe
kaz, shigeya

Contents


<kaz> scribenick: kaz

<inserted> scribenick: shigeya

subscribenick: shigeya

(repeating previous messages)

Requirements for Embedded Browsers needed by web-based signage

Presentation by Kiyoshi Tanaka

<davei> resentation API

<scribe> Agenda: Presentation -> Discussions -> Wrap-up

Tanaka: What is web-based signage?
... BG Defineds web-based sinage player as web runtime and JavaScript lib.
... Embedded browsers such as TV sets used
... TV set with web-based browser is useful for signage
... Embedded browser embed at the factory
... embdeded browser's resrouce is limited.

<inserted> Tanaka: Web signage is not operated by audiences, but owners

(end repeat)

Tanaka: discussions on Power Management API
... For trobule shooting purpose, restarting/rebooting needed

Fujimura: power management API (controlling embedded borwser) needed, thus proposing this API.

Futomi: I'd like to propose more functionality, You propose shutdown only, but we need a wake-up functionality
... to achieve this .. machine, task scheduleing API is needed.

Tanaka: We think about discussing in web signage BG.

Futomi: Everyone want task scheduling like CRON (like the one in Unix system) - timer capability

Tanaka: where is this API discussed in what kind of working group? there are none yet. any working group discussing such kind of a API?
... no idea?
... I want to discuss this api in BG.

Futomi: Maybe mozilla?

Tanaka: not Standard, but not Implementation
... Next one is Web NTP Client API
... NTP is OS level function, but this is need from browser issue. Browser directly conect to NTP Server it is convininent to adjusiting time
... Timestamp object provides the same functions

Futomi: This is explain to difficult. let me show you a demo.
... I don't speak about NTP protocol, but simplified .. for signage

(demo on screen)

Futomi: This application run on Chrome. JavaSciript based signage player
... Typically, one signage includes several panels.

Ryoya: using Audio, think about . Important to synchronize between browsers.

NTP is important for us

<sangwhan> s/Tnaka/Tanaka/

Futomi: Multiple panels run on a signage, and synchornization betweens are needed.
... if browser has a time synchronization mechanism synchornization machanism, it is useful.

Fujimura: multi terminal or single?

<sangwhan> s/synchronization mechanism//

Takashi: NYC team of google run signage at Times Square. Each chromium runs each screen.
... they have implemented synchronization mechanism between them
... TCP/UDP Socket API... If they publish API, then, you can use NTP.

Sangwhan: Web NTP. NTP itself is UDP. This might not work on TCP.
... Require to define the userland level protocol, which might use TCP, that might not work.

Roy: one commnet, Web.. TV IG, they will present ... tomorrow,

sangwhan: Signage group will meet tomorrow,

Tanaka: I want to know the status of specification
... any comments?
... next one: system context.

Takagi: Originally mozilla people.... I have discussed with Mozilla's Asai-san

Tanaka: System Events

Sangwhan: Is that possible, with some security issues like access system properties?
... when WD is released is unknown.

Miyazaki: Service works are lmited to some domains. But in signage, there is a remote owner, that's very specifc model to signange. we need some special workers
... I'm not sure because this issue is very related to a specific model.

Futomi: we possibliy design a new API, but I'm not sure. we don't need ... to service worker for now..

sangwhan: not need to be as a service worker, outside of rendering process.

Takashi: could be part of service worker. In that case, you may be better to inject API to specific access.

Futomi: Are you talking about chrome apps
... we need to discuss in BG on usecase

Tanaka: next one: Multiple resource for videos

<kaz> Jay_Kishigami(AB), Kaz_Ashimura(W3C), Satoru_Takagi(KDDI), Motoharu_Watanabe(TT), Tadashi_Adachihara(Sony), Koichi_Maruyama(NTT), Kazuhiro_Hoya(Fuji-TV), Yoshiaki_Ohsumi(Panasonic), Riko_Yahyu(Observer), Kei_Takegami(NTT), Toshiro_Kubota(NTT), Yasuji_Eguchi(DSC), Yoshiyuki_Kato(Mitsubishi), Atsushi_Hori(Mitsubishi), YoungJae_Shin(SoftBank), Takeshi_Katsuno(Softbank), Sangwhan_Moon(Opera), Youngha_Kim(TTA), Hyejin_Lee(HTML5_Convergenced_Technology_Forum)

<kaz> m)

Futomi: There are several signage product in this hall, we develop
... Why do you think this fucntionality need an API?

Tanka: Signage needs ... attractive, ...

Tanaka: I think this kind of work... covered by some WGs?

sangwhan: DASH

Tanaka: this kind of APIs can be discussed at DASH, if we have specifics, we can ask... Anyway, we'll discuss in BG meeting
... Next one is multicast video playback
... You can see a video streaming application on signages in the hallway
... at 10Mbps, shared with our local network.
... MMT technilogy might help.

sangwhan: ATSC3

Futomi: what is MMT?

Tanaka: time-coded, synchronization among multiple streams
... broadcasting company (plan to?) adapts these specifications
... These kind of issues are common among media implementations.

Fujimura: on multicast, IP multicast or applicaiton level multicast.. which is better??

Tanaka: Multicast implemented on Sony Bravia

sagwhan: with <object> tag?

sangwhan: video tag require source, requires magic URL, mutlicast content does not have URLs. might not be favored

Tanaka: Next one: access cotrol of external storage

<inserted> adachihara: would skip the detail today

sangwhan: two groups try to standardize and failed.

Roy: I think, one of the issue is security issue. We can limit.

sangwhan: This way donesn't fly, since we're at W3C.

Roy: hardware security working group proposed some kind of hardware token to be used.

sangwhan: these are crypto processors?

<futomi> http://www.w3.org/2015/hasec/2015-hasec-charter.html

Takashi: R/O or R/W?

Futomi: Signaage require R/W

adachihara: for caching (or implementing download functionalities)

Tanaka: last one: Double buffering API

sangwhan: do you need render surfaces? confusing with tab switch

Miyazaki: Audience do not want to see black screen for 3secs.

Futomi: Black screen shown due to the processor resource or other reasons.

Takashi: Network latency is one of the issue? or need a cross-fade?
... If network latency is the issue, service worker helps.

sangwhan: This have to be privileged API (to prevent AD comapnies to create pop-ups)

Jay: please use speaker queue.
... BG for gathering of requirements. There are lot of stakeholders.
... We have to standarize quickly
... My proposal is this kind of kick-off of web-based signage pre-meeting. And also to generate a charter, quickly accelerate as WG or standardazation, should have relationship with existing WGs
... such kind of movement required for us.
... This is a just breakout session, but we need WG.

Tanaka: We will discuss in BG meeting. also we will talk about this in parallel.
... We have presented several APIs.

Futomi: (some of the API need to chage name)

Jay: You can expereience digital-signage prototypes in hallway. Also visit the demo booth.

<kaz> [ adjourend ]

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.140 (CVS log)
$Date: 2015/11/09 07:21:53 $