07:46:04 <RRSAgent> RRSAgent has joined &websigns
07:46:04 <RRSAgent> logging to http://www.w3.org/2016/09/22-websigns-irc
07:46:07 <Zakim> Zakim has joined &websigns
07:46:12 <shigeya> q?
07:47:03 <shigeya> shigeya has left &websigns
07:48:22 <RRSAgent> RRSAgent has joined #websigns
07:48:22 <RRSAgent> logging to http://www.w3.org/2016/09/22-websigns-irc
07:48:23 <shigeya> q?
07:48:47 <Zakim> Zakim has joined #websigns
07:48:52 <shigeya> q?
07:49:52 <shigeya> RRSAgent, make draft minutes
07:49:52 <RRSAgent> I'm logging. I don't understand 'make draft minutes', shigeya.  Try /msg RRSAgent help
07:51:40 <shigeya> rrsagent, make minutes
07:51:40 <RRSAgent> I have made the request to generate http://www.w3.org/2016/09/22-websigns-minutes.html shigeya
07:52:06 <shigeya> rrsagent, where am i
07:52:06 <RRSAgent> I'm logging. I don't understand 'where am i', shigeya.  Try /msg RRSAgent help
07:52:21 <shigeya> Meeting: Web-Based Signage BG
07:52:38 <shigeya> Chair: Futomi Hatano, Kiyoshi Tanaka
07:52:46 <shigeya> Scribe: shigeya
07:53:00 <shigeya> Scribe: Shigeya Suzuki
07:53:04 <shigeya> scribenick: shigeya
07:54:31 <futomi> The URK of the wiki page for this meeting is here. https://www.w3.org/community/websignage/wiki/Group_meeting_at_TPAC_2016
07:55:14 <jay> s/URK/URL/
07:55:26 <futomi> s/URK/URL/
08:01:01 <shigeya> futomi: Time to start. thank you for coming.
08:01:10 <shigeya> … we will discuss about charter and working group.
08:01:21 <shigeya> … but at beginiing we want to share experiences.
08:02:00 <shigeya> … tanaka-san of NTT and shigeya suzuki of Keio describe the current topics.
08:02:15 <shigeya> … tanaka-san act as co-chair for today.
08:02:25 <shigeya> … first-part is self introduction
08:02:26 <nunoken1> nunoken1 has joined #websigns
08:02:37 <kawai> kawai has joined #websigns
08:02:39 <hyojin> hyojin has joined #websigns
08:02:43 <shigeya> futomi: Futomi Hatano of Newphoria.
08:02:56 <shigeya> kiyoshi: [self-introduciton continues]
08:03:27 <naomi> naomi has joined #websigns
08:04:22 <shigeya> asm: [Sam Sugimoto, of W3C speaks as Team contact]
08:04:25 <shigeya> s/asm/sam/
08:04:58 <shigeya> futomi: meeting agenda: https://www.w3.org/community/websignage/wiki/Group_meeting_at_TPAC_2016
08:05:30 <shigeya> [self-introduction part resumes]
08:05:48 <shigeya> jay: I’m AB. I hope for fruitful discussion.
08:05:58 <sam> sam has joined #websigns
08:06:16 <jihye> Jihye Hong, LG Electronics
08:07:33 <Dongwoo> Dongwoo has joined #websigns
08:10:09 <shigeya> futomi: Agenda bashing.
08:10:22 <shigeya> futomi: first part is information sharing.
08:10:32 <shigeya> … second part is implementation status ahring.
08:10:38 <shigeya> s/ahring/sharing/
08:10:55 <shigeya> … in the afternoon, we like to review the charter document.
08:11:20 <shigeya> … it’s already publisehd on net, and some of the members met to discuss, but we’d like to discuss in detail here.
08:11:39 <shigeya> … if we don’t complete today, we will continue meeting in tomorrow.
08:12:07 <shigeya> kiyoshi: there is discussion on emergency profile. I’m wondering if @1@ is working on the document.
08:12:33 <shigeya> .. if he doesn’t prepare the document, we’ll skip that part.
08:12:50 <shigeya> s/.. if/…/
08:13:14 <shigeya> s/@1@/Mr. Han/
08:14:05 <shigeya> futomi: sharing of current activities.
08:14:20 <shigeya> … we have published several documents.
08:14:47 <shigeya> … you can read these document on the BG web site
08:15:03 <shigeya> (showing use-case document)
08:15:35 <shigeya> (showing the three published profile documents )
08:17:16 <shigeya> kiyoshi: these documents inludes architecture discussion?
08:17:21 <jay> q+
08:18:21 <shigeya> jay: is there necessity to update these documents?
08:19:19 <shigeya> futomi: there are new APIs emerged for web-based signage. For example, currently we can store data in computer using index database API or file sytem API. Late file system API is obsoleted.
08:19:30 <kawai_> kawai_ has joined #websigns
08:19:50 <shigeya> … for new file system API deploped,
08:20:03 <shigeya> … if new useful API implemtend for browsers then we will update new documents.
08:20:45 <shigeya> ack jay
08:21:15 <shigeya> @2: what is next step for the deliverable?
08:21:30 <shigeya> futomi: last of the meeting, we decided to close this BG if WG is created.
08:21:45 <shigeya> … if the working group created, we cant update as BG.
08:21:55 <shigeya> … I think we can update as working grop
08:22:02 <shigeya> kiyoshi: really?
08:22:53 <shigeya> … we can create and use CG for updating and getting feedbacks.
08:23:08 <shigeya> @2: how about core profiel document?
08:23:21 <shigeya> … for this document, we need to update.
08:23:40 <shigeya> … tilte is currently “architecture..” but this document does not include architecutre discussion
08:23:52 <shigeya> futomi: is the title confusing
08:23:54 <shigeya> @2: yes.
08:24:10 <shigeya> futomi: Then, let’s change title.
08:24:24 <shigeya> … actually, this document documents requirements
08:25:02 <shigeya> kiyohsi: I think sec.2 includes architecture discussion, but just a observation on WBS
08:25:27 <shigeya> … in adition ITU-T is right place to discuss such kind of architecture
08:25:39 <whyun> whyun has joined #websigns
08:25:40 <shigeya> … next topic, we have collaboration issue
08:25:43 <miyoung> miyoung has joined #websigns
08:26:04 <shigeya> @2: so all three profile docuemnst has same issue.
08:26:29 <shigeya> futomi: let’s move onto next slot
08:26:36 <shigeya> … liaison with ITU
08:26:50 <shigeya> kiyoshi: at last TPAC. we got liaison letter from ITU-T.
08:27:03 <shigeya> … finally we replied to ITU-T.
08:27:17 <futomi> https://www.w3.org/community/websignage/wiki/images/c/c8/RLS.pdf
08:27:43 <shigeya> (kiyoshi describing the letter)
08:30:09 <shigeya> kiyoshi: we didn’t get the reply to this liaison letter, but ITU-T has intention to share.
08:30:21 <shigeya> … I want to ask @3@ to discuss
08:30:47 <shigeya> (Shin-Gak Kang  describing )
08:31:33 <shigeya> s/@2/sgkang/
08:32:11 <shigeya> sgkang: (Introduction  to SG16 Q14)
08:33:46 <kiyoshi> q?
08:39:25 <triblondon> triblondon has joined #websigns
08:40:38 <naomi> naomi has joined #websigns
08:41:09 <jay> q+
08:42:44 <shigeya> sgkang: (Technical paper on “Digital signage: web-based digital signage”, target date: 2017)
08:42:50 <naomi> naomi has joined #websigns
08:43:20 <shigeya> rrsagent, make minutes
08:43:20 <RRSAgent> I have made the request to generate http://www.w3.org/2016/09/22-websigns-minutes.html shigeya
08:45:12 <shigeya> kiyoshi: I have one issue for this slide. ITU-T discuss about some kind of web-runtime
08:45:37 <shigeya> … runtime on top of operation system.
08:47:39 <shigeya> q?
08:49:22 <shigeya> ack jay
08:49:58 <shigeya> jay: any crucial diffence between W3C and ITU-T? I think collaboration is great, but there are cruicial difference we need to understand
08:50:17 <shigeya> sgkang: this group focus  on web.
08:51:29 <shigeya> sgkang: we don’t want to develop same document. we can find cross collaboraiton
08:51:48 <shigeya> kiyoshi: on 15th page. This is one of the collaoboration item.
08:52:04 <shigeya> … hatano-san’s document is focusing on some of components.
08:52:17 <shigeya> … the figure shows overall architecture.
08:52:58 <shigeya> … just map profile document to ITU-document
08:53:15 <shigeya> … if our group have comment to ITU-T document, it will be a collaboration item.
08:53:19 <ajitomi> ajitomi has joined #websigns
08:53:26 <shigeya> sgkang: we have to update document accordingly.
08:54:29 <shigeya> futomi: How about liaison?
08:54:41 <shigeya> kiyoshi: currently with BG. how we can continue it?
08:54:52 <shigeya> sam: as long as BG continues that’s okay.
08:55:07 <shigeya> … in terms of WG, we have to restate relationship.
08:55:18 <shigeya> .. I have to double-check
08:55:39 <shigeya> futomi: CG and ITU-T can connect (collaborate?)
08:55:47 <shigeya> sam: i have to check.
08:56:11 <shigeya> kiyoshi: I mentioneed in the figure above.
08:56:38 <shigeya> futomi: in my opinion, DS client is part of runtime. but (for me) DS client is just a HTML5 application.
08:57:07 <shigeya> … we will develop new API between HTML5/applicaitonlayer and runtime layer
08:57:41 <shigeya> sgkang: we have to develop native applicaiton to support. If this group create API, we can use the API without developing native applicaiton.
08:58:14 <triblondon> triblondon has joined #websigns
08:58:30 <triblondon> q+
08:58:35 <shigeya> kiyoshi: there is OS+runtime box (connectd at right)
08:58:49 <shigeya> q+
09:00:08 <shigeya> ack triblondon
09:00:35 <shigeya> triblondon: I’m from TAG. so have preseonal interest.
09:01:01 <shigeya> … interest on crossing between this group and other W3C activities
09:01:10 <shigeya> … especially on Web Driver
09:03:24 <shigeya> … interested in how WBS group extend it’s scope (like controling sleep, such)
09:03:36 <shigeya> kiyoshi: havent’ decided yet. it’s part of on-going discussion.
09:04:19 <shigeya> … we want to more effective/attractive with ??-browser. may be some kind of management API useful for operator or some kind of web signage provider.
09:05:03 <shigeya> triblondon: this diagram is interesting for me too.
09:05:14 <shigeya> … it’s important to charter.
09:05:19 <kiyoshi> q?
09:05:21 <shigeya> ack shigeya
09:05:42 <sam> scribe: sam
09:06:02 <sam> shigeya: implimentation is platform dependant
09:06:24 <sam> ... we should have a figure we can share
09:07:05 <sam> ... we want to make a generic figure with specific wording.
09:07:36 <sam> ... W3C adn ITUT have different terminology
09:08:13 <shigeya> scribe: shigeya
09:08:30 <sam> s/adn/and/
09:09:26 <shigeya> kiyoshi: @5@ docuemnt is member only.
09:09:56 <shigeya> sgkang: we can update and provide if possible.
09:10:15 <shigeya> futomi: If it is difficult to open document to public, then we can use private mailng list?
09:10:23 <shigeya> kiyohsi: it’s ITU-T matter so not so simple.
09:10:37 <shigeya> s/kiyohsi:/kiyoshi:/
09:11:04 <shigeya> … tihis document is at same status as W3C document
09:11:49 <shigeya> osamu: it’s important check the relationship status. How to make good relatinship with ITU-T and W3C wrt web based signage.
09:12:10 <shigeya> … we got information of ITU-T (thanks!) then we should think how to collaborate.
09:12:26 <shigeya> kiyoshi: ITU-T don’t send document. we can request docuemts.
09:12:39 <jay> s/tihis/this/
09:12:42 <shigeya> … one option is request document to send from me .
09:13:30 <shigeya> sgkang: it’s depends on meeting in Dec. But for collaboration, and getting coments, it’s useful.
09:14:11 <shigeya> sgkang: (without approval, we can’t send document )
09:14:20 <shigeya> q?
09:14:43 <sangwhan> sangwhan has joined #websigns
09:14:53 <shigeya> futomi: next topic is charter.
09:15:03 <sam> scribe: sam
09:15:15 <shigeya> https://lists.w3.org/Archives/Public/public-websignage/2016Jul/0000.html
09:15:26 <sangwhan> rrsagent, draft minutes
09:15:26 <RRSAgent> I have made the request to generate http://www.w3.org/2016/09/22-websigns-minutes.html sangwhan
09:16:23 <sam> shigeya: please open the email on the link
09:17:00 <sam> ... we moved out document from google docs to github
09:17:11 <sangwhan> rrsagent, make logs world-visible
09:17:18 <sangwhan> rrsagent, draft minutes
09:17:18 <RRSAgent> I have made the request to generate http://www.w3.org/2016/09/22-websigns-minutes.html sangwhan
09:17:48 <sam> ... let me review what's happening
09:18:03 <sam> ... first draft last October
09:18:47 <sam> ... and continue to draft 5 at march 2016
09:19:28 <sam> ... sent W3M for intention to send the charter for AC Review
09:19:47 <sam> ... updated with W3M's requests
09:20:24 <sam> ... last fix#3 was made in June 1, 2016.
09:20:52 <sam> ... 3 issues
09:21:49 <sam> ... (explaining 3 issues described in the email)
09:24:07 <sam> ... I think the document are done at this point.
09:24:32 <sam> kiyoshi: last year we talked about which API we need
09:25:21 <shigeya> q?
09:25:24 <sam> ... finally we have draft charter
09:25:48 <sam> ... current charger is here
09:26:01 <shigeya> http://w3c.github.io/charter-drafts/web-based-signage-2016.html
09:26:29 <shigeya> scribe: shigeya
09:27:06 <shigeya> kiyoshi: (kiyoshi describing the draft charter)
09:29:29 <shigeya> sgkang: you mentioned DSC. Is that a external organization?
09:29:41 <shigeya> s/a external/an external/
09:30:16 <shigeya> kiyoshi: we included DSC as information source.
09:30:29 <kiyoshi> q?
09:30:36 <shigeya> futomi: (break till 11am)
09:41:12 <sam> sam has joined #websigns
09:56:58 <sangwhan> rrsagent, draft minutes
09:56:58 <RRSAgent> I have made the request to generate http://www.w3.org/2016/09/22-websigns-minutes.html sangwhan
09:57:04 <shigeya> shigeya has joined #websigns
10:00:35 <shigeya> futomi: next topic is introduciton to implementations.
10:00:45 <shigeya> futomi: first presenattion is by kiyoshi
10:01:49 <shigeya> https://www.w3.org/community/websignage/wiki/images/1/18/160922Web-based_Signage-NTT.pdf
10:02:06 <shigeya> (kiyoshi presents his slides)
10:03:36 <Zakim> Zakim has left &websigns
10:12:47 <sangwhan> sangwhan has changed the topic to: http://w3c.github.io/charter-drafts/web-based-signage-2016.html
10:14:39 <shigeya> shigeya has left #websigns
10:14:52 <shigeya> shigeya has joined #websigns
10:15:09 <jay> q+, to Kiyoshi on CUD
10:15:20 <jay> q?
10:15:24 <jay> q+
10:17:13 <shigeya> jay: one of the imporatant point is, universal design
10:17:20 <shigeya> … audience can be anybody
10:17:47 <shigeya> … one of the content shown is no color universal design in mind.
10:17:59 <shigeya> sangwhan: have you ever been to Japan? (joking)
10:18:35 <shigeya> kiyoshi: that’s very imporant point. this is just a example. maybe some kind of methods provoing foreingn people or desabled people must be supported.
10:18:54 <shigeya> … we at NTT, some people working on universal design, so we can make use of it.
10:18:59 <shigeya> q?
10:19:02 <shigeya> ack jay
10:19:32 <ajitomi> ajitomi has joined #websigns
10:19:48 <shigeya> sgkang: on “web based content”: there are several applications. last one. what is… use cases? what is the point?
10:20:44 <shigeya> kiyoshi: i want to comment on.. we can use other services already deployed on internet or cloud. requirement of cthe content for such kind of language translation is normal usecase for foreign people. but webbased content is a also a web content, so that we can use such kind of services
10:20:59 <shigeya> .. if we can use such kind of services inexpensively.
10:21:16 <shigeya> futomi: next, my turn.
10:21:55 <shigeya> https://www.w3.org/community/websignage/wiki/images/b/bb/TPAC2016_WBS_BG_f2f_Newphoria_Introduction_of_Web-based_Signage_JS_Player.pdf
10:22:01 <shigeya> (presenting his slides)
10:22:12 <shigeya> s/(presenting/(futomi presenting
10:23:15 <shigeya> http://www.applican.com
10:32:20 <triblondon> triblondon has joined #websigns
10:33:18 <kiyoshi> q?
10:33:23 <kiyoshi> q+
10:34:57 <sangwhan> s/introduciton to/introductions of/
10:36:30 <shigeya> q?
10:36:37 <shigeya> ack kiyoshi
10:37:02 <shigeya> kiyoshi: Futomi shown some ideas of APIs.
10:37:41 <shigeya> … we want to consider API as new proposal
10:38:08 <shigeya> kgkang: regarding display setting, how about getting display information?
10:38:37 <shigeya> … resolution, physical information can be.
10:38:52 <kiyoshi> s/new proposal/detailed proposal for existing/
10:39:11 <shigeya> q+
10:39:31 <shigeya> ack shigeya
10:39:44 <igarashi> igarashi has joined #websigns
10:40:28 <sam> shigeya: I think our charter and Futomi's API is different
10:40:35 <sam> scribe sam
10:40:52 <sam> ... do you want to modify or add new one.
10:42:02 <sam> kiyoshi: we discuss this in the afternoon
10:42:18 <shigeya> scribe: shigeya
10:42:33 <shigeya> @5: on slide 4, why you need such information?
10:42:57 <shigeya> futomi: it’s related universal plug-and-play. For exapmle, model number is not known to users. Our consumers know friendly name.
10:43:09 <kiyoshi> s/slide 4/slide 14/
10:43:13 <shigeya> … For example, sony bravia 42 is a friendly name.
10:43:26 <shigeya> … but operator want to know both inforamtion.
10:43:37 <shigeya> … many TV sets have both friendly and model number.
10:43:50 <shigeya> q?
10:45:20 <shigeya> (Jihye Hong, LG, presenting her slides)
10:45:43 <shigeya> “use cases in LG webOS Signage”
10:50:33 <shigeya> jihye: on multiple screen, using WebSocket, one of the display acts as master. using master-slave model.
10:55:51 <jay> q+
10:55:52 <shigeya> q?
10:55:58 <shigeya> ack jay
10:56:40 <shigeya> jay: my understanding is, webOS is propriaetary OS. If so, why you need to standardize it.
10:57:01 <shigeya> jihye: we prefer to use standardized API.
10:57:22 <shigeya> jay: do you have any plan to publish part of the implementation?
10:57:22 <sangwhan> http://www.openwebosproject.org
10:57:34 <shigeya> jihye: webOS is open sourced.
10:58:00 <shigeya> osamu: This seems imporant for multi-display setting.
10:58:39 <shigeya> … message passing with WebSocket. Do you have any desigin thoughts on contents manager and display?
10:58:54 <sangwhan> q+
10:59:06 <shigeya> jihye: we’re using controller to handle multiple signage
10:59:46 <shigeya> igarashi: JavaScript using websocket to sync or not? or webOS?
10:59:50 <shigeya> jihye: webOS
11:00:08 <shigeya> igarashi: what’s the role of the API?
11:00:36 <shigeya> jihye: API assigned display IDs and position. webOS then controls it.
11:00:44 <shigeya> q?
11:01:12 <shigeya> kiyoshi: do you consider to implement multi-screen std?
11:01:48 <kiyoshi> q?
11:02:02 <shigeya> igarashi: do you have interest to integrate the spec to multiscreen?
11:02:10 <shigeya> @6: yes (?)
11:02:13 <shigeya> q?
11:02:24 <shigeya> ack sangwhan
11:02:38 <shigeya> sangwhan: on last two presentations. two things are not in charter.
11:02:53 <shigeya> … display control. chater has power but not display bits.
11:03:11 <shigeya> … hatano-san mentioned NTP, how about video-sync?
11:03:32 <shigeya> futomi: my implementation works at 100ms order
11:03:41 <sam> s/@6/Hyojin/
11:03:51 <shigeya> sangwhan: there was a CG atlking about synchronization
11:04:00 <shigeya> s/atlking/talking/
11:04:18 <shigeya> … using multicast. every screen tunes into…
11:04:42 <shigeya> (sangwhan drawing)
11:05:05 <shigeya> sangwhan: there is many ways to solve it.
11:05:30 <shigeya> igrashi: LG’s solution is syncing by webOS
11:05:43 <shigeya> … possibly the sync technology itself should be standardized...
11:06:13 <shigeya> … possibly making use of CSS
11:06:34 <shigeya> sangwhan: having two clocks are bizarre
11:06:55 <shigeya> igarashi: we want to talk just about clock or synchornization techonology?
11:07:48 <shigeya> sangwhan: there is techology called PTP.
11:08:48 <shigeya> q?
11:09:03 <shigeya> osamu: we should undestand how to handle multiple display.
11:09:21 <shigeya> … single OS manage display. there is several scheme to handle multi screen.
11:09:53 <shigeya> sangwhan: LG has implmeentation. since standardization require implementation, thus it’s good.
11:10:14 <shigeya> osamu: SONY has another technology?
11:10:33 <shigeya> igarashi: we have, but whether we can standardize or not unkonwn.
11:10:54 <shigeya> … how the display know the source of the video?
11:11:00 <shigeya> s/unkonwn/unknown/
11:11:38 <shigeya> jihye: same video to each signage. each signage know its position and clip it.
11:11:55 <shigeya> igarashi: how that the JavaScript should set HTML video?
11:12:13 <shigeya> … what kind of HTML source used?
11:13:43 <shigeya> (all videos configured to each of display)
11:14:20 <shigeya> igarashi: whether we can standardize is another discussion.
11:14:52 <shigeya> sangwhan: if worker swapped the display, it will not work…
11:15:02 <shigeya> s/the display/two displays/
11:15:27 <shigeya> futomi: it’s lunch time.
11:16:39 <shigeya> (Toshihiko Yamakami, ACCESS presents slides)
11:16:49 <shigeya> https://www.w3.org/community/websignage/wiki/images/6/6a/ACCESS_web-based_signage_introduction.pdf
11:19:10 <shigeya> osamu: we’re disucssing standardization. Can ACCESS contribute to it?
11:19:17 <shigeya> yamakami: Yes.
11:19:26 <shigeya> ???: is it based on Chromium?
11:19:50 <shigeya> yamakami: we have several implementaiton. I don’t know which one.
11:20:38 <sangwhan> s/???/sangwhan/
11:20:49 <sangwhan> rrsagent, draft minutes
11:20:49 <RRSAgent> I have made the request to generate http://www.w3.org/2016/09/22-websigns-minutes.html sangwhan
11:20:51 <shigeya> luch time. next slot starts at 13:15pm
11:21:05 <kiyoshi> Q?
11:23:24 <shigeya> shigeya has joined #websigns
11:32:56 <triblondon> triblondon has joined #websigns
11:34:27 <shigeya> shigeya has joined #websigns
11:35:40 <triblondon__> triblondon__ has joined #websigns
11:47:51 <shigeya> shigeya has joined #websigns
11:55:08 <naomi> naomi has joined #websigns
11:57:16 <naomi> naomi has joined #websigns
11:58:52 <shigeya> shigeya has joined #websigns
12:05:14 <sam> sam has joined #websigns
12:10:31 <shigeya> shigeya has joined #websigns
12:18:23 <kiyoshi__> kiyoshi__ has joined #websigns
12:20:36 <shigeya> (resuming at 13:20pm)
12:20:50 <shigeya> futomi: next presentation is by sgkang.
12:21:11 <jay> jay has joined #websigns
12:21:12 <shigeya> https://www.w3.org/community/websignage/wiki/images/8/8e/TTA.pdf
12:21:27 <shigeya> (sgkang presenting his slides)
12:21:54 <shigeya> “Standardization of Digital Signage Service Platform based on HTML5 in TTA”
12:22:11 <shigeya> TTA = Telecommunications Technology Association
12:24:33 <shigeya> igarashi: in case of Samsung Smart, do they use HTML5?
12:24:42 <shigeya> sgkang: their own solution (not tizeng)
12:24:48 <shigeya> s/tizeng/tizen
12:25:10 <shigeya> … they provide SDK
12:25:17 <shigeya> igrashi: their own OS?
12:25:24 <shigeya> sgkang: based on Android
12:26:25 <shigeya> futomi: is digitalsignage.com korean compnay?
12:26:28 <shigeya> sgkang: no
12:26:43 <shigeya> s/korean/a Korean/
12:29:09 <futomi> futomi has joined #websigns
12:29:34 <shigeya> q?
12:30:19 <jay> q+ on interoperability
12:39:15 <shigeya> q?
12:39:23 <shigeya> ack jay
12:39:23 <Zakim> jay, you wanted to comment on interoperability
12:39:35 <shigeya> jay: I have question on interoperability.
12:40:31 <shigeya> jay: what kind of service require interoperability?
12:42:31 <shigeya> sgkang: They’re using proprietary solution, but if stndard exists, they’ll adopt them.
12:42:50 <shigeya> igarashi: If it is not secret, how many companies attending TTA?
12:44:07 <shigeya> sgkang: 10 SMEs.
12:44:49 <shigeya> (SME = Small and Medium Enterprises)
12:45:48 <shigeya> jay: is there any requirement by Korea government to show alert or emergency (notificiation) ? are there such?
12:46:20 <shigeya> sgkang: yes.
12:46:24 <shigeya> q?
12:46:35 <shigeya> igarashi: Is current spec public?
12:46:42 <shigeya> sgkang: just open to TTA members.
12:47:21 <shigeya> igarashi: is there possibilty to have a liaison to make these documents avaiable for us?
12:47:29 <shigeya> sgkang: I will check.
12:48:56 <shigeya> Topic: Review of the Web-based Signage WG Charter document
12:49:30 <shigeya> futomi: In this slot, we will discuss what kind of APIs we want to develop and who will edit the spec.
12:49:49 <shigeya> … currently, charter draft describes three categories.
12:50:10 <shigeya> … today I propose four APIs in Other Contextual Information category.
12:51:05 <shigeya> kiyoshi: to drafting API specs, we need three things: 1) use case,  2) feature , 3) gap analysis
12:51:16 <shigeya> … we want to start with use cases?
12:52:33 <shigeya> kiyoshi: in the morning, we have shown various APIs needed.
12:54:09 <futomi> 1 Power Management  2 Remote Prompting  3 Other Contextual Information   3-1 Device Information API   3-2 Network Information API   3-3 Display Setting API   3-4 NTP Server Setting API
12:54:56 <shigeya> futomi: It is clear to include 1, 3-1, 3-2, 3-3, 3-4 in the charter
12:55:39 <shigeya> … for me, 3-1 and 3-2 has priority. If no one has interest 3-3 and 3-4, we may want to delete them.
12:55:49 <jihye> q?
12:56:45 <shigeya> futomi: I think 3-4 and 3-4 is not essential according to my experience.
12:56:53 <shigeya> s/is not/are not/
12:57:07 <shigeya> kiyoshi: this group want to decide prioirity
12:57:15 <shigeya> s/prioirity/priority/
12:58:24 <shigeya> sgkang: any relationship between 1 and 3-3?
12:58:58 <shigeya> futomi: (power) status of display and controller is different.
12:59:25 <shigeya> s/controller/terminal/
13:00:47 <shigeya> sgkang: there different menanings of power management.
13:01:06 <shigeya> igarashi: Is there any explanation of the API?
13:01:26 <shigeya> futomi: All of panel includes OS and LCD and speaker or whatever.
13:02:32 <shigeya> igarashi: Have to describe in detail.
13:02:43 <kawai> kawai has joined #websigns
13:02:53 <shigeya> Igarashi: adding the short description ot each API might be useful.
13:03:55 <sam> scribe: sam
13:04:18 <sam> shigeya: what is OS mean in this context?
13:04:59 <sam> ... maybe device.
13:05:25 <shigeya> scribe: shigeya
13:06:41 <shigeya> kiyoshi: power management might be not good word here…
13:07:18 <triblondon__> triblondon__ has joined #websigns
13:07:56 <shigeya> (discussing on “Power Managent API” title and description)
13:08:51 <shigeya> jihye: display backlight control also.
13:09:10 <shigeya> q?
13:10:08 <shigeya> igarashi: control the luminance of display screen
13:10:31 <shigeya> … it’s a dimmer
13:11:03 <shigeya> … its not a level of brightness
13:12:32 <shigeya> jay: we should not discuss details. we need to discuss concept for API requirement.
13:12:59 <shigeya> … scheduling or rebooting is kind of OS control. it is easy to mix into powre management. We have to disucss at high-level APIs.
13:13:27 <shigeya> igarashi: my suggestion is list up first, and decide whether it is suitable or not later.
13:14:15 <shigeya> jay: we’re not in brainstorming time.
13:14:51 <shigeya> sgkang: we need rebooting, power (consolidating) something.
13:18:04 <shigeya> … rebooting is in power management. I’m not sure on display (setting or control).
13:18:46 <shigeya> igarashi: list and discuss later is a good strategy.
13:19:05 <shigeya> … targe is finishing this all APIs till tomorrow?
13:19:09 <shigeya> futomi: yes.
13:19:43 <shigeya> … my idea is we will gather everybody’s idea, tomorrow, we will discuss again.
13:20:08 <shigeya> … could you give us idea on APIs?
13:20:19 <shigeya> igarashi: Not just about power management, any APIs?
13:20:39 <shigeya> futomi: I think 3 is good enough.
13:20:55 <shigeya> … if you have any idea, I’d like to hear.
13:21:05 <shigeya> … current draft includes device info?
13:21:38 <shigeya> s/… current drat includes device info?/igarashi: current drat includes device info?
13:22:05 <shigeya> igarashi: only about query information, right?
13:22:47 <shigeya> (3-2 now includes items from Futomi’s presentation)
13:22:59 <naomi> naomi has joined #websigns
13:23:40 <shigeya> igarashi: Let’s discuss on device information API
13:24:05 <shigeya> kiyoshi: How do we use this APIs?
13:24:24 <shigeya> futomi: by administrators
13:24:42 <shigeya> igarashi: for what purpose?
13:24:53 <shigeya> futomi: what type of hardware adminstrator have to know.
13:25:03 <shigeya> igarashi: what they do once they know the info?
13:25:53 <shigeya> futomi: I want to know the location of the terminal, and name (type) of terminal.
13:26:18 <shigeya> kiyoshi: we give each terminal a number.
13:26:42 <shigeya> igarashi: pelase describe the situation, not how it is good or not
13:26:59 <shigeya> futomi: mainly, seriail number used for access control to cloud.
13:27:18 <shigeya> igarashi: another example is physical screen size. need it?
13:27:23 <shigeya> futomi: it’s useful information.
13:28:19 <shigeya> … terminal specic information.
13:28:33 <shigeya> kiyoshi: once get it, after that, we keep it in CMS?
13:28:45 <shigeya> … just get
13:28:46 <shigeya> q+
13:29:15 <sam> scribe: sam
13:29:47 <sam> shigeya: maybe serial number is just good enough
13:29:56 <jay> there are two kinds of info: informative and normative
13:30:37 <sam> ... we should know which information is crutial
13:31:03 <sam> futomi: some redundant info is useful for developer
13:31:09 <jay> q+
13:32:01 <jay> ack shigeya
13:32:04 <sam> shigeya: we shoud reduce down to reasonable information.
13:32:28 <sam> igarashi: info for human not for machine
13:32:51 <shigeya> q?
13:33:32 <sam> futomi: same as network management. we need all info possible.
13:34:34 <shigeya> jay: informative information is useful. In the case of operation, maybe we only need the location of the device and resolution or height or power requirement, such a metadata is required by the operaiton.
13:34:50 <shigeya> … so in the sense of operation, API should limit to normative meta data
13:34:52 <shigeya> scribe: shigeya
13:35:09 <shigeya> … we have to distinguish them.
13:35:16 <igarashi> igarashi has joined #websigns
13:35:59 <shigeya> igrashi: we’re talking about device information.
13:36:47 <shigeya> sgkang: we need info on remote management.
13:36:57 <shigeya> q+
13:37:18 <jay> ack jay
13:38:12 <kiyoshi__> q?
13:38:48 <sam> scribe: sensor info is different from device info.
13:38:58 <sam> scribe: sam
13:39:10 <shigeya> ack shigeya
13:39:13 <sam> shigeya: sensor info is different from device info.
13:39:19 <shigeya> scribe: shigeya
13:39:36 <shigeya> igarashi: how these sensor information is useful?
13:39:39 <sam> s/scribe: sensor info is different from device info.//
13:39:50 <shigeya> osamu: changing contents according to sensors
13:40:11 <shigeya> jihye: proximity sensor is useful for...
13:40:42 <shigeya> … changing display according to the distance.
13:40:47 <shigeya> q?
13:42:55 <shigeya> (adding sensing and ambient)
13:43:41 <shigeya> kiyoshi: on 3-1: original four items: serial number, manufacturer name, model number, friendly name
13:43:41 <sam> rrsagent, make minutes
13:43:41 <RRSAgent> I have made the request to generate http://www.w3.org/2016/09/22-websigns-minutes.html sam
13:45:50 <sam> shigeya: maybe more info for diagnosing
13:46:06 <sam> ... we can adjust items here.
13:46:13 <shigeya> scribe: shigeya
13:46:26 <shigeya> futomi: on 3-3
13:46:39 <shigeya> kiyoshi: we have discussed about dimmer.
13:46:54 <shigeya> igarashi: how about color space control?
13:47:53 <olivexu> olivexu has joined #websigns
13:48:00 <jay> is the same concept of network information API with http://wicg.github.io/netinfo/
13:48:58 <shigeya> kiyoshi: on remote prompting
13:49:56 <shigeya> @9: I thikn it’s related for on signage. Use like alert show dialog. so, then, you can’t control it anymore.
13:50:22 <shigeya> … I think for digital signage, it is imporant to change behavior. As synchronized operation.
13:50:41 <shigeya> … Now for mobile browser, browser shows dialog.
13:51:03 <shigeya> … may be you need to this alert or message alert box invoked on this screen to your management function.
13:51:20 <shigeya> … but the question is, if the funciton does make sens.
13:51:50 <shigeya> … other way is documentaing practices.
13:52:18 <shigeya> … (asynchronous vs synchronous)
13:53:07 <shigeya> … at second secreen WG, there are two APIs presentation APIs and (…)
13:53:13 <sam> s/@9/Fraunhofer/
13:54:08 <jihye> @9/louay
13:54:09 <shigeya> … Goal of presentation API is open in browser and launch on other screen.
13:54:29 <shigeya> … (like chromecast)
13:54:59 <shigeya> … goal of this API is standardization
13:55:37 <sam> s/Fraunhofer/Louay of Fraunhofer/
13:56:34 <shigeya> … other implementaiton might use smartphone screen bound by NFCs.
13:57:04 <shigeya> igarashi: in case of use of Presntation API…
13:58:09 <shigeya> louay: presentation API initiated by (for example) smart phone, then connect to large screen.
13:59:09 <shigeya> …presentation API requiers both devices on same network.
14:00:31 <shigeya> igarashi: Will we mention relationship?
14:01:16 <shigeya> … we might need guidelines how to use this kind of APIs.
14:02:27 <shigeya> kiyoshi: we must consider relationship
14:05:17 <shigeya> We resume our meeting 9am tomorrow morning
14:05:36 <sam> rragent, make minutes
14:05:46 <sam> rrsagenet, make minutes
14:06:00 <sam> rrsagent, make minutes
14:06:00 <RRSAgent> I have made the request to generate http://www.w3.org/2016/09/22-websigns-minutes.html sam
14:06:21 <sam> trackbot, end meeting
14:07:44 <shigeya> shigeya has joined #websigns
14:11:01 <shigeya> shigeya has joined #websigns
14:12:43 <shigeya> shigeya has joined #websigns
14:13:35 <jay_> jay_ has joined #websigns
14:39:39 <olivexu> olivexu has joined #websigns
14:45:57 <sam> sam has joined #websigns
15:07:43 <naomi> naomi has joined #websigns
15:24:56 <kawai> kawai has joined #websigns
15:31:20 <shigeya> shigeya has joined #websigns
15:43:21 <Zakim> Zakim has left #websigns
15:46:52 <shigeya> shigeya has joined #websigns
15:48:30 <shigeya> shigeya has joined #websigns
16:38:48 <naomi> naomi has joined #websigns
16:39:37 <naomi> naomi has joined #websigns
17:14:05 <shigeya> shigeya has joined #websigns
17:14:31 <shigeya> shigeya has joined #websigns
21:14:23 <sam> sam has joined #websigns
21:19:01 <shigeya> shigeya has joined #websigns