W3C home > Mailing lists > Public > public-web-and-tv@w3.org > March 2015

RE: New User Discovery Use Case

From: Evain, Jean-Pierre <evain@ebu.ch>
Date: Fri, 20 Mar 2015 17:14:37 +0000
To: Bill Rose <brose@wjrconsulting.com>, "public-web-and-tv@w3.org" <public-web-and-tv@w3.org>
Message-ID: <A71D9E70FCEE5E40A5EAA598864E60574B83599F@maildrs.gva.ebu.ch>
In Part 3-3 you can find the extra user information like the terminal and network information.

I lost track of OpenEPG, I remember T VA existed wheb there was a call for technology for openEPG and it has probably inspired a lot when openEPG was developed. I guess a lot can be mapped. DVB-SI is a very small subset of TVA in all respects.

As I said we still have request for extensions, which proves it is used. Some information can be found here:
https://tech.ebu.ch/tvaexternalreferences It is not updated and we know there is more but people do not necessarily communicate on this. As you can see ARIB in Japan transcribed the spec as it is usually the case. I know TV-Anytime is used there but i don't know the details. I also know companies who have used it in the US but hard to share names without their consent.

It is interesting to see that TVA's concepts where extremely innovative. Not much new under the sun really. Anywhere, anytime, claimed by many but specified by few

jean-pierre

________________________________
From: Bill Rose [brose@wjrconsulting.com]
Sent: 20 March 2015 17:35
To: Evain, Jean-Pierre; public-web-and-tv@w3.org
Subject: RE: New User Discovery Use Case

Hi JP

Thanks for the new info. What capabilities does it have for client related information - decoders, resolution, buffering, etc.?

Also, how different is CEA 2033 - OpenEPG from TV Anytime and DVB-SI? I see DLNA supports both as well as DVB-SI. Can they map somehow?

Finally, who (what) supports TV Anytime? i.e. how widely supported is it by TVs, STBs, browsers, etc., in the US, EU, Japan?

From: Evain, Jean-Pierre [mailto:evain@ebu.ch]
Sent: Friday, March 20, 2015 4:55 AM
To: Bill Rose; public-web-and-tv@w3.org
Subject: RE: New User Discovery Use Case

Hi Bill,

It is interesting to not that you actually skipped the key part of TVA-Anytime, i.e. part 3 that contains the schema :--)

In Part 3-1, you’ll find a user description split into user preferences (profile, search and browsing preferences) and usage history (how content has been consumed – actions, etc.). In 3-3 you find more metadata such as on accessibility…

In part 3-1, you’ll find information about the programme: editorial metadata, purchase conditions, etc.

In part 3-3 and part 3-4  you find more information on advertising, interstitial, coupons, etc. You also have more information about rights.

CRID is a unique identifier – quite ahead of its time as it came before ISAN and EIDR, which both can be used in creating CRIDs (defined in an RFC too) which make them further unique within a content provider namespace (e.g.. in a particular application domain).
CRIDs can be used to store information about content. An interesting scenario is that you see an announcement about a programme either in an EPG or watching a trailer. According to the application at hand (red button or just hyperlink) you select this content and decide “record when available” or “advise when available on replay”, etc. All is managed through the smaller piece of information that an unique identifier is.
The question of authority is therefore solved by:

-          Using uniquely attributed IDs from ISAN/EIDR

-          Manage you own unique IDs as content provider within your namespace using the RFC CRID structure (reusing ISAN/EIDR or not)


For more on TVA:  https://tech.ebu.ch/tvanytime and you can download the latest version of the specification there. We have started a new maintenance phase for ETSI at the request of the industry and we’ll deal further with social media, etc.

I actually have to start my TVA webex… now!

See you soon.

Best regards,
Jean-Pierre


From: Bill Rose [mailto:brose@wjrconsulting.com]
Sent: jeudi 19 mars 2015 20:33
To: Evain, Jean-Pierre; public-web-and-tv@w3.org<mailto:public-web-and-tv@w3.org>
Subject: RE: New User Discovery Use Case

Thanks JP (I think - I spent much of today reading/scanning through the TVA documents, in particular parts 1, 2, and 4 with a quick look at parts 5, 8 and 9). I was aware of TVAnytime but not the details. You are right, a lot of information and examples are there. I didn't see anything on having the client criteria as being part of the user's search criteria although that might be implicit in the user search criteria. If I understand it correctly the user inputs their search criteria which is received by a service that returns CRID(s) that meet the criteria. The client criteria, if included, would further narrow what is returned and might be useful in narrowing location resolution. I also see cost data can be requested/returned for the various content CRIDs.

I noticed that there is no authority to assign CRIDs and I didn't see how that would be done. Probably in another document. However, it appears a given CRID may be reusable (may have an expirataion date) which would be a problem if it is added as a watermark or fingerprint to content which are fixed for all time once added. Thus any CRID used to watermark would have to be permenent (no expiration). While that appears to be an option, I am not sure if it is possible to ensure there is no possibility of duplication and if, without an authority, the CRID approach would be able to accommodate the large number of content IDs required for what GGIE envisions. Feel free to comment on my observations and TVA's applicablility to what GGIE is doing.

Any comments on the UC I posted? And do you have any User Discovery UCs you want to post?

Thanks for the reference.

Bill



From: Evain, Jean-Pierre [mailto:evain@ebu.ch]
Sent: Thursday, March 19, 2015 4:37 AM
To: Bill Rose; public-web-and-tv@w3.org<mailto:public-web-and-tv@w3.org>
Subject: RE: New User Discovery Use Case

Hello Bill,

Thanks,

Do you know the TV-Anytime specification ?

I contains a lot about user description, user modes of content consumption, content description, all in order to facilitate search and recommendations.

In addition to this, all TVA mechanisms for describing broadcast and on-demand publication events and associated services have been introduced in an earlier version od schema.org.

The TVA data model is also actually RDF ready.

If you need more information…

Best regards,

Jean-Pierre

From: Bill Rose [mailto:brose@wjrconsulting.com]
Sent: mercredi 18 mars 2015 21:02
To: public-web-and-tv@w3.org<mailto:public-web-and-tv@w3.org>
Subject: New User Discovery Use Case

Resending - My appologies if you get 2 copies of this. I had not set my permissions to post W3C message archives. - Bill

I posted a Use Case for GGIE User Discovery at https://www.w3.org/2011/webtv/wiki/GGIE_TF/UseCases/User_Discovery to get the discussion started on this subject. Its an extension to Streaming UC-1b adding client information to the search criteria. As I am new to this feel free to edit, comment, make suggestions - including that it does not belong here, or whatever. Also, feel free to post new User Discovery Use Cases or discussion topics.

Bill Rose
WJR Consulting Inc.
Office: (860) 313 8098
Cell: (860) 794 3846

________________________________

**************************************************
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error, please notify the system manager. This footnote also confirms that this email message has been swept by the mailgateway
**************************************************

________________________________

**************************************************
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error, please notify the system manager. This footnote also confirms that this email message has been swept by the mailgateway
**************************************************
------------------------------------------------------------------------------

**************************************************
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error, please notify the system manager. This footnote also confirms that this email message has been swept by the mailgateway
**************************************************
Received on Friday, 20 March 2015 17:15:58 UTC

This archive was generated by hypermail 2.3.1 : Friday, 20 March 2015 17:15:59 UTC