08:22:26 RRSAgent has joined #signage 08:22:26 logging to http://www.w3.org/2012/11/01-signage-irc 08:22:41 Zakim has joined #signage 08:28:07 Adenda:http://www.w3.org/community/websignage/wiki/Group_meeting_at_TPAC_2012 08:29:14 rrsagent, draft minutes 08:29:14 I have made the request to generate http://www.w3.org/2012/11/01-signage-minutes.html Shinji 08:30:11 Meeting: Web-based Signage Business Group meeting at TPAC2012 08:30:55 Chair: Futomi Hatano 08:31:15 Agenda: http://www.w3.org/community/websignage/wiki/Group_meeting_at_TPAC_2012 08:32:07 agenda? 08:36:43 agenda+ Welcome 08:37:03 agenda+ Proposals from the BG members 08:37:20 agenda+ Joint meeting with DAP 08:38:00 agenda+ Proposals from the observers (if any) 08:38:21 agenda+ Reviewing our draft 08:38:25 agenda? 08:40:10 agenda 1 = Welcome [Chair] 08:41:12 agenda 2 = Proposals from the BG members from NTT and KDDI [Chair] 08:42:07 agenda 3 = Joint meeting with DAP [Chair] 08:42:34 agenda 4 = Proposals from the observers (if any) [Chair] 08:43:14 agenda 5 = Reviewing our draft [Chair] 08:43:19 agenda ? 08:44:25 Scribe: Naomi Yoshizawa and Shinji Ishii 08:48:47 rrsagent, help 09:14:38 Zakim, help 09:14:38 Please refer to http://www.w3.org/2001/12/zakim-irc-bot for more detailed help. 09:14:41 Some of the commands I know are: 09:14:41 xxx is yyy - establish yyy as the name of unknown party xxx 09:14:41 if yyy is 'me' or 'I', your nick is substituted 09:14:41 xxx may be yyy - establish yyy as possibly the name of unknown party xxx 09:14:41 I am xxx - establish your nick as the name of unknown party xxx 09:14:41 xxx holds yyy [, zzz ...] - establish xxx as a group name and yyy, etc. as participants within that group 09:14:42 xxx also holds yyy - add yyy to the list of participants in group xxx 09:14:42 who's here? - lists the participants on the phone 09:14:42 who's muted? - lists the participants who are muted 09:14:42 mute xxx - mutes party xxx (like pressing 61#) 09:14:42 unmute xxx - reverses the effect of "mute" and of 61# 09:14:42 is xxx here? - reports whether a party named like xxx is present 09:14:43 list conferences - reports the active conferences 09:14:45 this is xxx - associates this channel with conference xxx 09:14:45 excuse us - disconnects from the irc channel 09:14:45 I last learned something new on $Date: 2012/10/14 23:37:24 $ 09:16:19 JonathanJ1 has joined #signage 09:21:23 Zakim, what conference is this? 09:21:24 no conference has been selected, Shinji 09:25:32 q+ 09:25:36 q? 09:25:42 ack 09:25:59 Zakim, ack 09:25:59 I don't understand 'ack', Shinji 09:26:18 ack next 09:26:37 q? 09:57:03 tomoyuki has joined #signage 10:34:58 futomi has joined #signage 10:37:55 sangwhan has joined #signage 10:38:01 sangwhan has left #signage 10:56:59 sangwhan has joined #signage 11:16:14 JonathanJ1 has left #signage 12:11:58 Shinji has joined #signage 12:16:49 futomi has joined #signage 12:22:49 tokamoto has joined #signage 12:23:00 naomi has joined #signage 12:31:00 RRSAgent, make minutes 12:31:00 I have made the request to generate http://www.w3.org/2012/11/01-signage-minutes.html Shinji 12:34:54 rrsagent, make log public 12:35:33 rrsagent, draft minutes 12:35:33 I have made the request to generate http://www.w3.org/2012/11/01-signage-minutes.html naomi 12:39:36 toru: let's start. thank you for coming 12:39:43 ... will discuss about some topics 12:39:49 ... let's introduce ourselves first 12:40:01 ... there are two proposals from members - NTT and KDDI 12:40:12 ... s/toru/futomi/ 12:40:28 ... would like to observer's opinion 12:40:36 ... and talk about use cases and requirements 12:40:49 ... I am Futomi Hatano, Newpholia corporation, web developer 12:40:53 ... thank you for coming 12:41:26 ryosuke: I am Ryosuke @@ from NTT 12:41:32 s/@@/Aoki/ 12:42:06 Toshi: I am Toshiyuki Okamoto of KDDI 12:42:17 whyun has joined #signage 12:42:32 Chaals: work for Yandex. I am here for 20 minutes. co-chair of Web Apps 12:42:39 a12u has joined #signage 12:42:45 ... one specification might work on WebApps 12:42:53 ... want to talk about ideas / specifications 12:43:13 ... important to WebApps group to listen, what we need 12:43:24 ... if you don't, you will be completely ignored 12:43:42 AA: @@ from PP. working on TV systems 12:44:02 Ryoichi: Ryoichi Kawada from KDDI 12:44:12 ... research and develop 12:44:25 aizu: Hiroyuki Aizu of Toshiba 12:44:33 ... manufacture of PC and devices 12:44:44 ... try to integrate Brower to TV 12:44:48 s/@@ from PP/hyun wook from ETRI/ 12:44:55 Katsuhiko: Katsuhiko Kawazoe of NTT 12:45:05 ... responsive of creating new business 12:45:10 ... co-chair of digital signage Japan 12:45:21 shinichi: Shinichi Nakao of Newpholia 12:45:33 ... working with futomi 12:45:49 Hiroshi: Hiroshi Yoshida of Hakuhodo which is 2nd largest PR company in Japan 12:45:53 Kiyoshi has joined #signage 12:45:59 Shinji: Shinji Ishii of NTT and W3C 12:46:07 ... working on digital signage 12:46:32 AA: ... from ETRI 12:46:42 BB: kim from KAIST 12:46:47 ... interactive signage 12:46:49 s/AA/SeungHei Kim/ 12:47:05 ... try to technology standard 12:47:11 CC: ..Kim from KAIST 12:47:17 ... researching signage 12:47:21 ... collecting @@ information 12:47:34 DD: Soobin Lee from KAIST 12:47:43 ... first TPAC and hope to contribute a lot 12:47:53 EE: Kang from Korea 12:48:11 FF: Kiyoshi Tanaka of NTT, researcher of @@ 12:48:26 Manyoung: Manyoung of Future technology 12:48:40 Yamada: Koichi Yamada of KDDI 12:48:54 Mitsuru: Mitsuru Yamada of KDDI 12:49:09 Koichi: Koichi Takagi of KDDI 12:49:19 ... relationship between system apps and signage 12:49:27 manyoung has joined #signage 12:49:32 toru: Toru Kobayashi of NTT 12:49:36 s/ Koichi Yamada of KDDI// 12:49:46 ... group leader of device oriented group 12:49:52 ...expect to have many comments 12:50:02 alan: Alan Bird of W3C 12:50:15 shin has joined #signage 12:50:20 futomi: proposal of BG members 12:50:41 chaals: co-chair of WebApps 12:50:52 tomoyuki has joined #signage 12:50:55 ... sent some comments to you 12:51:06 ... highlightened is push API 12:51:18 ... meant to allowed to application to sleep 12:51:32 ... messages can wait to the application what to do 12:51:40 ... working draft of WebApps 12:51:41 sblee has joined #signage 12:51:46 s/@@/IPTV/ 12:51:50 ... by AT&T, Telephonica ,etc 12:52:00 ... Mozilla looks implement something like this 12:52:30 ... /me thanks kiyoshi 12:52:54 chaals: disaster senario 12:53:00 Skim has joined #signage 12:53:03 yamaday has joined #signage 12:53:23 ... WebApps needs usecases of demands and implementations 12:53:36 ... it's not going fast 12:54:01 ... when you want to some WGs especially for implementing 12:54:09 ... speak up 12:54:23 ... they don't mind to listen to your opinions 12:54:36 ... and please be nice 12:54:38 Present + Toshiyuki Okamoto, Ryosuke Aoki, Charles McCathie Nevile, Wook Hyun, Ryoichi Kawada, Hiroyuki Aizu, Katsuhiko Kawazoe, Shinichi Nakao, Hiroshi Yoshida, Shinji Ishii, Naomi Yoshizawa, Toru Kobayashi 12:54:47 toru: what is the difference between Web Socket and @@ 12:54:58 Alan has joined #signage 12:54:59 Chaals: WebSocket is OO 12:55:09 ... push API is transport independent 12:55:22 ... application will register some services 12:56:02 Present + Manyoung Cho 12:56:15 I have made the request to generate http://www.w3.org/2012/11/01-signage-minutes.html Alan 12:56:28 rrsagent, set log world 12:56:33 toru: why operators interested in it 12:56:56 chaals: s/operators/Opera/ 12:57:07 s/operators/Opera/ 12:57:33 chaals: ^^^^^ 12:57:44 s/@@/PushAPI/ 12:57:45 ... feel free to send questions to me anytime 12:57:57 futomi: presentation of NTT 12:58:14 Skim has joined #Signage 12:58:38 aoki: Multi-screen collaboration and disaster situation 12:58:48 ... [ reviewing slide ] 12:58:59 ... carry mobile devices such as tablet 12:59:02 s/00/connection/ 12:59:12 ... disasters occured frequently 12:59:20 Present+ Koichi Takagi, Mitsuru Yamada, J. Alan Bird, Manyoung Cho, Kiyoshi Tanaka, Soobin Lee, Gisung Kim, Jaejeung Kim, Sung Hei Kim, Shin-Gak Kang, Masahito Kawamori 12:59:26 ... Japan was struck by big earthquake and tsunami 12:59:39 ... after the disaster people want to get informtaion 12:59:49 hiroki has joined #signage 12:59:53 ... safety and get to know friends and family 13:00:03 ... also wanted to know evacuation center 13:00:13 ... but it was difficult to get those information 13:00:28 ... our research goal is to share information after disaster quickly as possible 13:00:35 JonathanJ1 has joined #signage 13:00:40 ... internet access was difficult and impossible 13:00:53 ... infrastructure was damaged or network load was overloaded 13:01:17 ... wireless screen devices didn't work 13:01:32 yamaday has joined #signage 13:01:35 ... each devices has different carriers and operation systems 13:01:48 ... each of them has different compliance 13:02:04 ... each area network has connectivity using HTML5 browser 13:02:06 Present + Koichi Takagi, Mitsuru Yamada, J. Alan Bird, Manyoung Cho, Kiyoshi Tanaka, Soobin Lee, Gisung Kim, Jaejeung Kim, Sung Hei Kim, Shin-Gak Kang, Masahito Kawamori 13:02:15 ... multi-screen collaboration has 3 connections 13:02:18 ...1 @@ 13:02:26 ...2 how to use information 13:02:27 @@@@ 13:02:47 ... 3 how to investigation to clarify the problem after disaster 13:02:57 ... extracted problems from surveys 13:03:09 ... [ revieiwng slides ] 13:03:26 ... would like to discuss 3 problems 13:03:54 ... 1. system can't catch up with current disaster situation 13:04:04 ... situations changes rapidly 13:04:14 ... internet access will be affected by heavy traffic 13:04:24 ... time of internet access recovery is depend on the places 13:04:39 ... evacuation center or train station get to communiti3es 13:04:50 ... devices of local network change frequently 13:05:09 ... to be effected by multi-screen @@ 13:05:23 ... want to propose information sharing using core devices 13:05:30 ... at evacuation center using wifi 13:05:40 kotakagi has joined #signage 13:05:49 ... core device collects local information like foods supply 13:06:05 ... it distributes information of volunteers or other evacuation center 13:06:14 NTT' Ryosuke Aoki propose: Information sharing using core devices 13:06:16 ... they upload corrected information 13:06:31 ... information sharing realize network available 13:06:43 ...3. there are too AAAAAAA 13:06:50 ... [ reviewing photos ] 13:07:08 hiroki has joined #signage 13:07:09 ... [ puts hundreds of notes ] 13:07:17 ... difficult to check and read all of them 13:07:40 ... to solve this problem is to layout reconsiliation BBBB 13:07:50 ... core device such as Digital signag 13:08:02 ... core device download information requested from display on their mobile 13:08:12 NTT' Ryosuke Aoki propose #2 : Layout reconstruction of trimmed information 13:08:13 ... each people get information targetted one 13:08:30 ... finally the layout construct reviewing information 13:08:48 ... they can store information in their mobile 13:09:03 ... 10. senior / impaired people can't understand the announcement 13:09:21 ... not everybody could understand all informtaion 13:09:26 ... need to be easy to understand 13:09:40 ... display information according to user profile on their mobile 13:09:48 NTT' Ryosuke Aoki propose #3 : displaying information according to user profile 13:10:13 ... for seniors to recomment to use big mobiles 13:10:23 s/recomment/recommend 13:10:38 ... need to discuss those 3 issues 13:10:59 ... how can mark up distinguish core devices from non-core devices 13:11:04 ... how can CCCCC 13:11:08 ... how can DDDDD 13:11:27 futomi: let's talk about this standarlization step by step 13:11:49 ... 1. information shring using core devices 13:11:54 shige__ has joined #signage 13:12:07 ... there is a leader at each evacuation center 13:12:25 ... each core devices collect and output information 13:12:51 ... if hte core device is full battery, core devices turns into automatically FFF 13:13:05 ... adopts sharing information 13:13:23 explains core device non-core devices 13:13:24 futomi: personnel devices could be a device? 13:13:54 ... I don't want my smartphone gets core device 13:14:06 ... if mine become to it, traffic will concentrate to my phone 13:14:21 ... there there are many people around my mobile it will be hang up 13:14:39 ryosuke 13:14:42 Chair: smartphone is core device? 13:14:53 ryosuke: if it's connected to power, your mobile could be core device 13:15:17 ... it's possible for your phone to be a core device short time 13:15:40 ... core device might not be able to run always 13:15:50 ... just only collection information 13:15:57 ... and updates 13:16:10 s/collection/collect/ 13:16:23 futomi: core device should be digital signage terminal 13:16:30 ... it has a big battery 13:16:58 GG: PPP 13:17:23 s/GG/Shin-Gak Kang/ 13:17:52 ryosuke: Tokyo station has a lot of digital signage which could be an evacuation center 13:18:07 ... if each mobile could be core device GGGGG 13:18:37 hyun: digital terminal could communicate to evacuation information 13:18:55 sangwhan has joined #signage 13:19:02 sangwhan1 has joined #signage 13:19:12 ... is my smartphone send information? 13:19:22 ryosuke: you can use it through router 13:19:36 hyun: localized network? 13:19:55 ryosuke: core devices connected to wifi router which directly use @@ 13:19:59 rrsgagent, draft minutes 13:20:02 ... should be easy 13:20:08 s/rrsgagent, draft minutes// 13:20:12 rrsagent, draft minutes 13:20:12 I have made the request to generate http://www.w3.org/2012/11/01-signage-minutes.html sangwhan1 13:20:28 hyun: how PPPPP 13:20:45 futomi: wondering which part is good for web technology 13:20:57 ... some systems apps not relevant to web 13:21:05 ... some functions is web technology 13:21:16 present+ Sangwhan_Moon 13:21:31 ryosuke: core device through and have server function 13:21:36 ... connecting internet 13:21:45 ... local area network is core device 13:21:54 ... same display and same functions 13:22:04 ... so user can display information 13:22:12 futomi: HTML is already working 13:22:22 ... what kind of web technology will be used 13:22:33 ... what kind of api should be required 13:22:58 ryosuke: apis of develper using this function [pointing slides ] 13:23:02 manyoung has joined #signage 13:23:18 futomi: are we talking about OOO 13:23:51 futomi: smartphone upload information 13:24:12 ryosuke: core device finds each devices in a local area network 13:24:18 Slide: Information sharing using core device 13:24:20 s/how PPPPP/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/ 13:24:33 futomi: key of this proposal IIII 13:25:06 ryosuke: we want to create this API as core device 13:25:25 rrsagent, draft minutes 13:25:25 I have made the request to generate http://www.w3.org/2012/11/01-signage-minutes.html sangwhan1 13:25:31 futomi: discovering devices around me i.g. NFC or @@ or wifi-direct 13:26:04 ryosuke: Oofunato or Miyagi had big damages 13:26:09 s/@@/bluetooth/ 13:26:10 ... they made wifi network 13:26:21 q? 13:26:28 ... but this system connection is wireless 13:26:48 BB: want to know what kind of information the core device correct 13:26:53 s/BB/Gisung/ 13:26:59 ryosuke: safety of family or friends information 13:27:29 ... people separated from family and stayed each evacuation center having no internet connection nor telephone 13:27:45 ... calling children could't established 13:28:07 s/could't established/was not possible/ 13:28:08 ... if core device correct those information, the volunteer moves and distribute it to each devices 13:28:15 BB: who makes html document 13:28:22 s/BB/Gisung/ 13:28:37 ryosuke: volunteers and I am now forming system 13:29:00 Katsuhiko: how to share information at the same time 13:29:10 ... peer to peer information 13:29:19 ... information shouldn't be changable 13:29:29 gisungkim has joined #signage 13:29:31 ... but could be shareble 13:29:43 ryosuke: reference p to p system 13:30:10 ... we use a flow by human 13:30:24 ... people detect core device 13:30:38 ... people comes to evacuation center detect core device 13:30:48 ... so they can collect information 13:31:26 q? 13:31:35 ryosuke: miyagi / oofunato had many evacuation center 13:31:45 ... we could use human power 13:31:52 slide #14 : question from ETRI Kang, ETRI Hyun, KAIST Gisung, NTT Katsuhiko, 13:32:19 ryosuke: 2 proposal Multi-screen collaboration of digital PPPP 13:32:32 ... How can mark up reconstruct a layout after data trimming 13:32:39 futomi: is it OCR? 13:32:42 ryosuke: yes 13:32:58 ... Optical Caractor Reader 13:33:30 ... [ showing slides - hundreds of notes ] 13:33:55 ... if safety information could get into as digital signage 13:34:01 rrsagent, draft minutes 13:34:01 I have made the request to generate http://www.w3.org/2012/11/01-signage-minutes.html JonathanJ1 13:34:09 ... an user could access to those information 13:34:31 futomi: receiving information to a mobile 13:34:42 ryosuke: but display size is different 13:34:44 ..silde #18 Multi-screen collaboration of digital signage and mobile deives 13:35:02 futomi: information is digital data 13:35:10 ... this requirements discussed by our BG 13:35:18 ... usecase and requirements documents 13:35:36 ... it requires discovering terminal and communicating terminal 13:35:44 ... those are listed in our document 13:35:50 ... let's talk it later 13:36:11 aizu: clip @@? 13:36:23 ryosuke: user could pick up targetted information 13:36:37 s/targetted/targeted/ 13:36:42 ... people could select and collect information easily 13:36:52 ... cut and paste are easy 13:37:05 ... could do trimming information 13:37:18 aizu: looks like evernote function 13:37:24 Present + Sangwhan Moon, Peter Hutchins 13:37:24 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 13:37:33 ryosuke: our research focus is how to clip and layout reconstruction 13:37:40 futomi: challenging 13:37:56 BB: issue suggested is selecting partial area of web page? 13:38:10 ... after collecting multiple ``` 13:38:24 ... are you talking about everything? 13:38:43 futomi: big data first and we pick up information 13:39:01 ... one person needs to small portion of information 13:39:11 ... it should be transfered to quickly 13:39:18 CC: portion? 13:39:32 ... content could be ??? 13:39:48 ..slide #19 Layout reconstruction of trimmed information 13:39:49 ... clip something and pickup information 13:40:12 futomi: important is to how to @@ 13:40:15 s/BB/Soobin/ 13:40:23 s/futomi:/toru:/ 13:40:26 s/CC/Kang/ 13:40:41 toru: @@@ 13:41:09 katsuhiko: this function, big map, I want to pick up information limited one 13:41:28 a lady: in this situation, implementation, who is where 13:41:36 ... you may need to use keyword 13:41:56 toru: user's requirements is important 13:42:08 ... Mr. A requires a bathroon 13:42:21 ... automatically the device could find 13:43:18 FF: the case of disaster 13:43:28 ... human hand write discription 13:43:33 ... google finder 13:43:40 s/discription/description/ 13:43:41 ... what kind of @@ are you using 13:43:49 s/google finder/google person finder/ 13:44:00 ryosuke: Googld personal finder requires internet accessibility available 13:44:12 s/oogld/oogle/ 13:44:15 ... many volunteers wrote each information (typed) 13:44:22 ... this sitution is after disaster 13:44:31 ... thought internet access is available 13:44:52 FF: local area can be installed and shared by person 13:45:09 ryosuke: hoping personal finder is volunteer typing 13:45:16 ... but want to do it automatically 13:45:33 ... tv reporters collected information and typed 13:45:38 ... were hard 13:45:55 slide #19 : question from KAIST Soobin, ETRI Kang, ETRI Sung, ETRI Wook,, comment from NTT Katsuhiko 13:46:09 ryosuke: 10. Displaying information according to user profile 13:46:17 ... display design 13:46:27 ... change mobile speed 13:46:33 ... can see information visually 13:46:43 ..slide #23: Displaying information acceding to user profile 13:46:50 q+ 13:46:52 ... also senior people could get it but not small letters 13:47:01 q? 13:47:07 futomi: is this a personal devices? 13:47:16 ryosuke: each people could download an announcement 13:47:27 ... if html documents only normal correspondence 13:47:28 shin has joined #signage 13:47:34 ... some people couldn't get those 13:47:53 ack sangwhan1 13:48:07 sangwhan1: operating system @@@ 13:48:27 ... netral system `````` 13:48:35 ... the device should be pre-configured 13:48:48 ... if you unable to use the device, what do you do 13:49:13 ... accessibility does ¥¥¥ 13:49:28 Comment/Question from Sangwhan (Open software ASA). 13:49:29 ... if person adjust device **** 13:49:55 FF: persona devices LLLLLLLL 13:50:00 s/operating system @@@/the operating system should be taking care of this, not the content dispatcher/ 13:50:11 ... if it's personal device, it might not be possible 13:50:22 s/netral system ``````/the content should be neutral in nature and it should be up to the device to provide it in a accessible manner/ 13:50:44 ryosuke: supply or lease a device to senior people 13:51:00 FF: OOO 13:51:10 s/accessibility does ¥¥¥/the accessibility groups work on the specs to make this "just work" for compliant devices/ 13:51:16 toru: could circulate each device? 13:51:43 q? 13:51:49 q- 13:52:09 GG: spoken by TTN 13:52:16 s/Open software ASA/Opera Software ASA/ 13:52:28 ... low sentence, information provider could convey easily 13:52:35 toru: meaning recognition? 13:52:44 GG: yes 13:52:54 futomi: thanks, ryosuke 13:53:04 rrsagent, draft minutes 13:53:04 I have made the request to generate http://www.w3.org/2012/11/01-signage-minutes.html sangwhan1 13:53:13 slide #23: question/comment from ETRI/Kang, Opera Software/Sangwhan, NTT/Toru, KAIST/Gisung 13:53:35 next session will start 15:30 13:56:17 shinji_ has joined #signage 13:56:53 test 14:02:26 Present+ Jonathan_Jeon 14:04:08 Present+ Hiroyuki_Aizu 14:13:43 kotakagi has joined #signage 14:17:34 whyun has joined #signage 14:18:55 Alan has joined #signage 14:29:54 yamaday has joined #signage 14:31:50 sblee has joined #signage 14:32:03 agenda? 14:33:02 toshi: toshi of KDDI 14:33:04 Next KDDI presentation 14:33:07 Please see item 1 of http://www.w3.org/community/websignage/wiki/TPAC2012_KDDI_Input 14:33:16 ... Mapping functions for signage 14:33:33 ... mapping functions for websignage 14:33:46 ... believe it7s important topic 14:33:57 ... also a big one for SVG grup 14:34:03 s/grup/group/ 14:34:24 ...1. Map and signage 14:34:37 ... map is one of the important and indispensable component for signage 14:34:42 shin has joined #signage 14:34:42 Skim has joined #Signage 14:34:42 ... [ showing slide ] 14:34:56 ... maps can be used to help travellers 14:35:06 ... large trip map projects is goingto move things ahead 14:35:20 slide: Map Signage 14:35:27 ... according to the use cases and requirements R3. Commuication @@ 14:35:48 ... 2. Map and Disaster relief and signage 14:35:51 slide: Mapping Disaster Relief and Signage 14:36:09 ... map will be the most important information phenotype helping disaster relief 14:36:11 s/Communication @@/Communication with a touched device/ 14:36:27 ... ITU's actions are - announcement and Liaison to W3C 14:36:51 ... such as evacuation shelter map and homecoming support map 14:37:18 ... disaster is one of the important use cases for this BG 14:37:34 ... progress report of standardization at W3C 14:37:51 ... March 2012, the new charter of SVGWG 14:38:01 ... prmotion of the standardization of the mapping function 14:38:15 ... possibility to standardize some of these as basic functions of SVG2 14:38:27 ... in the last f2f September 2012 of SVGWG 14:38:47 ... agreed to standardize a part of the mapping functions as a part of basic functions of SVG2 by generalizing it 14:39:03 ... details our technical discussion is outscope now 14:39:08 ... use cases 14:39:16 ... off-line mapping system at the time of disaster 14:39:26 ... for signage with a variety of screen size and shapes 14:39:33 ... only clipping on map 14:39:42 ... not just only mapping but can be use images 14:39:51 ... and can download 14:40:03 ... in the W3C only SVGWG works on mapping now 14:40:17 ... appear SVG technology on signage 14:40:33 ... want to talk about mapping function 14:40:44 ... Map an Signage 14:40:55 futomi: ideas? opinions? 14:41:10 ... question. what is the benefit of using SVG maop 14:41:14 s/maop/map/ 14:41:21 ... people usess Google map 14:41:27 ... but it does't use SVG 14:41:36 ... why google doesn't use SVG? 14:41:43 toshi: 1st is @@ 14:41:53 s/@@/off-line 14:42:02 ... google map data is big size 14:42:15 ... SVG gets information what we need 14:42:18 ... exactly 14:42:30 futomi: what's the difference? 14:42:45 ... a map using SVG was heavy 14:42:52 ... google one was faster and light 14:43:09 ... not familyliar with map technology but want to know clear benerfit 14:43:40 ryoichi: SVG map merit is close to platform 14:43:50 ... and vendor independent 14:43:55 ... SVG is a platform technology 14:44:29 futomi: is there other mapping @@ 14:44:41 s/@@/in real/ 14:44:56 present + Hidetoshi Yokota 14:45:03 ryoichi: one of KDDI has a service called map for use in a case of disaster 14:45:09 ... navigation of disaster time 14:45:16 ... uses SVG technolgy 14:45:54 ... [ryoichi looks for the demonstration ] 14:46:11 toru: what is off-line mapping 14:46:22 ... do you need a server? or only client? 14:46:34 toshi: don't need a server 14:46:40 ... show a map only references 14:47:05 ... sigange terminal device mapping information 14:47:20 toru: in advance, signage terminal could download data 14:47:29 toshi: including mapping data 14:47:56 ryoichi: we don't have to rely on networks 14:48:11 futomi: data could be update? 14:48:24 ryoichi: you have to be online though 14:48:37 ..And we can chose combination with server or without server 14:48:39 ... [ showing demo ] 14:49:08 Additional presentation from Kawata-san 14:49:35 BB: mapping and map should be different meanings 14:49:57 ... which definition you are talking? 14:49:59 s/BB/Wook/ 14:50:18 toru: mapping is integration of information 14:50:29 ... map is a navigation or rout information 14:50:45 toshi: we talk about both of it 14:50:57 ryoichi: [ showing demo ] 14:50:59 Additional presentation is "SAIGAI Navi" 14:51:09 ... this system works without 3G 14:51:26 futomi: seems like a feature phone 14:51:38 ryoichi: kind of old tech 14:52:12 tomoyuki has joined #signage 14:52:36 futomi: do you use an ordinary browser or proprietary application? 14:52:40 ryoichi: the later one 14:52:46 hiroki has joined #signage 14:52:53 ... at the disaster you need GPS 14:53:01 futomi: smartphone service? 14:53:02 This service is using map and mapping in feature phone 14:53:10 ryoichi: not yet but in the future 14:53:26 Next topic 14:53:47 futomi: proposal from observers 14:53:51 ... anything? 14:54:06 ... then review our draft 14:54:12 ... long long long document 14:54:30 ... URL 14:54:46 ...@@@ 14:55:01 JonathanJ1 has joined #signage 14:55:15 futomi: new proposal are welcome 14:55:47 http://www.w3.org/community/websignage/wiki/Web-based_Signage_Use_cases_and_Requirements 14:56:38 ... R.1 Making contents using a declarative approach 14:56:46 ... had a workshop in Makuhari last June 14:56:57 s/@@@// 14:56:57 ... some member proposed declarative approaches 14:57:41 ... we can use HTML5 or smile 14:57:44 hiroki has joined #signage 14:57:55 ... how can I use HTML or SMILE 14:58:06 s/smile/SMILE/ 14:58:18 tomoyuki has joined #signage 14:58:46 ... [ explaining requirements ] 14:59:02 ... [ read the page ] 15:01:40 s/SMILE/SMIL/ 15:03:56 ... are you interested in HTML appraoch or SMIL? 15:04:51 tomoyuki_ has joined #signage 15:04:56 gskim has joined #signage 15:06:00 Toru: just clralfication question in this session process 15:06:18 AA: want to discuss about timing 15:06:26 ... fully supported by advertisement on time 15:06:37 s/AA/Gisung/ 15:06:42 ... signage input generates information and you can schedule one 15:06:49 ... event based one is important 15:06:54 ... want to talk about it 15:07:03 futomi: scheduled one 15:07:39 ... what is the difference between scheduled one or R9 or R14 15:07:55 Kiyoshi_ has joined #signage 15:08:19 BB: advertiser pay a thousand @@ 15:08:23 ... looks into signage 15:08:33 ... distract signage pays 1000 dollars 15:08:37 ... user interactive 15:08:46 ... could be disturbing for advertisers 15:08:50 ... could be have clear senario 15:08:57 ... compensate issue 15:09:17 ... scheduled content 15:09:29 ... another content by user interactively 15:09:47 ... is the current web-based signage or web application 15:09:53 ... do we allow ?? 15:10:03 ... free advertisement 15:10:10 ... during the time 15:10:16 ... annotating by markup 15:10:31 ... structure which supports two type of conttents 15:10:41 s/conttents/contents/ 15:10:52 ... could be a senario or requirements 15:11:07 ... how to support advertisement 15:11:41 s/BB/Jaejeung/ 15:11:43 futomi: do you assume a senario has a interactive content or static one 15:11:58 AA: scheduled one starts 1 o'clock 15:12:06 ... a use turn on movie 15:12:18 ... 5 minutes left, another advertisement starts 15:12:44 ... we should provide something tool annotation of web contents designer 15:12:54 ryoichi: do you have a business examples? 15:13:07 BB: we are research institute 15:13:28 ... we have met this issue people interuppted scheduling 15:13:43 ryoichi: what do you mean user adoptive 15:13:49 BB: adoptive 15:14:06 ... base of signage is plain content of schedule 15:14:34 ... we are looking into @@@ 15:14:47 scribenick: Shinji 15:15:27 s/BB/Gisung/ 15:15:48 Futomi is confireingi time scheduled signage 15:16:48 Jaejeung explain an example of time scheduled signage 15:17:24 sangwhan has joined #signage 15:17:32 rrsagent, draft minutes 15:17:32 I have made the request to generate http://www.w3.org/2012/11/01-signage-minutes.html sangwhan 15:19:10 ack katsuhiko 15:19:30 from Gisung's mailLet me give an example. 15:19:30 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) 15:19:31 Advertisement B is also scheduled to be displayed just from 2 PM to 3 PM. 15:19:32 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. 15:20:19 Hiroshi : this use case is business format 15:22:27 q+ 15:22:29 Gisung: already 15:22:32 q- 15:24:00 q+ 15:25:56 q? 15:26:07 scribenick: naomi 15:26:11 sangwhan: @@@ 15:26:23 ... don't know why PPP 15:26:35 ... R14 15:26:59 ... should be solved programatically by IIII 15:27:58 ... submitted by YouTube 15:28:11 ... draft stage but could address the use cases 15:28:56 http://dvcs.w3.org/hg/html-media/raw-file/ae41dd28af33/media-source/media-source.html 15:30:21 ... [ explaining the draft ] 15:30:54 Sangwhan: explains "Media Source Extensions" 15:31:12 ... you might want to talk to Netflix guys or ask Mike Smith 15:31:59 toru: viewing videos simultaneousely? 15:32:06 Sangwhan: que 15:32:19 ... because costs too much 15:32:33 ... want to take @@@ 15:33:02 ... the draft is not final one 15:33:15 ... you can test which is available from Google 15:33:19 Skim has joined #Signage 15:33:27 ... Opera has implementation but it's not public 15:33:43 .. discussion about about dynamic content insertion 15:33:54 s/about about/about/ 15:35:27 futomi: media source extnetion could be a solution of R14 15:35:31 ... especially for video 15:35:33 Katsuhiko and Toru: In this session, we need discussion business use case, and then discussion gap analysis. 15:35:34 rotsuya has joined #signage 15:38:55 Futomo: R14 is related "Media Source Extensions" 15:40:44 s/extnetion/extensions/ 15:52:50 tokamoto has joined #signage 15:53:04 naomi has joined #signage 15:53:32 sangwhan has joined #signage 15:53:39 sangwhan1 has joined #signage 16:01:24 kotakagi has joined #signage 16:01:30 futomi: next requirements - R2 16:01:59 rotsuya has joined #signage 16:02:09 ... this requirements has been solved 16:02:26 ... for video contents PPP 16:02:32 ... the format of caption is necessary 16:02:39 ... web ttt is applicable 16:02:46 ... images and style text 16:02:53 ... no common capturing 16:03:08 ... we have a solution of video but not for static content 16:03:15 ... should we define the format? 16:03:20 ... or HTML? 16:03:56 sangwhan: what is the advantage of defining static content? 16:04:40 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 16:04:57 sangwhan: I don't think we need it and WG won't take it 16:05:07 futomi: ok then move to next topic 16:05:13 ... communication touch devices 16:05:27 ... when use touches signage terminal on he/her terminal 16:05:40 ... smartphone get information 16:05:43 ... gap analysis 16:05:55 ... exchange text data i.e., URL 16:06:09 ... we expect to transition to PPP WG 16:06:13 sblee has joined #signage 16:07:20 KK: communication of touch devices 16:07:38 ... looks like touch smartphone screen 16:07:54 ... you can commit OOO 16:08:02 s/KK/Kang/ 16:08:28 shin has joined #signage 16:08:57 ... personal devices 16:09:03 s/Kang/R3. Communication with a touched device/ 16:09:04 a lady: touch device is touch screen 16:09:26 ... personal devices 16:09:36 futomi: [ modifying wiki ] 16:09:46 s/R3. Communication with a touched device/R3/ 16:10:30 futomi: R4 16:10:38 ... bit difficult requirement 16:10:51 ... in Japan many smartphone has @@ communication function 16:11:01 s/@@/infrared/ 16:11:08 ... device to device communication inflate to common communicate with devices 16:11:24 ... if there are signage terminals, they has communication function. 16:11:33 ... all terminal scan personal devices 16:11:45 ... how do we communicate this PPP 16:11:57 ... how can we use this situation 16:12:03 ... wifi or bluetooth 16:12:06 s/this PPP/infrared base terminals/ 16:12:23 ... need to communicate only KKK 16:12:35 ... only solution is infrared communication 16:12:39 s/infrared base terminals/these terminals/ 16:12:48 ... if I want to communicate with next one, I just point to the terminal 16:12:51 ... easy for human 16:13:09 toshi: what is the difference between O and P 16:13:18 sangwhan1: UUUU 16:13:53 ... globaly available and standard in Japan from 10 years ago 16:14:01 ... not sure for the size of out of Japanese market 16:14:03 s/O and P/infraed and NFC/ 16:14:07 whyun has joined #signage 16:14:13 a lady: we can use NFC 16:14:28 ... you could make the requirement 16:14:34 s/a lady/Sung/ 16:15:01 sangwhan1: agreed. generalized or combing with NFC and R3 16:15:09 ... no API covered 16:15:31 futomi: smartphone with infrared function in Japan 16:15:43 ...do you still need the requirements? 16:16:12 BB: let's merge R3 and 4 16:16:33 futomi: then I combine R3 and 4 16:17:42 ACTION: Futomi to merge R3 and R4 16:18:20 Editors note: R3 and R4 will combine one requirement. 16:19:01 Thanks Sangwhan 16:19:10 futomi: R5. Discovered by personal devices 16:19:44 rrsagent, draft minutes 16:19:44 I have made the request to generate http://www.w3.org/2012/11/01-signage-minutes.html sangwhan1 16:19:44 ... when a signage terminal communicates with a personal device, a personal devices need to discover a specified terminal at first 16:20:06 ... /me sangwhan1 ++ 16:20:22 s/... \/me sangwhan1 ++// 16:20:43 futomi: Web Intents has hopes 16:20:59 ... one more way is network @ 16:21:51 ... [ playing a video of Daniel, Opera ] 16:22:50 http://dev.opera.com/articles/view/network-service-discovery-api-support-in-opera/ 16:25:15 futomi: not sure this API is available for the requirements 16:25:32 ... gotten advice from +++ 16:25:52 s/+++/the DAP WG/ 16:26:09 Sangwhan1: backing of UPnP, it's extensible 16:26:36 ... we hope other browser could take ** 16:26:46 ... at the moment UPnP is not free 16:26:52 ... we are paying for it 16:27:04 ... use cases paying regardless KKK 16:27:26 ... it's a very controversial topic - we haven't decided, too 16:27:55 futomi: I have programmed UPnP using JS before which was compliated 16:28:19 ... but I will remain this phrase 16:28:44 toru: UPnP or DLNA 16:28:57 ... ??? 16:29:08 Sangwhan1: complex problem to be solved 16:29:13 ... engaged communicatiohn 16:29:32 s/communicatiohn/communication/ 16:29:45 ... possibility using QR code or }}}} 16:29:52 ... requires user interaction 16:30:03 s/???/UPnP and DLNA is pre-registered./ 16:30:24 HH: what is the minimun requirements of layer 3 and 2 16:30:38 ... >>> 16:30:48 ... if we apply this to signage 16:31:08 s/}}}}/manual url input/ 16:31:24 ... if broadcaster feature is enough for bluetooth or wifi which requires OO 16:31:25 s/KKK/then this should not be a issue/ 16:31:40 ... what is the requirements for signage 16:32:15 ... it's not just a home environment? 16:32:33 ... or broadcaster environment 16:32:44 futomi: it will be limited situation 16:33:07 ... upper layer 16:33:35 futomi: R6 16:34:07 ... Capturing an end-user 16:34:27 futomi: In this requirement is only focus on layer 2. not include layer 3. 16:35:25 ... vendor machine implement a camera 16:35:39 ... will be valuable 16:36:39 futomi: putting video date on camvas 16:37:02 q+ 16:37:18 toru: it's an image recognition 16:38:13 sangwhan1: possible working now 16:38:27 ... [ showing demo ] 16:39:18 ... using JS recognition 16:39:23 ... entirely JS 16:39:52 ... technically possible now - face recognition is not good for detecting people face though 16:39:59 ... should be more accurate 16:40:06 ... URL 16:40:08 hiroki has left #signage 16:40:36 ryoichi: you need to send a data to server 16:40:56 sangwhan1: if you see a mustache, it recognizes a person 16:42:09 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/ 16:42:34 BB: R9, identifying location 16:42:56 ... [[ 16:43:07 ... majoring information of contential dectation 16:43:16 ... can it make more general 16:43:30 futomi: make sense but want to make this requirement to be separated 16:43:44 s/R9, identifying/R8, identifying/ 16:44:08 toru: R15 is specific 16:44:18 ... needed technology / use cases is differne 16:44:32 sangwhan1: base technology is the same? 16:44:48 ... deliverable of LLL 16:45:07 ... you can get canvas out of video, it's up to users how to implement data 16:45:16 ftomi 16:45:26 s/ftomi/futomi 16:45:35 futomi: R15 says personal meta data 16:45:42 ... I think it's different 16:45:44 s/[[/i also think R6 and R15 / 16:46:01 s/i also think R6 and R15 /i also think R6 and R15 are similar/ 16:46:37 s/LLL/this group is not to develop a computer vision library/ 16:46:37 BB: R15 is just a identification 16:46:38 shige has joined #signage 16:46:46 ... can be differenciate of use cases 16:47:09 s/BB/Wook/ 16:47:27 Wook: should focus between devices 16:47:42 ... idenfying PP 16:48:08 AA: identify personal profile +++ 16:48:31 ... do we precise to get actual analysis 16:49:11 sangwhan1: seems like can be combined ** 16:49:28 ... general man or woman to distinguish "who" 16:49:42 ... near field service discovery 16:50:06 toru: use case prospective, we shouldn't combine 16:50:39 futomi: not combined 16:50:45 zakim, make log public 16:50:45 I don't understand 'make log public', sangwhan1 16:50:52 s/zakim, make log public// 16:50:57 rrsagent, make log public 16:51:00 toshi: would like to confirm my presentation 16:51:02 zakim, draft minutes 16:51:02 I don't understand 'draft minutes', sangwhan1 16:51:09 s/zakim, draft minutes// 16:51:10 ... review of mapping 16:51:13 rrsagent, draft minutes 16:51:13 I have made the request to generate http://www.w3.org/2012/11/01-signage-minutes.html sangwhan1 16:51:58 ... my propose of mapping and PP could be continuously discussed 16:52:13 s/ and PP/ / 16:52:19 [everybody agreed] 16:52:28 meeting adjourned 16:52:51 rrsagent, make minutes 16:52:51 I have made the request to generate http://www.w3.org/2012/11/01-signage-minutes.html sangwhan1 16:55:13 Roy has joined #signage 16:55:18 Alan has left #signage 17:00:57 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/ 17:01:36 hiroki has joined #signage 17:01:51 hiroki has left #signage 17:04:52 rrsagent, make minutes 17:04:52 I have made the request to generate http://www.w3.org/2012/11/01-signage-minutes.html naomi 17:05:28 zakim, help 17:05:28 Please refer to http://www.w3.org/2001/12/zakim-irc-bot for more detailed help. 17:05:31 Some of the commands I know are: 17:05:31 xxx is yyy - establish yyy as the name of unknown party xxx 17:05:31 if yyy is 'me' or 'I', your nick is substituted 17:05:31 xxx may be yyy - establish yyy as possibly the name of unknown party xxx 17:05:31 I am xxx - establish your nick as the name of unknown party xxx 17:05:31 xxx holds yyy [, zzz ...] - establish xxx as a group name and yyy, etc. as participants within that group 17:05:32 xxx also holds yyy - add yyy to the list of participants in group xxx 17:05:32 who's here? - lists the participants on the phone 17:05:32 who's muted? - lists the participants who are muted 17:05:32 mute xxx - mutes party xxx (like pressing 61#) 17:05:32 unmute xxx - reverses the effect of "mute" and of 61# 17:05:32 is xxx here? - reports whether a party named like xxx is present 17:05:33 list conferences - reports the active conferences 17:05:34 this is xxx - associates this channel with conference xxx 17:05:34 excuse us - disconnects from the irc channel 17:05:34 I last learned something new on $Date: 2012/10/14 23:37:24 $ 17:06:25 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/ 17:06:51 rrsagent, make log public 17:06:56 rrsagent, make minutes 17:06:56 I have made the request to generate http://www.w3.org/2012/11/01-signage-minutes.html naomi 17:08:41 tracker, help 17:08:56 rrsagent, help 17:09:39 rrsagent, bye 17:09:39 I see 1 open action item saved in http://www.w3.org/2012/11/01-signage-actions.rdf : 17:09:39 ACTION: Futomi to merge R3 and R4 [1] 17:09:39 recorded in http://www.w3.org/2012/11/01-signage-irc#T16-17-42