Re: [backstage] Links to video/audio for specific shows

2007-07-13 Thread Ben O'Neill

That's just a flaw in TV-Anytime that should be fixed.

Why not switch it to use real URLs that actually go somewhere (as the 
Semantic Web is supposed to) and stop using CRIDs - integrate the two 
ideas :)


Ben

Chris Sizemore wrote:
yes, i agree that TV-Anytime supplies some of the requirement (indeed, 
perhaps everything brian was suggesting... brian?)
 
but does TVA, despite the URN (the crid, i.e. 
crid://my.id.creator/xxx88r; http://en.wikipedia.org/wiki/Crid), 
supply the on the Web part?
 
depending on one's philosophical bent, that's one of the potential 
problems with URNs  thus CRIDs: they can't (easily) be dereferenced, in 
the way that a regular old URL can be... URNs aren't on the Web...
 
i guess what i'm saying is that the regular old URL for a programme 
Episode should be just as permanent as the TVA CRID -- and because 
it's permanent AND on the Web, the regular old URL is even more 
useful than the CRID.
 
the permanent URL works great for people AND machines (which can follow 
the link from the URL to the CRID and thus to the asset(s))...
 
everybody wins?
 
 
best--
 
--cs



*From:* [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] *On Behalf Of *Andy Burras

*Sent:* 13 July 2007 08:37
*To:* backstage@lists.bbc.co.uk
*Subject:* RE: [backstage] Links to video/audio for specific shows

 


Isn’t that TV-Anytime ?

Each programme has a unique URI identifier. Then a separate data source 
holds a mapping between the IDs and the locations it can be obtained from


 


Cheers…

…Andy B.

-
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/


Re: [backstage] Links to video/audio for specific shows

2007-07-13 Thread Ben O'Neill


On 13 Jul 2007, at 11:45, Steve Jolly wrote:


Ben O'Neill wrote:

That's just a flaw in TV-Anytime that should be fixed.
Why not switch it to use real URLs that actually go somewhere (as  
the Semantic Web is supposed to) and stop using CRIDs - integrate  
the two ideas :)


A number of reasons.

Because a programme can be accessed in a number of different ways,  
which change over time.  You might be satisfied with a single http  
URL, but someone without a net connection would find it distinctly  
useless.


They'd find it no less useless than a CRID ...



Because some common kinds of location are intrinsically ephemeral -  
DVB locators, for example, which are useless after the broadcast  
which they refer to.


Because some common kinds of location change with time.  Again, DVB  
locators can contain the time of a programme being broadcast, and  
if the schedule changes, the locator needs to change too.


Surely that causes major problems with matching.



TV-Anytime was designed to try not to favour one method of  
accessing content over another - which is good from the perspective  
of a broadcaster with multiple platforms, and also good for the  
average Joe who has both broadband and access to digital TV, IMO.


I'm not favouring any method over any other method. Using a valid URL  
doesn't mean that you have to go to the web page, it simply means  
that if you can access the Internet you can go to the web page to get  
more data that your dataset may not have due to being out-dated or  
otherwise.




S
-
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/


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.  
Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/


Re: [backstage] O2 - iPhone deal - UK

2007-07-05 Thread Ben O'Neill

Christopher Woods wrote:

Pfft.

Good things and bad things will come from this:

Good:
O2 won't be able to knacker the phone by slapping their custom
memory-hogging interface onto it (like they did with my lovely XDA 2i, it
took me ages to clear out the crap they put on it!)

O2 won't be able to slap their branding on it

Bad:

O2 most likely won't bring out any inclusive data plan for this, and since
when did they have an EDGE network? Orange has largest European EDGE
network, and T-Mobile has one too pan-Europe, but O2? Just plain old, slow,
GPRS. UK iPhone users are going to have HEFTY data bills, and they're going
to be pissed off with the slow browsing speed.



O2 has a 3G network, it's expected the iPhone will have 3G when it 
launches here anyway

-
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/


Re: [backstage] BBC on YouTube

2007-03-02 Thread Ben O'Neill
I believe that UK residents won't be able to view any of the content  
that has adverts in it.


On 2 Mar 2007, at 18:37, James Cridland wrote:


