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> 
收件者: shkim@etri.re.kr, 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 
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.