IRC log of webtv on 2014-05-28

Timestamps are in UTC.

13:00:20 [RRSAgent]

RRSAgent has joined #webtv

13:00:20 [RRSAgent]

logging to http://www.w3.org/2014/05/28-webtv-irc

13:00:25 [kaz]

zakim, this will be tv

13:00:25 [Zakim]

ok, kaz, I see UW_WebTVIG()9:00AM already started

13:00:29 [kaz]

zakim, call kazuyuki-617

13:00:30 [Zakim]

ok, kaz; the call is being made

13:00:30 [Zakim]

+ +49.303.aabb

13:00:30 [Zakim]

+Kazuyuki

13:00:34 [Zakim]

-??P16

13:00:52 [kaz]

zakim, who is here?

13:00:52 [Zakim]

On the phone I see +1.650.946.aaaa, +49.303.aabb, Kazuyuki

13:00:54 [Zakim]

On IRC I see RRSAgent, Zakim, yosuke, ddavis, Bin_Hu, PaulHiggs, aldafu, kaz, jcverdie, schuki, timeless_, tobie_, MarkS, trackbot

13:00:55 [PaulHiggs]

zakim, call PaulHiggs

13:00:55 [Zakim]

I am sorry, PaulHiggs; I do not know a number for PaulHiggs

13:01:06 [Bin_Hu]

zakim, aaaa is me

13:01:06 [Zakim]

+Bin_Hu; got it

13:01:08 [kaz]

zakim, aabb is Alex

13:01:08 [Zakim]

+Alex; got it

13:01:12 [kaz]

zakim, who is here?

13:01:12 [Zakim]

On the phone I see Bin_Hu, Alex, Kazuyuki

13:01:14 [Zakim]

On IRC I see RRSAgent, Zakim, yosuke, ddavis, Bin_Hu, PaulHiggs, aldafu, kaz, jcverdie, schuki, timeless_, tobie_, MarkS, trackbot

13:01:23 [Zakim]

+[IPcaller]

13:01:31 [Zakim]

+??P18

13:01:34 [ddavis]

zakim, ??P18 is me

13:01:34 [Zakim]

+ddavis; got it

13:01:48 [Zakim]

+Paul_Higgs

13:01:49 [kaz]

zakim, IPcaller is yosuke

13:01:50 [Zakim]

+yosuke; got it

13:01:51 [Zakim]

+Jean-Charles

13:02:04 [kaz]

zakim, who is here?

13:02:04 [Zakim]

On the phone I see Bin_Hu, Alex, Kazuyuki, yosuke, ddavis, Paul_Higgs, Jean-Charles

13:02:06 [Zakim]

On IRC I see RRSAgent, Zakim, yosuke, ddavis, Bin_Hu, PaulHiggs, aldafu, kaz, jcverdie, schuki, timeless_, tobie_, MarkS, trackbot

13:02:07 [PaulHiggs]

thanks, just checking

13:02:16 [Zakim]

+gmandyam

13:02:45 [gmandyam]

gmandyam has joined #webtv

13:03:03 [jcverdie]

zakim, jcverdie is Jean-Charles

13:03:04 [Zakim]

sorry, jcverdie, I do not recognize a party named 'jcverdie'

13:03:15 [kaz]

zakim, who is here?

13:03:15 [Zakim]

On the phone I see Bin_Hu, Alex, Kazuyuki, yosuke, ddavis, Paul_Higgs, Jean-Charles, gmandyam

13:03:17 [Zakim]

On IRC I see gmandyam, RRSAgent, Zakim, yosuke, ddavis, Bin_Hu, PaulHiggs, aldafu, kaz, jcverdie, schuki, timeless_, tobie_, MarkS, trackbot

13:03:34 [wuwei]

wuwei has joined #webtv

13:04:11 [kaz]

zakim, Jean-Charles is jcverdie

13:04:11 [Zakim]

+jcverdie; got it

13:04:51 [wuwei]

zakim, code?

13:04:52 [Zakim]

the conference code is 932881 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), wuwei

13:05:00 [kaz]

zakim, who is here?

13:05:00 [Zakim]

On the phone I see Bin_Hu, Alex, Kazuyuki, yosuke, ddavis, Paul_Higgs, jcverdie, gmandyam

13:05:03 [Zakim]