On 3/2/07, Andrew Bowden [EMAIL PROTECTED] wrote:


 Might interest some people here.

*http://www.youtube.com/BBC* http://www.youtube.com/BBC
*http://www.youtube.com/profile?user=bbcworldwide*http:// 
www.youtube.com/profile?user=bbcworldwide


Particularly interesting is the announcement that Top Gear, for  
example,
will carry ads on this system: within the UK, too. I think this is  
the first

time that BBC programming has ever carried ads while being part of a
BBC-branded 'channel' online.

(Do you remember back in 1999, when Yahoo News did a deal to take  
BBC News
content as long as it had no advertising around it? Hum, whatever  
happened

to that?)

--
http://james.cridland.net/


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.  
Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/


Re: [backstage] Uk geocoder?

2005-08-11 Thread Ben O'Neill
What are you interested in?  Placenames to latitude / longitude or postcodes?

I have a database for placenames with latitude/longitude but no postcodes.

See:
http://www.jibble.org/ukpostcodes/


On 06/08/05, Siobhan Ramsey [EMAIL PROTECTED] wrote:
  
  
 
   
 
 Can anyone help me out with where I can access a free online geocoder for
 the uk?  Is there a summary/list idiots guide anywhere of all BBC googlemap 
 projects. 
 
   
 
 Thanks 
 
   
 
 Siobhan Ramsey 
  
  
  
 
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of Graeme Mulvaney
  Sent: 05 August 2005 15:02
  To: backstage@lists.bbc.co.uk
  Subject: Re: Creating New Topics (Was: [backstage] NewsGlobe Update) 
 
   
  
 
 I think that using a new subject is better - I'm using gmail which
 auto-threads them into conversations, it makes life so much easier. 
  
 
   
  
 
 --- 
  
 
   
  
 
 # I've got another 50 gmail invites - if anybody wants an account just mail
 me...
  

  
 
 On 8/5/05, Dave Cross [EMAIL PROTECTED] wrote: 
 
 On Fri, Aug 05, 2005 at 01:01:30PM +0100, David Burden wrote:
  
  [ interesting stuff that had nothing to do with what he was replying to ] 
  
  David,
  
  When creating a new topic of dicussion on this (or any other) mailing
  list, it's a really good idea to create a completely new email instead
  of just replying to an old one an changing the subject. 
  
  The reason for this is that when you reply to an email, your mail
  program inserts headers called 'In-Reply-To' and 'References' which
  indicate which discussion thread your email belongs to. When someone
  reads your email in a program that supports a threaded view of the 
  discussion (e.g. thunderbird or mutt) then the program uses those
  headers to work out where to display your message.
  
  As a result, your email about NewsGlobe appeared way down in the
  discussion on Ave's bbc2mp3 instead of in its own new thread. 
  
  I realise that most people don't use threaded email readers so they
  don't notice the problem, but it can get really annoying for those of
  us who do.
  
  Thanks,
  
  Dave...
  
  --
  Stab a sorry heart 
  With your favourite finger
  
  
  -
  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/ 
 
 
  
  
  -- 
  You can't build a reputation based on what you are going to do. 


-- 
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.  
Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/


Re: [backstage] TV-Anytime: Feedback please!

2005-08-01 Thread Ben O'Neill
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/
 


-- 
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.  
Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/


Re: [backstage] Geotagging BBC news stories

2005-07-22 Thread Ben O'Neill
Is it against the TCs to provide an RSS file that is 99% the same as
the one on the BBC but with geographical information added?

