Web-based Signage Business Group meeting at TPAC2012 -- 01 Nov 2012

<Shinji> Adenda:http://www.w3.org/community/websignage/wiki/Group_meeting_at_TPAC_2012

<Shinji> Scribe: Naomi Yoshizawa and Shinji Ishii

<Shinji> ack

<naomi> toru: let's start. thank you for coming

<naomi> ... will discuss about some topics

<naomi> ... let's introduce ourselves first

<naomi> ... there are two proposals from members - NTT and KDDI

<naomi> ... s/toru/futomi/

<naomi> ... would like to observer's opinion

<naomi> ... and talk about use cases and requirements

<naomi> ... I am Futomi Hatano, Newpholia corporation, web developer

<naomi> ... thank you for coming

<naomi> ryosuke: I am Ryosuke Aoki from NTT

<naomi> Toshi: I am Toshiyuki Okamoto of KDDI

<naomi> Chaals: work for Yandex. I am here for 20 minutes. co-chair of Web Apps

<naomi> ... one specification might work on WebApps

<naomi> ... want to talk about ideas / specifications

<naomi> ... important to WebApps group to listen, what we need

<naomi> ... if you don't, you will be completely ignored

<naomi> AA: hyun wook from ETRI. working on TV systems

<naomi> Ryoichi: Ryoichi Kawada from KDDI

<naomi> ... research and develop

<naomi> aizu: Hiroyuki Aizu of Toshiba

<naomi> ... manufacture of PC and devices

<naomi> ... try to integrate Brower to TV

<naomi> Katsuhiko: Katsuhiko Kawazoe of NTT

<naomi> ... responsive of creating new business

<naomi> ... co-chair of digital signage Japan

<naomi> shinichi: Shinichi Nakao of Newpholia

<naomi> ... working with futomi

<naomi> Hiroshi: Hiroshi Yoshida of Hakuhodo which is 2nd largest PR company in Japan

<naomi> Shinji: Shinji Ishii of NTT and W3C

<naomi> ... working on digital signage

<naomi> SeungHei Kim: ... from ETRI

<naomi> BB: kim from KAIST

<naomi> ... interactive signage

<naomi> ... try to technology standard

<naomi> CC: ..Kim from KAIST

<naomi> ... researching signage

<naomi> ... collecting @@ information

<naomi> DD: Soobin Lee from KAIST

<naomi> ... first TPAC and hope to contribute a lot

<naomi> EE: Kang from Korea

<naomi> FF: Kiyoshi Tanaka of NTT, researcher of IPTV

<naomi> Manyoung: Manyoung of Future technology

<naomi> Yamada:

<naomi> Mitsuru: Mitsuru Yamada of KDDI

<naomi> Koichi: Koichi Takagi of KDDI

<naomi> ... relationship between system apps and signage

<naomi> toru: Toru Kobayashi of NTT

<naomi> ... group leader of device oriented group

<naomi> ...expect to have many comments

<naomi> alan: Alan Bird of W3C

<naomi> futomi: proposal of BG members

<naomi> chaals: co-chair of WebApps

<naomi> ... sent some comments to you

<naomi> ... highlightened is push API

<naomi> ... meant to allowed to application to sleep

<naomi> ... messages can wait to the application what to do

<naomi> ... working draft of WebApps

<naomi> ... by AT&T, Telephonica ,etc

<naomi> ... Mozilla looks implement something like this

<naomi> ... /me thanks kiyoshi

<naomi> chaals: disaster senario

<naomi> ... WebApps needs usecases of demands and implementations

<naomi> ... it's not going fast

<naomi> ... when you want to some WGs especially for implementing

<naomi> ... speak up

<naomi> ... they don't mind to listen to your opinions

<naomi> ... and please be nice

<naomi> toru: what is the difference between Web Socket and PushAPI

<naomi> Chaals: WebSocket is OO

<naomi> ... push API is transport independent

<naomi> ... application will register some services

<naomi> toru: why operators interested in it

<naomi> chaals: s/Opera/Opera/

<naomi> chaals: ^^^^^

<naomi> ... feel free to send questions to me anytime

<naomi> futomi: presentation of NTT

<naomi> aoki: Multi-screen collaboration and disaster situation

