W3C home > Mailing lists > Public > public-tvapi@w3.org > September 2014

RE: Wiki Table of Class hierarchy of TV APIs for discussion

From: HU, BIN <bh526r@att.com>
Date: Fri, 5 Sep 2014 16:22:52 +0000
To: Shelly Lin <slin@mozilla.com>
CC: Marco Chen <mchen@mozilla.com>, "shkim@etri.re.kr" <shkim@etri.re.kr>, "public-tvapi@w3.org" <public-tvapi@w3.org>
Message-ID: <179FD336116F754C876A9347238FE29A026E0B0A@CAFRFD1MSGUSRIA.ITServices.sbc.com>
Thank you Shelly for the great work.

All,

Please continue the analysis and add the related information to the table.

Thanks
Bin

From: Shelly Lin [mailto:slin@mozilla.com]
Sent: Thursday, September 04, 2014 11:30 PM
To: HU, BIN
Cc: Marco Chen; shkim@etri.re.kr; public-tvapi@w3.org
Subject: Re: Wiki Table of Class hierarchy of TV APIs for discussion

Hi everyone,

I've added a new column of "Media source's type" to the table of class hierarchy of TV APIs.
Both Mozilla and Webions are clear on using MediaStream. As for OIPF, the result of "HTMLObjectElement(URI base)" is referenced from their API spec, Volume 5 (Declarative-Application-Environment), 7.1.1.1 and 8.3.

I'm not so sure on the OIPF part, please feel free to correct/fill in the rest cells, thank you very much!

Cheers,
Shelly

________________________________
From: "BIN HU" <bh526r@att.com<mailto:bh526r@att.com>>
To: "Marco Chen" <mchen@mozilla.com<mailto:mchen@mozilla.com>>
Cc: shkim@etri.re.kr<mailto:shkim@etri.re.kr>, public-tvapi@w3.org<mailto:public-tvapi@w3.org>
Sent: Thursday, September 4, 2014 4:36:24 AM
Subject: RE: Wiki Table of Class hierarchy of TV APIs for discussion

Marco,

Thank you for your insight.

Perhaps you can edit the wiki and add one or more column with the suggested information there?

Thanks
Bin

From: Marco Chen [mailto:mchen@mozilla.com]
Sent: Wednesday, September 03, 2014 7:05 AM
To: HU, BIN
Cc: shkim@etri.re.kr<mailto:shkim@etri.re.kr>; public-tvapi@w3.org<mailto:public-tvapi@w3.org>
Subject: Re: Wiki Table of Class hierarchy of TV APIs for discussion

Hi,

Refer to [1], it seems that Webinos used mediastream (under Program column) to expose program information (ex: EPG).
But checking with [2], it is defined as "represents a valid source for a HTMLVideoElement" only.
Thus I think to put mediastream under Program column is not proper for Webinos.

This issue brings me another suggestion.
Maybe we can also collect what object is used to represent TV stream from each of specs. (ex: MediaStream or dvb://)

[1] http://www.w3.org/community/tvapi/wiki/Main_Page/Class_Hierarchy

[2] http://dev.webinos.org/specifications/draft/tv.html






Thanks,
Sincerely yours


________________________________
寄件者: "BIN HU" <bh526r@att.com<mailto:bh526r@att.com>>
收件者: shkim@etri.re.kr<mailto:shkim@etri.re.kr>, public-tvapi@w3.org<mailto:public-tvapi@w3.org>
寄件備份: 2014 9 月 3 星期三 上午 3:54:41
主旨: Wiki Table of Class hierarchy of TV APIs for discussion

Hello team,

Thank you all for the participation and good discussion this morning. I created a wiki table of class hierarchy analysis. See [1]. This is also directly linked from our main wiki page [2] – under “1.1.2 API Specification”.

Thank you
Bin

[1] http://www.w3.org/community/tvapi/wiki/Main_Page/Class_Hierarchy

[2] http://www.w3.org/community/tvapi/wiki/Main_Page


From: 김성혜 [mailto:shkim@etri.re.kr]
Sent: Tuesday, September 02, 2014 2:25 AM
To: public-tvapi@w3.org<mailto:public-tvapi@w3.org>
Subject: Class hierarchy of TV APIs for discussion


Dear All,

I have looked at the class hierarchy for Mozilla’s TV manager API and Webinos APIs.
I also have looked at the APIs defined in TTA (standard association in Korea).



Root

Tuner

Channel

Program

Mozilla

TVManager

TVTuner

TVChannel

TVProgram

Webinos

TVManager

TVDisplayManager
TVTunerManager

TVChannel

MediaStream

TTA



ChannelManager

Channel

Program

OIPF DAE









Hybridcast









…










We need to look at other APIs that are defined by other SDOs and APIs that are used by the TV manufacturers to meet the requirements that we have developed.

In today's conference call, I hope we can make a base hierachary and we can work on the APIs in the next meeting.
Also, I think we need to number the requirements to make it easy to propose and define APIs that meets our requirements.

Regards,
Sung Hei Kim
Wook Hyun.


Received on Friday, 5 September 2014 16:24:17 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:45:12 UTC