Hi,
No problem, should be finished shortly.
I really appreciate the feeds of TV but I have to say that they are
overly complex for the overall content and things such as published
start times etc are really unhelpful.
<PublishedStartTime>2005-07-22T05:00:00Z</PublishedStartTime>
<PublishedDuration>PT03H00M00S</PublishedDuration>
Times in the well accepted '20050722050000' would be much better and
adding a duration instead of an end date/time is to me a waste. To make
the system useful im having to extract the time as a string, fiddle with
it and then for the finish time you have to extract the hours and
minutes and add this on.
I'm sure there are more than enough reasons for using the TVAnytime
standard but for use over the web I dont find it useful. Most of the
additional information held in the PL and CR files would be easily
attached to the main PI which would make processing much easier.
Just some thoughts,
Cheers, James.
unigamer wrote:
That would be much appreciated by me, I hope the project goes well.
On 01/08/05, James <[EMAIL PROTECTED]> wrote:
I'm just finishing a utility that
a) downloads the BBC's feeds and uncompresses them once per day and
b) an app which produces a very simple XML format with all the
relevant information about the programs.
c) A simple web app where you can define what channel and time frame
you want to know more information about
In between a & b I store all the information in the database so I may
open this up too, dependent on how hard it gets hit.
Either way whatever i produce will be made available to all.
Jim.
Ben O'Neill wrote:
Mmmm, I can't help but feel the volume of information is over the top.
I've even thought it'd be worth installing a triple store and using
that to do some knowledge "stuff".
With my current PC-based TV guide about to expire I was thinking about
replacing that using the BBCs feeds but the Radio Time's data would
make this far far simpler ...
What are others using the data for?
On 01/08/05, Andrew McParland <[EMAIL PROTECTED]> wrote:
Hi Ben,
What sort of documentation would you like? A few pointers to some existing
information below:
+ Our LGPL'ed Java TV-Anytime API:
http://www.bbc.co.uk/opensource/projects/tv_anytime_api/
contains a useful paper detailing the API which gives a good idea of
what's in TV-Anytime, also available from:
http://www.bbc.co.uk/rd/pubs/whp/whp-pdf-files/WHP060.pdf
+ Plenary documents of the TV-Anytime Forum (including drafts of the
specifications):
ftp://tva:[EMAIL PROTECTED]/Plenary/0-Plenary.html
+ Including a draft of the current ETSI version of the Metadata
specification (includes XML Schema):
ftp://tva:[EMAIL PROTECTED]/Plenary/TV288r1.zip
+ And a Systems specification that includes some more examples and
philosophy of use:
ftp://tva:[EMAIL PROTECTED]/Plenary/TV302r1.zip
+ Note that the ETSI versions are the definitive versions of the
specifications, freely downloadable with registration from www.etsi.org
+ A short, high-level introductory overview: "TV-Anytime - using all that
extra data":
http://www.bbc.co.uk/rd/pubs/whp/whp-pdf-files/WHP050.pdf
+ An overview of the structure of the specifications: "TV-Anytime Phase 1 -
a decisive milestone in open standards for Personal Video Recorders":
http://www.ebu.ch/trev_295-evain.pdf
Some of the higher level documents are useful for getting accross the "ah,
it's not just an EPG then" idea and the use of identifiers (CRIDs),
grouping, etc.
I hope that helps a bit. But please do let us know what more specific info
would help you.
Cheers,
Andrew
Andrew McParland | Phone: +44 (0) 1737 839590
BBC Research & Development | Fax: +44 (0) 1737 839665
Kingswood Warren, Tadworth | Email: [EMAIL PROTECTED]
Surrey, KT20 6NP, UK | Web: http://www.bbc.co.uk/rd
On Tue, Jul 19, 2005 at 03:23:00PM +0100, Ben O'Neill wrote:
I like the data and plan on using it quite soon (I've only had brief
looks so far) but I'd like to see better documentation. Being gzipped
isn't a problem for me.
On 19/07/05, Ben Metcalfe <[EMAIL PROTECTED]> wrote:
Hello folks
As you will know, we released the TV Anytime feeds a couple of weeks
back (In case anyone hasn't seen them yet, they live here:
http://backstage.bbc.co.uk/data/7DayListingData)
We're keen to hear your feedback about the feeds, in particular if there
is anything we can do to help make them easier for you to integrate into
your prototypes.
Please let us know your thoughts and views generally, but questions we
have been thinking about include:
* Could we package them differently (ie not gzip archive)?
* Do we need to make better documentation available?
* Do you want a perl/php API to access the data more easily?
Please let me know - either via this list or directly to me: backstage
(at) bbc.co.uk.
Thanks folks
Ben + backstage.bbc.co.uk team.
-
Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please
visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html.
--
Ben O'Neill
[EMAIL PROTECTED]
-
Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please
visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html.
-
Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please
visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html.
Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
-
Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please
visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html.
Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
-
Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please
visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html.
Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