<naomi> ... [ reviewing slide ]

<naomi> ... carry mobile devices such as tablet

<naomi> ... disasters occured frequently

<naomi> ... Japan was struck by big earthquake and tsunami

<naomi> ... after the disaster people want to get informtaion

<naomi> ... safety and get to know friends and family

<naomi> ... also wanted to know evacuation center

<naomi> ... but it was difficult to get those information

<naomi> ... our research goal is to share information after disaster quickly as possible

<naomi> ... internet access was difficult and impossible

<naomi> ... infrastructure was damaged or network load was overloaded

<naomi> ... wireless screen devices didn't work

<naomi> ... each devices has different carriers and operation systems

<naomi> ... each of them has different compliance

<naomi> ... each area network has connectivity using HTML5 browser

<naomi> ... multi-screen collaboration has 3 connections

<naomi> ...1 @@

<naomi> ...2 how to use information

<naomi> @@@@

<naomi> ... 3 how to investigation to clarify the problem after disaster

<naomi> ... extracted problems from surveys

<naomi> ... [ revieiwng slides ]

<naomi> ... would like to discuss 3 problems

<naomi> ... 1. system can't catch up with current disaster situation

<naomi> ... situations changes rapidly

<naomi> ... internet access will be affected by heavy traffic

<naomi> ... time of internet access recovery is depend on the places

<naomi> ... evacuation center or train station get to communiti3es

<naomi> ... devices of local network change frequently

<naomi> ... to be effected by multi-screen @@

<naomi> ... want to propose information sharing using core devices

<naomi> ... at evacuation center using wifi

<naomi> ... core device collects local information like foods supply

<naomi> ... it distributes information of volunteers or other evacuation center

<Shinji> NTT' Ryosuke Aoki propose: Information sharing using core devices

<naomi> ... they upload corrected information

<naomi> ... information sharing realize network available

<naomi> ...3. there are too AAAAAAA

<naomi> ... [ reviewing photos ]

<naomi> ... [ puts hundreds of notes ]

<naomi> ... difficult to check and read all of them

<naomi> ... to solve this problem is to layout reconsiliation BBBB

<naomi> ... core device such as Digital signag

<naomi> ... core device download information requested from display on their mobile

<Shinji> NTT' Ryosuke Aoki propose #2 : Layout reconstruction of trimmed information

<naomi> ... each people get information targetted one

<naomi> ... finally the layout construct reviewing information

<naomi> ... they can store information in their mobile

<naomi> ... 10. senior / impaired people can't understand the announcement

<naomi> ... not everybody could understand all informtaion

<naomi> ... need to be easy to understand

<naomi> ... display information according to user profile on their mobile

<Shinji> NTT' Ryosuke Aoki propose #3 : displaying information according to user profile

<naomi> ... for seniors to recommend to use big mobiles

<naomi> ... need to discuss those 3 issues

<naomi> ... how can mark up distinguish core devices from non-core devices

<naomi> ... how can CCCCC

<naomi> ... how can DDDDD

<naomi> futomi: let's talk about this standarlization step by step

<naomi> ... 1. information shring using core devices

<naomi> ... there is a leader at each evacuation center

<naomi> ... each core devices collect and output information

<naomi> ... if hte core device is full battery, core devices turns into automatically FFF

<naomi> ... adopts sharing information

<Shinji> explains core device non-core devices

<naomi> futomi: personnel devices could be a device?

<naomi> ... I don't want my smartphone gets core device

<naomi> ... if mine become to it, traffic will concentrate to my phone

<naomi> ... there there are many people around my mobile it will be hang up

<naomi> ryosuke

<Shinji> Chair: smartphone is core device?

<naomi> ryosuke: if it's connected to power, your mobile could be core device

<naomi> ... it's possible for your phone to be a core device short time

<naomi> ... core device might not be able to run always

<naomi> ... just only collect information

<naomi> ... and updates

<naomi> futomi: core device should be digital signage terminal

<naomi> ... it has a big battery

<naomi> Shin-Gak Kang: PPP

<naomi> ryosuke: Tokyo station has a lot of digital signage which could be an evacuation center

<naomi> ... if each mobile could be core device GGGGG

<naomi> hyun: digital terminal could communicate to evacuation information