On 21/07/05, Tony Hirst [EMAIL PROTECTED] wrote:
 backstage@lists.bbc.co.uk on 21 July 2005 at 21:52 + wrote:
  it seems you have the same motivation as I had when I mailed this list
 about RSS Annotation Streams!
 
 missed that - ah:
 http://www.mail-archive.com/backstage@lists.bbc.co.uk/msg00330.html and
 http://datamining.typepad.com/data_mining/2005/07/rss_annotation_.html
 
 I agree with the sentiment, and then some - if someone goes to the trouble
 of adding value to a story/feed, it would be good if those extras could be
 syndicated separately but identifiably too without others having to
 reinvent/reimplement the same technique/recreate the same annotation data.
 
 Perhaps this is format that we want to develop
 further?
 
 That sounds like an interesting (and perhaps useful) exercise...where to
 start? i tend to work back to generalised solutions from a couple of
 similar but different implementations of a thing...would it be fair to say
 that the annotation stream on its own would be relatively worthless
 without the original story it was annotating? or could you imageine it
 ever standing alone on its own terms?
 
 
 Back to the geotagged BBC stories, even something as simple as returning
 lat/long when passed a story ID would be v reusable...
 
 For example:
 http://backstage.bbc.co.uk/prototypes/archives/2005/05/a_map_of_the_ne.html
  http://boneill.ninjagrapefruit.com/wp-content/bbc/newmaps/ divines geo
 data
 
 and  Duncan's http://backstage.min-data.co.uk/geotagged/  must have a
 script for locating stories
 So if someone can make story id/geotag info available, then I'm sure the
 lazy community (of which I count myself a part) would be v grateful :-)
 
 tony
 
 
 -
 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.


Re: [backstage] TV-Anytime: Feedback please!

2005-07-19 Thread Ben O'Neill
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.


Re: [backstage] Article IDs are unique?

2005-06-25 Thread Ben O'Neill
From when Ben has previously posted it was my understanding that the
article ID is unique, but it can change.  If new information becomes
available and a major change in the article takes place the article
will get a new id.

On 25/06/05, Gavin Joyce [EMAIL PROTECTED] wrote:
 Thanks,
 
 I understand that articles can be updated with time, and I use the
 article ID as the identifier rather than the published date or the
 text content.
 
 Actually, I mistakenly left out the two article titles which seemed
 like they were not related (other than both being about tennis). The
 first was about a player called 'Gonzal' and the second is about
 Roddick struggling past Daniele Bracciali.
 
 I have since cleared my test database, but I follow up if I see this
 behaviour again.
 
 Thanks,
 Gavin
 
 On 25/06/05, mike chamberlain [EMAIL PROTECTED] wrote:
  On 6/24/05, Gavin Joyce [EMAIL PROTECTED] wrote:
   Hi,
  
   Are the IDs of articles published on bbc unique per article without
   time limit? Or are the IDs reused with time.
  
 
  A story can be updated and republished with the same id. The update
  might just be spelling/grammer corrects, or it could be more detailed
  rewrite...
 
  Mike.
 
 
  -
  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.
 


-- 
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.


Re: [backstage] New Prototype - Have I Got News (Feeds) For You

2005-05-28 Thread Ben O'Neill
I like this, does need funnyness though, maybe give them chances to
guess as well (ie don't give us the answer after 1 wrong answer)?

On 28/05/05, Nick Crossland [EMAIL PROTECTED] wrote:
 OK, since my first idea, of mapping traffic data - Google maps has been
 done already now, here's something a bit different:
 
 http://www.nickcrossland.co.uk/missingwordsround
 
 It's a prototype for an online version of the 'Missing Word' Round from
 'Have I Got News For You'. It takes 100 most recent headlines from the
 BBC Backstage RSS news feed, updated every 15 minutes. The missing words
 are selected semi-randomly by the server, so may not have quite the
 comic potential of the TV version. PHP isn't renowned for its sense of
 humour.
 
 The feeds are filtered for certain keywords, since death, murder and
 destruction aren't really that funny. The odd one may still slip through...
 
 Because it is based on an RSS feed, there's the potential for 'guest
 publications' - just like the show. That is, assuming 'Knitting Machine
 World', 'Sea Shell Quarterly' or 'Centre Parting Monthly' publish an RSS
 version of their headlines!
 
 To-Do
 # Track user sessions, so that you don't get repeat headlines
 # Add 'funniness voting' to previous user guesses. Can then give the
 'funniest' answers on the homepage, or show them more prominently on the
 answers page
 # Find a better way of analysing the headlines so 'better/funnier' words
 can be blanked out (if anyone knows of an API or free source of a
 dictionary, to work out whether the words are nouns, adjectives, etc
 that would be very helpful!)
 # Include more RSS feeds, perhaps giving users a choice of which one
 # Give credit if you are close to the answer, rather than having to get
 it exactly
 
 ~nick~
 
 


-- 
Ben O'Neill
[EMAIL PROTECTED]