On IRC I see wuwei, gmandyam, RRSAgent, Zakim, yosuke, ddavis, Bin_Hu, PaulHiggs, aldafu, kaz, jcverdie, schuki, timeless_, tobie_, MarkS, trackbot

13:05:24 [Zakim]

+EricP

13:05:42 [kaz]

zakim, EricP is Wu_Wei

13:05:42 [Zakim]

+Wu_Wei; got it

13:05:43 [ddavis]

Meeting: Web and TV IG call

13:05:46 [ddavis]

Scribe: Daniel

13:05:50 [ddavis]

scribenick: ddavis

13:05:57 [kaz]

zakim, Wu_Wei is wuwei

13:05:57 [Zakim]

+wuwei; got it

13:05:58 [ddavis]

chair: Yosuke

13:06:04 [yosuke]

http://www.w3.org/2011/webtv/wiki/New_Ideas

13:06:07 [ddavis]

Topic: Use-case gathering

13:06:43 [kaz]

Agenda: http://lists.w3.org/Archives/Public/public-web-and-tv/2014May/0010.html

13:07:15 [kaz]

rrsagent, make log public

13:07:17 [ddavis]

yosuke: So there are some use cases from IG members and several concerning accessibility.

13:07:20 [kaz]

rrsagent, draft minutes

13:07:20 [RRSAgent]

I have made the request to generate http://www.w3.org/2014/05/28-webtv-minutes.html kaz

13:07:41 [ddavis]

yosuke: So going through the wiki page...

13:07:50 [ddavis]

yosuke: First use-case is audio fingerprinting.

13:07:55 [kaz]

scribenick: kaz

13:08:18 [kaz]

topic: Audio Fingerprinting (watermarking) - Daniel

13:08:43 [kaz]

-> https://www.w3.org/2011/webtv/wiki/New_Ideas#Audio_Fingerprinting_.28watermarking.29 UC1

13:08:57 [kaz]

ddavis: there was ATSC proposal on this

13:09:42 [kaz]

s/there was ATSC proposal/ATSC asked about proposal/

13:10:09 [kaz]

... Facebook has announced they're adding watermarking capability to their mobile apps

13:10:13 [gmandyam]

q+

13:10:36 [kaz]

gmandyam: uncertain about what to do...

13:10:43 [kaz]

ack g

13:11:21 [kaz]

ddavis: would add clarification

13:11:26 [kaz]

gmandyam: great

13:11:43 [kaz]

s/gmandyam:/paul:/g

13:11:58 [kaz]

q+ gmandyam

13:12:02 [kaz]

ack g

13:12:21 [kaz]

gmandyam: video watermark and audio watermark

13:12:46 [kaz]

... audio fingerprinting for location identification, etc.

13:13:03 [wuwei]

wuwei has joined #webtv

13:13:19 [jcverdie]

q+

13:13:31 [kaz]

... think video watermarking is the description here

13:13:42 [kaz]

s/is/fits/

13:13:53 [wuwei]

wuwei has joined #webtv

13:14:29 [kaz]

zakim, who is speaking?

13:14:39 [Zakim]

kaz, listening for 10 seconds I heard sound from the following: ddavis (38%), Paul_Higgs (93%), gmandyam (24%)

13:14:44 [wwu]

wwu has joined #webtv

13:14:59 [kaz]

paul: what do you mean by "video watermarking" and "audio watermarking"?

13:15:10 [kaz]

... microphone to content recognition

13:15:29 [wwu]

wwu has joined #webtv

13:16:03 [kaz]

ddavis: maybe there are two separate use cases here

13:16:07 [kaz]

yosuke: agree

13:16:14 [wwu]

wwu has joined #webtv

13:16:17 [jcverdie]

q?

13:16:32 [kaz]

ddavis: would split them then

13:17:08 [wwu]

wwu has joined #webtv

13:17:15 [kaz]

jcverdie: concerned about patents

13:17:42 [kaz]

ddavis: thought about that...

13:17:47 [gmandyam]

Just to clarify: The ATSC put out a call-for-proposals for watermarking video/audio with an embedded low rate data channel (around 1 kbps), where the user device could extract information in the broadcast feed to retrieve additional data related to the content being played.

13:17:59 [kaz]

paul: this is more about APIs

13:18:33 [kaz]

ddavis: need to investigate

13:18:52 [kaz]

paul: EME also has APIs for content protection

13:19:07 [kaz]