<naomi> ... is my smartphone send information?

<naomi> ryosuke: you can use it through router

<naomi> hyun: localized network?

<naomi> ryosuke: core devices connected to wifi router which directly use @@

<naomi> ... should be easy

<naomi> hyun: it's quite useful use case for safety confirmation in the disaster situation, but those service can be achieved by general web server within digital signage terminal

<naomi> futomi: wondering which part is good for web technology

<naomi> ... some systems apps not relevant to web

<naomi> ... some functions is web technology

<naomi> ryosuke: core device through and have server function

<naomi> ... connecting internet

<naomi> ... local area network is core device

<naomi> ... same display and same functions

<naomi> ... so user can display information

<naomi> futomi: HTML is already working

<naomi> ... what kind of web technology will be used

<naomi> ... what kind of api should be required

<naomi> ryosuke: apis of develper using this function [pointing slides ]

<naomi> futomi: are we talking about OOO

<naomi> futomi: smartphone upload information

<naomi> ryosuke: core device finds each devices in a local area network

<Shinji> Slide: Information sharing using core device

<naomi> futomi: key of this proposal IIII

<naomi> ryosuke: we want to create this API as core device

<naomi> futomi: discovering devices around me i.g. NFC or bluetooth or wifi-direct

<naomi> ryosuke: Oofunato or Miyagi had big damages

<naomi> ... they made wifi network

<naomi> ... but this system connection is wireless

<naomi> Gisung: want to know what kind of information the core device correct

<naomi> ryosuke: safety of family or friends information

<naomi> ... people separated from family and stayed each evacuation center having no internet connection nor telephone

<naomi> ... calling children was not possible

<naomi> ... if core device correct those information, the volunteer moves and distribute it to each devices

<naomi> Gisung: who makes html document

<naomi> ryosuke: volunteers and I am now forming system

<naomi> Katsuhiko: how to share information at the same time

<naomi> ... peer to peer information

<naomi> ... information shouldn't be changable

<naomi> ... but could be shareble

<naomi> ryosuke: reference p to p system

<naomi> ... we use a flow by human

<naomi> ... people detect core device

<naomi> ... people comes to evacuation center detect core device

<naomi> ... so they can collect information

<naomi> ryosuke: miyagi / oofunato had many evacuation center

<naomi> ... we could use human power

<Shinji> slide #14 : question from ETRI Kang, ETRI Hyun, KAIST Gisung, NTT Katsuhiko,

<naomi> ryosuke: 2 proposal Multi-screen collaboration of digital PPPP

<naomi> ... How can mark up reconstruct a layout after data trimming

<naomi> futomi: is it OCR?

<naomi> ryosuke: yes

<naomi> ... Optical Caractor Reader

<naomi> ... [ showing slides - hundreds of notes ]

<naomi> ... if safety information could get into as digital signage

<naomi> ... an user could access to those information

<naomi> futomi: receiving information to a mobile

<naomi> ryosuke: but display size is different

<Shinji> ..silde #18 Multi-screen collaboration of digital signage and mobile deives

<naomi> futomi: information is digital data

<naomi> ... this requirements discussed by our BG

<naomi> ... usecase and requirements documents

<naomi> ... it requires discovering terminal and communicating terminal

<naomi> ... those are listed in our document

<naomi> ... let's talk it later

<naomi> aizu: clip @@?

<naomi> ryosuke: user could pick up targeted information

<naomi> ... people could select and collect information easily

<naomi> ... cut and paste are easy

<naomi> ... could do trimming information

<naomi> aizu: looks like evernote function

<JonathanJ1> FYI - I've proposed a new element for collaboration with mobile and fixed device on HTML WG - http://lists.w3.org/Archives/Public/public-html/2012Nov/0002.html

<naomi> ryosuke: our research focus is how to clip and layout reconstruction

<naomi> futomi: challenging

<naomi> Soobin: issue suggested is selecting partial area of web page?

