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

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

From: Shelly Lin <slin@mozilla.com>
Date: Wed, 10 Sep 2014 21:18:00 -0700 (PDT)
To: Paul Higgs <paul.higgs@ericsson.com>
Cc: BIN HU <bh526r@att.com>, Marco Chen <mchen@mozilla.com>, shkim@etri.re.kr, public-tvapi@w3.org
Message-ID: <568599867.20601431.1410409080029.JavaMail.zimbra@mozilla.com>
Hi Paul, 

Sure, please feel free to remove the content of "Media Source" for OIPF. 
"Media Source" refers to the object type of broadcast(pushed) content, for example, whether it is a MediaStream object, an URI-base media element (e.g.. using tv://), or any other. 

Thanks, 
Shelly 

----- Original Message -----

From: "Paul Higgs" <paul.higgs@ericsson.com> 
To: "Shelly Lin" <slin@mozilla.com>, "BIN HU" <bh526r@att.com> 
Cc: "Marco Chen" <mchen@mozilla.com>, shkim@etri.re.kr, public-tvapi@w3.org 
Sent: Thursday, September 11, 2014 1:39:20 AM 
Subject: RE: Wiki Table of Class hierarchy of TV APIs for discussion 



Hi Shelly 



Can we remove that “HTMLObjectElement(URI base)” from the table for OIPF or perhaps you could clarify your expectations for the the column “Media Source”? 



The OIPF specifications define three different video player objects with different state machines due to their different characteristics of the services they support 

· first is the A/V Control object which (profiled and extended from CEA-2014) is designed to support “pulled” (RTSP, HTTP, DASH)/downloaded(HTTP,FLUTE) content. This is a widely implemented player as it has been specified and deployed since 2009 

· second is the video/broadcast object which is used for “pushed” content, i.e DVB, ATSC, ISDB, IGMP/RTP. This is also well deployed for both windowed and full-screen broadcast services (i.e. HbbTV) 

· third is the HTML5 <video> element, I guess I don’t need to explain that 



My understanding of the work in this group is to define a new interface to something with the same functionality as the second OIPF player (the video/broadcast object). The media source for this is not an HTMLObjectElement and the two OIPF defined players are based on that solely for integration with the DOM. 



Paul 




From: Shelly Lin [mailto:slin@mozilla.com] 
Sent: Friday, September 05, 2014 2:30 AM 
To: BIN HU 
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 



----- Original Message -----



From: "BIN HU" < bh526r@att.com > 
To: "Marco Chen" < mchen@mozilla.com > 
Cc: shkim@etri.re.kr , 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 ; 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 > 
收件者 : 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. 
Received on Thursday, 11 September 2014 05:00:29 UTC

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