... may be related to patents

13:19:16 [kaz]

ddavis: EME itself is an exception

13:19:53 [jcverdie]

q?

13:19:55 [jcverdie]

ack me

13:20:02 [kaz]

ddavis: would investigate that point

13:20:16 [kaz]

topic: Media playback adjustment

13:20:25 [kaz]

s/adjustment/adjustment - Daniel/

13:20:43 [kaz]

ddavis: adjust media playback speed, etc.

13:20:51 [PaulHiggs]

<video> can change speed

13:21:01 [PaulHiggs]

but audio is likely to be muted

13:21:45 [kaz]

yosuke: thinks this feature is important for broadcasting service

13:21:54 [kaz]

... any other questions?

13:21:56 [yosuke]

q?

13:22:13 [kaz]

aldafu: playback rate for video

13:22:28 [kaz]

... possible to do it

13:22:34 [kaz]

ddavis: but audio may be muted

13:22:43 [kaz]

q+

13:23:01 [kaz]

ack k

13:23:07 [ddavis]

scribenick: ddavis

13:23:53 [ddavis]

kaz: When we investigate this, maybe we can consider extending it, e.g. for Japanese videos - if we try to playback at a higher speed, the player can play the video and sound faster and the speech sound is played back at the original frequency.

13:24:22 [ddavis]

kaz: So there's a special speech playback technology. The sound is not muted and the sound quality is not changed.

13:24:34 [ddavis]

yosuke: I think modern VCRs have similar functions.

13:25:01 [ddavis]

yosuke: So when we playback with double speed the voice may be high-pitched, which we don't want.

13:25:20 [PaulHiggs]

how does the re-sync occur?

13:25:23 [aldafu]

ddavis: check http://www.w3.org/2010/05/video/mediaevents.html

13:25:24 [ddavis]

yosuke: If the HTML5 media element doesn't have that function, it's worth considering.

13:25:37 [aldafu]

ddavis: you can actually control playback rate and audio goes along for me

13:25:58 [yosuke]

q?

13:26:17 [aldafu]

ddavis: not really, it becomes pretty warped

13:26:26 [kaz]

s/ddavis: you can/ddavis, you can/

13:26:49 [aldafu]

aldafu has left #webtv

13:27:01 [aldafu]

aldafu has joined #webtv

13:27:13 [kaz]

[some smart recorder has a capability of preserver the audio pitch]

13:27:21 [kaz]

s/ddavis: not/ddavis, not/

13:27:36 [wuwei1]

wuwei1 has joined #webtv

13:28:19 [kaz]

rrsagent, draft minutes

13:28:19 [RRSAgent]

I have made the request to generate http://www.w3.org/2014/05/28-webtv-minutes.html kaz

13:28:36 [kaz]

zakim, who is here?

13:28:36 [Zakim]

On the phone I see Bin_Hu, Alex, Kazuyuki, yosuke, ddavis, Paul_Higgs, jcverdie, gmandyam, wuwei

13:28:38 [PaulHiggs]

there are several industry initiatives on screen synchronization

13:28:39 [Zakim]

On IRC I see wuwei1, aldafu, gmandyam, RRSAgent, Zakim, yosuke, ddavis, Bin_Hu, PaulHiggs, kaz, jcverdie, schuki, timeless_, tobie_, MarkS, trackbot

13:28:49 [ddavis]

yosuke: Using watermarking can take time so it may not work.

13:29:30 [kaz]

Present: Bin, Alex, Kaz, Yosuke, Daniel, Paul, JC, Giri, Wu

13:29:43 [ddavis]

PaulHiggs: There are a few other industry organisations looking at synchronising streams - AKA screen synchronisation or companion device synchronisation.

13:30:02 [ddavis]

yosuke: This use case has some new perspective.

13:30:52 [ddavis]

yosuke: The broadcasting industry is syncing a broadcast stream and video, whereas this use case is about syncing two videos.

13:31:31 [ddavis]

PaulHiggs: I read a couple of things in this - there's multi-camera angle synchronisation and multi-video synchronisation.

13:31:51 [kaz]

kaz has joined #webtv

13:32:29 [ddavis]

PaulHiggs: It could be 2.5 use cases. The multi-angle one could be on the same device or separate devices.

13:33:01 [ddavis]

ACTION: ddavis to clarify use case 1 description

13:33:01 [trackbot]