<naomi> ... after collecting multiple ```

<naomi> ... are you talking about everything?

<naomi> futomi: big data first and we pick up information

<naomi> ... one person needs to small portion of information

<naomi> ... it should be transfered to quickly

<naomi> Kang: portion?

<naomi> ... content could be UPnP and DLNA is pre-registered.

<Shinji> ..slide #19 Layout reconstruction of trimmed information

<naomi> ... clip something and pickup information

<naomi> toru: important is to how to @@

<naomi> toru: @@@

<naomi> katsuhiko: this function, big map, I want to pick up information limited one

<naomi> a lady: in this situation, implementation, who is where

<naomi> ... you may need to use keyword

<naomi> toru: user's requirements is important

<naomi> ... Mr. A requires a bathroon

<naomi> ... automatically the device could find

<naomi> FF: the case of disaster

<naomi> ... human hand write description

<naomi> ... google person finder

<naomi> ... what kind of @@ are you using

<naomi> ryosuke: Google personal finder requires internet accessibility available

<naomi> ... many volunteers wrote each information (typed)

<naomi> ... this sitution is after disaster

<naomi> ... thought internet access is available

<naomi> FF: local area can be installed and shared by person

<naomi> ryosuke: hoping personal finder is volunteer typing

<naomi> ... but want to do it automatically

<naomi> ... tv reporters collected information and typed

<naomi> ... were hard

<Shinji> slide #19 : question from KAIST Soobin, ETRI Kang, ETRI Sung, ETRI Wook,, comment from NTT Katsuhiko

<naomi> ryosuke: 10. Displaying information according to user profile

<naomi> ... display design

<naomi> ... change mobile speed

<naomi> ... can see information visually

<Shinji> ..slide #23: Displaying information acceding to user profile

<naomi> ... also senior people could get it but not small letters

<naomi> futomi: is this a personal devices?

<naomi> ryosuke: each people could download an announcement

<naomi> ... if html documents only normal correspondence

<naomi> ... some people couldn't get those

<naomi> sangwhan1: the operating system should be taking care of this, not the content dispatcher

<naomi> ... the content should be neutral in nature and it should be up to the device to provide it in a accessible manner

<naomi> ... the device should be pre-configured

<naomi> ... if you unable to use the device, what do you do

<naomi> ... the accessibility groups work on the specs to make this "just work" for compliant devices

<Shinji> Comment/Question from Sangwhan (Opera Software ASA).

<naomi> ... if person adjust device ****

<naomi> FF: persona devices LLLLLthis group is not to develop a computer vision library

<naomi> ... if it's personal device, it might not be possible

<naomi> ryosuke: supply or lease a device to senior people

<naomi> FF: OOO

<naomi> toru: could circulate each device?

<naomi> GG: spoken by TTN

<naomi> ... low sentence, information provider could convey easily

<naomi> toru: meaning recognition?

<naomi> GG: yes

<naomi> futomi: thanks, ryosuke

<Shinji> slide #23: question/comment from ETRI/Kang, Opera Software/Sangwhan, NTT/Toru, KAIST/Gisung

<Shinji> next session will start 15:30

<Shinji> test

<naomi> toshi: toshi of KDDI

<Shinji> Next KDDI presentation

<kotakagi> Please see item 1 of http://www.w3.org/community/websignage/wiki/TPAC2012_KDDI_Input

<naomi> ... Mapping functions for signage

<naomi> ... mapping functions for websignage

<naomi> ... believe it7s important topic

<naomi> ... also a big one for SVG group

<naomi> ...1. Map and signage

<naomi> ... map is one of the important and indispensable component for signage

<naomi> ... [ showing slide ]

<naomi> ... maps can be used to help travellers

<naomi> ... large trip map projects is goingto move things ahead

<Shinji> slide: Map Signage

<naomi> ... according to the use cases and requirements R3. Communication with a touched devicep>

<naomi> ... 2. Map and Disaster relief and signage

<Shinji> slide: Mapping Disaster Relief and Signage

<naomi> ... map will be the most important information phenotype helping disaster relief

<kotakagi> s/Communication @@/Communication with a touched device/

<naomi> ... ITU's actions are - announcement and Liaison to W3C

<naomi> ... such as evacuation shelter map and homecoming support map

<naomi> ... disaster is one of the important use cases for this BG

<naomi> ... progress report of standardization at W3C

<naomi> ... March 2012, the new charter of SVGWG

<naomi> ... prmotion of the standardization of the mapping function

<naomi> ... possibility to standardize some of these as basic functions of SVG2

<naomi> ... in the last f2f September 2012 of SVGWG

<naomi> ... agreed to standardize a part of the mapping functions as a part of basic functions of SVG2 by generalizing it

<naomi> ... details our technical discussion is outscope now

<naomi> ... use cases

<naomi> ... off-line mapping system at the time of disaster

<naomi> ... for signage with a variety of screen size and shapes

<naomi> ... only clipping on map

<naomi> ... not just only mapping but can be use images

<naomi> ... and can download

<naomi> ... in the W3C only SVGWG works on mapping now

<naomi> ... appear SVG technology on signage

<naomi> ... want to talk about mapping function

<naomi> ... Map an Signage

<naomi> futomi: ideas? opinions?

<naomi> ... question. what is the benefit of using SVG map

<naomi> ... people usess Google map

<naomi> ... but it does't use SVG

<naomi> ... why google doesn't use SVG?

<naomi> toshi: 1st is off-line

<naomi> ... google map data is big size

<naomi> ... SVG gets information what we need

<naomi> ... exactly

<naomi> futomi: what's the difference?

<naomi> ... a map using SVG was heavy

<naomi> ... google one was faster and light

<naomi> ... not familyliar with map technology but want to know clear benerfit

<naomi> ryoichi: SVG map merit is close to platform

<naomi> ... and vendor independent

<naomi> ... SVG is a platform technology

<naomi> futomi: is there other mapping in real

<naomi> ryoichi: one of KDDI has a service called map for use in a case of disaster

<naomi> ... navigation of disaster time

<naomi> ... uses SVG technolgy

<naomi> ... [ryoichi looks for the demonstration ]

<naomi> toru: what is off-line mapping

<naomi> ... do you need a server? or only client?

<naomi> toshi: don't need a server

<naomi> ... show a map only references

<naomi> ... sigange terminal device mapping information

<naomi> toru: in advance, signage terminal could download data

<naomi> toshi: including mapping data

<naomi> ryoichi: we don't have to rely on networks

<naomi> futomi: data could be update?

<naomi> ryoichi: you have to be online though

<Shinji> ..And we can chose combination with server or without server

<naomi> ... [ showing demo ]

<Shinji> Additional presentation from Kawata-san

<naomi> Wook: mapping and map should be different meanings

<naomi> ... which definition you are talking?

<naomi> toru: mapping is integration of information

<naomi> ... map is a navigation or rout information

<naomi> toshi: we talk about both of it

<naomi> ryoichi: [ showing demo ]

<Shinji> Additional presentation is "SAIGAI Navi"

<naomi> ... this system works without 3G

<naomi> futomi: seems like a feature phone

<naomi> ryoichi: kind of old tech

<naomi> futomi: do you use an ordinary browser or proprietary application?

<naomi> ryoichi: the later one

<naomi> ... at the disaster you need GPS

<naomi> futomi: smartphone service?

<Shinji> This service is using map and mapping in feature phone

<naomi> ryoichi: not yet but in the future

<Shinji> Next topic

<naomi> futomi: proposal from observers

<naomi> ... anything?

<naomi> ... then review our draft

<naomi> ... long long long document

<naomi> ... URL

<naomi> ...

<naomi> futomi: new proposal are welcome

<Shinji> http://www.w3.org/community/websignage/wiki/Web-based_Signage_Use_cases_and_Requirements

<naomi> ... R.1 Making contents using a declarative approach

<naomi> ... had a workshop in Makuhari last June

<naomi> ... some member proposed declarative approaches

<naomi> ... we can use HTML5 or SMILE

<naomi> ... how can I use HTML or SMIL

<naomi> ... [ explaining requirements ]

<naomi> ... [ read the page ]

<naomi> ... are you interested in HTML appraoch or SMIL?

<Shinji> Toru: just clralfication question in this session process

<naomi> Gisung: want to discuss about timing

<naomi> ... fully supported by advertisement on time

<naomi> ... signage input generates information and you can schedule one

<naomi> ... event based one is important

<naomi> ... want to talk about it

<naomi> futomi: scheduled one

<naomi> ... what is the difference between scheduled one or R9 or R14

<naomi> Jaejeung: advertiser pay a thousand @@

<naomi> ... looks into signage

<naomi> ... distract signage pays 1000 dollars

<naomi> ... user interactive

<naomi> ... could be disturbing for advertisers

<naomi> ... could be have clear senario

<naomi> ... compensate issue

<naomi> ... scheduled content

<naomi> ... another content by user interactively

<naomi> ... is the current web-based signage or web application

<naomi> ... do we allow ??

<naomi> ... free advertisement

<naomi> ... during the time

<naomi> ... annotating by markup

<naomi> ... structure which supports two type of contents

<naomi> ... could be a senario or requirements

<naomi> ... how to support advertisement

<naomi> futomi: do you assume a senario has a interactive content or static one

<naomi> AA: scheduled one starts 1 o'clock

<naomi> ... a use turn on movie

<naomi> ... 5 minutes left, another advertisement starts

<naomi> ... we should provide something tool annotation of web contents designer

<naomi> ryoichi: do you have a business examples?

<naomi> Wook: we are research institute

<naomi> ... we have met this issue people interuppted scheduling

<naomi> ryoichi: what do you mean user adoptive

<naomi> Gisung: adoptive

<naomi> ... base of signage is plain content of schedule

<naomi> ... we are looking into @@@

<naomi> scribenick: Shinji

Futomi is confireingi time scheduled signage

Jaejeung explain an example of time scheduled signage

from Gisung's mailLet me give an example.

Advertisement A is scheduled to be displayed on a digital signage at 1 PM. It is paid for 1 hour display (from 1 PM to 2 PM)

Advertisement B is also scheduled to be displayed just from 2 PM to 3 PM.

A user comes to the signage at 1:55 PM. He tries to play an movie clip pertaining to the advertisement A. The duration of the movie clip is 10 min.

Hiroshi: this use case is business format

Gisung: already

<naomi> scribenick: naomi

sangwhan: @@@
... don't know why PPP
... R14
... should be solved programatically by IIII
... submitted by YouTube
... draft stage but could address the use cases

<sangwhan> http://dvcs.w3.org/hg/html-media/raw-file/ae41dd28af33/media-source/media-source.html

sangwhan: [ explaining the draft ]

<Shinji> Sangwhan: explains "Media Source Extensions"

sangwhan: you might want to talk to Netflix guys or ask Mike Smith

toru: viewing videos simultaneousely?

Sangwhan: que
... because costs too much
... want to take @@@
... the draft is not final one
... you can test which is available from Google
... Opera has implementation but it's not public

<Shinji> .. discussion about dynamic content insertion

futomi: media source extensions could be a solution of R14
... especially for video

<Shinji> Katsuhiko and Toru: In this session, we need discussion business use case, and then discussion gap analysis.

<Shinji> Futomo: R14 is related "Media Source Extensions"

futomi: next requirements - R2
... this requirements has been solved
... for video contents PPP
... the format of caption is necessary
... web ttt is applicable
... images and style text
... no common capturing
... we have a solution of video but not for static content
... should we define the format?
... or HTML?

sangwhan: what is the advantage of defining static content?

futomi: we don't need these format but it might be better to use HTML but if you want to use the other way, please let me know

sangwhan: I don't think we need it and WG won't take it

futomi: ok then move to next topic
... communication touch devices
... when use touches signage terminal on he/her terminal
... smartphone get information
... gap analysis
... exchange text data i.e., URL
... we expect to transition to PPP WG

R3: communication of touch devices
... looks like touch smartphone screen
... you can commit OOO
... personal devices

Sung: touch device is touch screen
... personal devices

futomi: [ modifying wiki ]
... R4
... bit difficult requirement
... in Japan many smartphone has infrared communication function
... device to device communication inflate to common communicate with devices
... if there are signage terminals, they has communication function.
... all terminal scan personal devices
... how do we communicate these terminals
... how can we use this situation
... wifi or bluetooth

<sangwhan1> s/this PPP/these terminals/

futomi: need to communicate only then this should not be a issue
... only solution is infrared communication
... if I want to communicate with next one, I just point to the terminal
... easy for human

toshi: what is the difference between infra-red and NFC

sangwhan1: UUUU
... globaly available and standard in Japan from 10 years ago
... not sure for the size of out of Japanese market

<Shinji> s/O and P/infraed and NFC/

a lady: we can use NFC

scribe: you could make the requirement

sangwhan1: agreed. generalized or combing with NFC and R3
... no API covered

futomi: smartphone with infrared function in Japan
... do you still need the requirements?

BB: let's merge R3 and 4

futomi: then I combine R3 and 4

<sangwhan1> ACTION: Futomi to merge R3 and R4 [recorded in http://www.w3.org/2012/11/01-signage-minutes.html#action01]

<Shinji> Editors note: R3 and R4 will combine one requirement.

<Shinji> Thanks Sangwhan

futomi: R5. Discovered by personal devices
... when a signage terminal communicates with a personal device, a personal devices need to discover a specified terminal at first
... /me sangwhan1 ++

<sangwhan1> s/... \/me sangwhan1 ++//

futomi: Web Intents has hopes
... one more way is network @
... [ playing a video of Daniel, Opera ]

<sangwhan1> http://dev.opera.com/articles/view/network-service-discovery-api-support-in-opera/

futomi: not sure this API is available for the requirements
... gotten advice from the DAP WG

<sangwhan1> s/+++/the DAP WG/

Sangwhan1: backing of UPnP, it's extensible
... we hope other browser could take **
... at the moment UPnP is not free
... we are paying for it
... use cases paying regardless KKK
... it's a very controversial topic - we haven't decided, too

futomi: I have programmed UPnP using JS before which was compliated
... but I will remain this phrase

toru: UPnP or DLNA
... ???

Sangwhan1: complex problem to be solved
... engaged communication

s/communicatiohn/communication/

scribe: possibility using QR code or manual url inputbr /> ... requires user interaction

HH: what is the minimun requirements of layer 3 and 2
... >>>
... if we apply this to signage

<sangwhan1> s/}}}}/manual url input/

HH: if broadcaster feature is enough for bluetooth or wifi which requires OO
... what is the requirements for signage
... it's not just a home environment?
... or broadcaster environment

futomi: it will be limited situation
... upper layer
... R6
... Capturing an end-user

<Shinji> futomi: In this requirement is only focus on layer 2. not include layer 3.

futomi: vendor machine implement a camera
... will be valuable
... putting video date on camvas

toru: it's an image recognition

sangwhan1: possible working now
... [ showing demo ]
... using JS recognition
... entirely JS
... technically possible now - the recognition code is not very good in this demo, but can be improved
... should be more accurate
... URL

ryoichi: you need to send a data to server

sangwhan1: if you see a mustache, it recognizes a person

<sangwhan1> s/face recognition is not good for detecting people face though/the recognition code is not very good in this demo, but can be improved/

Wook(?): R8, identifying location
... i also think R6 and R15 are similar
... majoring information of contential dectation
... can it make more general

futomi: make sense but want to make this requirement to be separated

<sangwhan1> s/R9, identifying/R8, identifying/

toru: R15 is specific
... needed technology / use cases is differne

sangwhan1: base technology is the same?
... deliverable of LLL
... you can get canvas out of video, it's up to users how to implement data

futomi

s/ftomi/futomi

futomi: R15 says personal meta data
... I think it's different

<sangwhan1> s/[[/i also think R6 and R15 /

<sangwhan1> s/i also think R6 and R15 /i also think R6 and R15 are similar/

BB: R15 is just a identification
... can be differenciate of use cases

Wook: should focus between devices
... idenfying PP

AA: identify personal profile +++
... do we precise to get actual analysis

sangwhan1: seems like can be combined **
... general man or woman to distinguish "who"
... near field service discovery

toru: use case prospective, we shouldn't combine

futomi: not combined

<sangwhan1> s/zakim, make log public//

toshi: would like to confirm my presentation

<sangwhan1> s/zakim, draft minutes//

toshi: review of mapping
... my proposal is to review continuously map and mapping which contains SVG is resolution

<sangwhan1> s/ and PP/ /

[everybody agreed]

<sangwhan1> meeting adjourned

s/my propose of mapping and PP could be continuously discussed/my proposal is to review continuously map and mapping which contains SVG is resolution/

- DRAFT -

Web-based Signage Business Group meeting at TPAC2012

01 Nov 2012

Attendees

Contents

Summary of Action Items

Scribe.perl diagnostic output