Created ACTION-194 - Clarify use case 1 description [on Daniel Davis - due 2014-06-04].

13:33:02 [yosuke]

q?

13:33:18 [ddavis]

ACTION: ddavis to check current ability to change playback rate for HTML media element.

13:33:18 [trackbot]

Created ACTION-195 - Check current ability to change playback rate for html media element. [on Daniel Davis - due 2014-06-04].

13:33:35 [ddavis]

ACTION: ddavis to split synchronisation use case (#4)

13:33:35 [trackbot]

Created ACTION-196 - Split synchronisation use case (#4) [on Daniel Davis - due 2014-06-04].

13:33:44 [ddavis]

yosuke: Bin, could you explain use case 4 please?

13:34:21 [ddavis]

Bin_Hu: When you watch TV, based on the service provider you'll be provided with an overlay showing the promotion of another channel, for example.

13:34:31 [kaz]

i/yosuke: Bin,/topic: Triggered Interactive Overlay/

13:34:41 [ddavis]

Bin_Hu: The content is triggered by content in the main stream.

13:34:57 [ddavis]

Bin_Hu: There are a few requirements that can be extracted from this.

13:35:00 [kaz]

i|yosuke: Bin,|-> https://www.w3.org/2011/webtv/wiki/New_Ideas#Triggered_Interactive_Overlay Triggered Interactive Overlay UC|

13:35:06 [kaz]

rrsagent, draft minutes

13:35:06 [RRSAgent]

I have made the request to generate http://www.w3.org/2014/05/28-webtv-minutes.html kaz

13:35:30 [ddavis]

Bin_Hu: So the trigger could be within the stream, or it could be within the platform and associated with a channel.

13:35:51 [kaz]

kaz has joined #webtv

13:36:03 [ddavis]

Bin_Hu: Also, you may be viewing a baseball game, for example, and there could be a trigger that shows an overlay.

13:36:15 [ddavis]

Bin_Hu: This overlay could show a different team.

13:36:36 [ddavis]

Bin_Hu: These overlays must be valid during that 15 or 30 seconds.

13:37:01 [ddavis]

Bin_Hu: Or it could be triggered by a particular actor in the content.

13:37:16 [PaulHiggs]

can you clarify why this only applies to a "Hybrid STB"?

13:37:19 [ddavis]

Bin_Hu: This trigger must be technology-agnostic.

13:38:04 [kaz]

i|Using watermarking can|topic: Media stream synchronization|

13:38:10 [PaulHiggs]

HbbTV and MPEG DASH already provide "standardized" events

13:38:36 [ddavis]

Bin_Hu: HTML5 may be enhanced by added event types to support these different triggers.

13:38:44 [kaz]

i|Using watermarking can|-> https://www.w3.org/2011/webtv/wiki/New_Ideas#Media_stream_synchronization Media Stream Synchronization|

13:38:46 [kaz]

rrsagent, draft minutes

13:38:46 [RRSAgent]

I have made the request to generate http://www.w3.org/2014/05/28-webtv-minutes.html kaz

13:39:32 [ddavis]

Bin_Hu: On the other hand, in HTML5 there may be some other ways, specifically in specs for the TV industry.

13:39:50 [kaz]

i|adjust media playback speed,|-> https://www.w3.org/2011/webtv/wiki/New_Ideas#Media_playback_adjustment Media Playback Adjustment|

13:39:52 [kaz]

rrsagent, draft minutes

13:39:52 [RRSAgent]

I have made the request to generate http://www.w3.org/2014/05/28-webtv-minutes.html kaz

13:40:08 [ddavis]

yosuke: These trigger event types may be related to the Media In-Band Resource Community Group.

13:40:26 [ddavis]

yosuke: They're looking at MPEG events and tracks

13:40:47 [ddavis]

Bin_Hu: Right, it may be part of that or it could be something for another group to look into.

13:41:05 [kaz]

q?

13:41:14 [kaz]

q+ PaulHiggs

13:41:17 [kaz]

ack P

13:41:22 [ddavis]

PaulHiggs: In the use case you say this applies to a hybrid STB. Any reason why it has to be a hybrid STB?

13:41:38 [ddavis]

Bin_Hu: That's just an example. Maybe IP STB or other is also applicable.

13:41:48 [jcverdie]

q+

13:41:52 [yosuke]

q?

13:42:01 [kaz]

ack j

13:42:22 [ddavis]

jcverdie: I'm confused about the difference about your use case and a basic web app to get messages from the server.

13:42:45 [jcverdie]

s/get messages/get web notifications

13:42:54 [wuwei]

wuwei has joined #webtv

13:43:07 [ddavis]

Bin_Hu: For example with sports, you may have a trigger engine within the STB, e.g. at 7:00pm, so the user may be offered other content.

13:43:19 [ddavis]

Bin_Hu: But how to enable those events on the web platform is the issue.

13:43:41 [ddavis]

Bin_Hu: How to create the same experience on top of playing content (e.g. Channel 5)?

13:43:53 [ddavis]

Bin_Hu: The native platform is able to use such trigger engines.

13:44:12 [yosuke]

q?

13:44:16 [ddavis]

yosuke: Any other comments?

13:44:47 [ddavis]

yosuke: Bin, I think this is interesting so I'd like to do some gap analysis of this use case and the Media In-Band Resource CG.

13:45:01 [ddavis]

yosuke: I'll do that quickly and put the results on the mailing list.

13:45:05 [ddavis]

Bin_Hu: Great, thank you.

13:45:08 [kaz]

q+

13:45:28 [kaz]

ack q

13:45:52 [ddavis]

kaz: I'd also like to join the gap analysis work because there's a slight possibility of MMI work being related.

13:46:15 [PaulHiggs]

what is MMI?

13:46:17 [ddavis]

Topic: Accessibility use case extensions

13:46:43 [ddavis]

yosuke: Do we have any of the accessibility people here today?

13:46:51 [ddavis]

kaz: No but we can invite them for the next time.

13:48:46 [PaulHiggs]

is this "accessability" for those with disabled?

13:48:48 [ddavis]

ddavis: These are additional parts to the use cases from the first round.

13:49:36 [ddavis]

kaz: These are not necessarily brand new use cases. We can start by briefly checking the use cases additions that have been submitted.

13:49:50 [ddavis]

yosuke: So you suggest we walk through them quickly?

13:49:56 [ddavis]

kaz: Yes, some of them.

13:50:15 [ddavis]

kaz: Maybe we can just pick up the accessibility portion from some of them.

13:50:38 [ddavis]

yosuke: Do you have any suggestions about which to look at?

13:51:26 [ddavis]

kaz: Mark Sadecki (W3C) and John Foliot (member) created these. John considered media accessibility requirements so let's look at UC 8.

13:51:42 [kaz]

-> https://www.w3.org/html/wg/wiki/User:Jfoliot/UseCases#.22Use_Case_Eight_.E2.80.93_Download_and_Go.22 UC8

13:51:43 [ddavis]

yosuke: Use case is Download and Go.

13:52:06 [ddavis]

yosuke: The original use case is when the user downloads content on to a tablet to watch later.

13:52:39 [ddavis]

yosuke: Accessibility requirement is that whenever a media file is downloaded, all related resources (captions, etc.) must also be available for download.

13:53:05 [ddavis]

yosuke: The download of the supplemental resources should maintain the hierarchy.

13:53:17 [ddavis]

yosuke: The file directory structure is preserved in the download.

13:53:43 [ddavis]

yosuke: For example, putting all files in a zip or cab file.

13:54:02 [ddavis]

kaz: So this means we have to think about how to pack all related content.

13:54:30 [ddavis]

kaz: This is similar to ePub format for digital books.

13:54:56 [ddavis]

yosuke: The reality of the industry is that the recorder splits the information from the original stream.

13:55:35 [ddavis]

yosuke: I think we can suggest something to the TV industry.

13:55:48 [ddavis]

kaz: We could also think about media synchronisation for this purpose as well.

13:56:27 [ddavis]

kaz: Not only in-band information but also out-band information as well.

13:56:46 [ddavis]

yosuke: I think there are two ways to deal with these requirements.

13:56:56 [ddavis]

yosuke: One way is to improve these use cases.

13:57:07 [ddavis]

yosuke: But to me, these sound like more fundamental requirements.

13:57:59 [ddavis]

yosuke: It sounds like something similar to GGIE that is now talking about nodes between original creators and consumers and that content should not change between them.

13:58:23 [ddavis]

yosuke: We could create a note or guideline about essential requirements for web and TV.

13:58:39 [ddavis]

yosuke: Which way do you think fits into W3C's way of working best?

13:59:02 [ddavis]

kaz: Maybe we could start with a note or guidelines and if needed pick up additional requirements or use cases later.

14:00:40 [ddavis]

ddavis: So we can get general, more common accessibility issues as a note or set of guidelines, and then particular ones may be better as a new use case.

14:01:30 [ddavis]

yosuke: People form the industry can reference what kind of requirements they need to satisfy by looking at our guidelines. For something more specific we can have a separate use case.

14:01:49 [ddavis]

yosuke: So Kaz or Daniel, could you feed this back to the accessibility group?

14:01:52 [ddavis]

ddavis: Yes

14:02:01 [ddavis]

yosuke: Should we invite them to this call?

14:02:10 [ddavis]

kaz: Yes, we can do that.

14:02:33 [ddavis]

yosuke: Should the IG do something before the next call?

14:02:49 [ddavis]

yosuke: I can classify their requirements into general ones and specific ones.

14:03:04 [ddavis]

ddavis: That sounds very useful to me.

14:03:21 [ddavis]

kaz: we can also send a call for participation on this topic.

14:03:23 [Zakim]

-gmandyam

14:03:35 [gmandyam]

Giri signing off - thanks.

14:03:58 [ddavis]

ddavis: The deadline for use case submissions is the end of this week, right?

14:04:06 [ddavis]

kaz: Yes, but we can polish use cases after that.

14:04:51 [ddavis]

yosuke: So we've gone through all the use cases.

14:05:55 [ddavis]

ACTION: Yosuke to classify the accessibility requirements into general ones and specific ones.

14:05:56 [trackbot]

Created ACTION-197 - Classify the accessibility requirements into general ones and specific ones. [on Yosuke Funahashi - due 2014-06-04].

14:06:22 [Zakim]

-jcverdie

14:06:29 [ddavis]

ddavis: With 4k content starting to increase (e.g. Netflix) is this something that can affect our use cases? Do we need new ones?

14:06:58 [ddavis]

yosuke: In Japan broadcasters have started looking at caption for 4k but it's still very early stage.

14:07:28 [ddavis]

yosuke: I'm not sure the caption people have considered 4k. It may be better to ask them if there are gaps or problems.

14:07:45 [ddavis]

ddavis: OK, I'll ask them.

14:07:53 [Zakim]

-wuwei

14:08:36 [ddavis]

yosuke: During the last TPAC the work of the Community Group was migrated into the Working Group.

14:09:03 [ddavis]

ddavis: I can speak to the Timed Text Working Group

14:09:20 [ddavis]

ACTION: ddavis to ask Timed Text WG about 4k affecting captioning.

14:09:20 [trackbot]

Created ACTION-198 - Ask timed text wg about 4k affecting captioning. [on Daniel Davis - due 2014-06-04].

14:09:45 [ddavis]

yosuke: There may be other non-captioning issues with 4K.

14:10:00 [ddavis]

yosuke: We can take a step-by-step approach, looking at captioning first.

14:10:25 [ddavis]

yosuke: Another alternative is to also discuss other issues within the IG.

14:10:37 [ddavis]

yosuke: What do you think?

14:10:48 [ddavis]

kaz: I think step-by-step approach is better.

14:11:14 [kaz]

rrsagent, draft minutes

14:11:14 [RRSAgent]

I have made the request to generate http://www.w3.org/2014/05/28-webtv-minutes.html kaz

14:11:37 [ddavis]

yosuke: Let's go with a step-by-step approach.

14:11:48 [jcverdie]

jcverdie has joined #webtv

14:12:08 [ddavis]

PaulHiggs: If we're going to start looking at future technologies, there's all kind of things about gesture and speech-based input/control.

14:12:20 [kaz]

s/UC8/Accessibility Extension Use Case 8/

14:12:28 [ddavis]

PaulHiggs: Are you expecting use cases on those?

14:12:44 [kaz]

q

14:12:45 [kaz]

q+

14:13:00 [ddavis]

PaulHiggs: So we could focus on 4K but then we don't look at something else.

14:13:23 [ddavis]

yosuke: Any topic that IG members or the industry is interested in can be the topic for these use cases.

14:13:49 [ddavis]

yosuke: For example, Netflix is bringing 4K content so it's worth looking at.

14:14:24 [ddavis]

yosuke: Japanese industry will also start broadcasting 4k trials during this year's world cup. So it's not a far-future technology.

14:14:42 [ddavis]

yosuke: If there's something that can affect web users, it could be a relevant topic.

14:14:55 [wwu]

wwu has joined #webtv

14:16:03 [ddavis]

ddavis: There's also a requirement that any use case is fine as long as somebody has ownership of it.

14:16:10 [kaz]

q?

14:16:33 [ddavis]

PaulHiggs: Should Netflix be bringing this to the discussion?

14:16:48 [ddavis]

yosuke: What about asking the stakeholders to submit issues or problems?

14:17:15 [ddavis]

yosuke: There are some research facilities dealing with 4k - we can ask them about issues and web standards.

14:17:25 [ddavis]

kaz: You can also bring your ideas to the wiki.

14:17:51 [ddavis]

PaulHiggs: What I'm trying to say is let's solve a problem where there is one.

14:18:22 [ddavis]

PaulHiggs: I don't think we can answer what they need - only they can answer that.

14:18:57 [ddavis]

yosuke: Paul's point is good, so how about creating an invitation or questionnaire for 4k stakeholders?

14:19:15 [ddavis]

yosuke: We can create the text and ask stakeholders, sharing the result with the IG.

14:19:27 [ddavis]

yosuke: Based on that we can decide what to do next.

14:19:37 [yosuke]

q?

14:19:43 [kaz]

ack k

14:20:01 [ddavis]

ACTION: ddavis and yosuke to create questionnaire for 4k stakeholders about web standards issues.

14:20:02 [trackbot]

Created ACTION-199 - And yosuke to create questionnaire for 4k stakeholders about web standards issues. [on Daniel Davis - due 2014-06-04].

14:20:28 [ddavis]

yosuke: Thank you all. Let's do follow-up work on the mailing list.

14:20:39 [Zakim]

-Paul_Higgs

14:20:44 [Zakim]

-Kazuyuki

14:20:46 [Zakim]

-ddavis

14:20:47 [Zakim]

-Bin_Hu

14:20:49 [Zakim]

-Alex

14:21:05 [kaz]

[ adjourned ]

14:21:06 [ddavis]

rrsagent, make minutes

14:21:06 [RRSAgent]

I have made the request to generate http://www.w3.org/2014/05/28-webtv-minutes.html ddavis

14:21:19 [Zakim]

-yosuke

14:21:21 [Zakim]

UW_WebTVIG()9:00AM has ended

14:21:21 [Zakim]

Attendees were +1.650.946.aaaa, +49.303.aabb, Kazuyuki, Bin_Hu, Alex, ddavis, Paul_Higgs, yosuke, gmandyam, jcverdie, wuwei

14:22:17 [ddavis]

Regrets: Giuseppe, Mark_Vickers

14:24:02 [kaz]

rrsagent, draft minutes

14:24:02 [RRSAgent]

I have made the request to generate http://www.w3.org/2014/05/28-webtv-minutes.html kaz

15:02:41 [wuwei]

wuwei has joined #webtv

16:35:55 [Zakim]

Zakim has left #webtv

16:37:42 [wwu]

wwu has joined #webtv

17:59:27 [wuwei]

wuwei has joined #webtv

17:59:50 [kaz]

kaz has joined #webtv

18:17:51 [kaz]

kaz has joined #webtv

18:38:50 [kaz]

kaz has joined #webtv

18:39:14 [kaz]

kaz has joined #webtv

19:32:41 [wuwei]

wuwei has joined #webtv

20:13:53 [kaz]

kaz has joined #webtv

20:25:51 [kaz]

kaz has joined #webtv

21:05:51 [kaz]

kaz has joined #webtv

21:17:50 [kaz]

kaz has joined #webtv

21:19:50 [kaz]

kaz has joined #webtv

21:20:50 [kaz]

kaz has joined #webtv

21:21:11 [kaz]

kaz has joined #webtv

22:21:23 [kaz]

kaz has joined #webtv

22:23:21 [kaz]

kaz has joined #webtv

22:28:21 [kaz]

kaz has joined #webtv

22:41:21 [kaz]

kaz has joined #webtv

23:38:21 [jcverdie]

jcverdie has joined #webtv

23:38:23 [kaz]

kaz has joined #webtv

23:46:22 [kaz]

kaz has joined #webtv