RE: [backstage] What would you love to see coming out of BBC Vision in the near future?
here's an example of some work in that direction by my colleague michael smethurst: http://bbc-hackday.dyndns.org:2825/programmes/29xn (currently down, tho -- michael?) is back now - apologies with rdf here: http://bbc-hackday.dyndns.org:2825/programmes/29xn.rdf winmail.dat
Re: [backstage] What would you love to see coming out of BBC Vision in the near future?
Great idea. Better if you could just type Neil Young and get a video wall http://www.blinkx.com/ of 25 moving images of the man hyper linked to different performances, with a drop down box to refine the video wall by show or year. A user would not want to peruse that hierarchy and the rdf feeds don't work in my yahoo or google reader,don't for me anyway. Richard On 07/03/2008, Michael Smethurst [EMAIL PROTECTED] wrote: here's an example of some work in that direction by my colleague michael smethurst: http://bbc-hackday.dyndns.org:2825/programmes/29xn (currently down, tho -- michael?) is back now - apologies with rdf here: http://bbc-hackday.dyndns.org:2825/programmes/29xn.rdf
RE: [backstage] What would you love to see coming out of BBC Vision in the near future?
I think we absolutely agree in principle, richard, great suggestions and advice... Within an organisation such as the BBC, maybe what is most important in the first instance is a common set of principles for managing and publishing IDs rather than a one size fits all system? -- agreed, and that lingua franca is no doubt going to be (is already starting to be) URI identifiers exchanged (internally in the 1st instance) over HTTP... so, in many cases this is in the form of system-namespace/GUID : http://some.internal.system.bbc.co.uk/ba853904-ae25-4ebb-89d6-c44cfbd56thy (which for instance, might mean the iPlayer genre Drama to that system...) and then there's going to need to be an equivalency engine which helps map between all the different systems across the Beeb which know about and have an ID for, say, Torchwood series 2 episode 6 or Jonathan Ross... there's no one true ID or URI for these concepts... how true does that ring for you? and, though I really don't want to start a what does a URI represent? or who's more Restful? flame war, I'm interested in unpacking what you mean by the musicbrainz example should be a location where you find out information about ³Blur²... isn't that what the following URL does? http://musicbrainz.org/artist/ba853904-ae25-4ebb-89d6-c44cfbd71bd2.html i.e. that URI is a location where you find out metadata about Blur, isn't it? BTW, I'm thinking about all this in terms illustrated by the following: http://www.w3.org/DesignIssues/LinkedData.html http://www4.wiwiss.fu-berlin.de/bizer/pub/LinkedDataTutorial/ http://ivanherman.wordpress.com/2007/10/12/wikipedia-uri-s-as-reliable-identifiers-for-the-semantic-web/ http://fgiasson.com/blog/index.php/2007/05/22/browsing-musicbrainzs-dataset-via-uri-dereferencing/ best-- --cs ** From: [EMAIL PROTECTED] on behalf of Richard Cartwright Sent: Thu 3/6/2008 10:13 AM To: BBC Backstage Subject: Re: [backstage] What would you love to see coming out of BBC Vision in the near future? Hi Chris It¹s not the size or form of your ID that matters, it is what you do with it that counts ;-) For UUIDs, UMIDs or URLs, you need a common understanding of what happens to them in inevitable change. I think of one use for a URL as a reference to a location where content can be expected to change, such as a news service home page, whereas I consider a UUID is immutable, it refers to one item of content for ever. Create a new version of the content and you have to create a new ID. However, this is a way of thinking and true for most ID schemes ... it all depends on how you choose to manage your identifiers. My excursion into the world of AAF has taught me a lot about comprehensive techniques for structuring and managing IDs for, and relationships between, all kinds of different media material. Most of what AAF is about is structural metadata, how one thing relates to another in a package, along a timeline, encoded with a particular codec etc.. This allows you to trace relationships between content through its various authoring stages back to its original source, a kind of super edit decision list. Structural metadata can be enhanced with descriptive metadata, normally using a schema of your own choosing as there is limited agreement between organisations about what this should be. So to build and expose your EverythingBrainz, perhaps what is needed is an API for exploring structural relationships between items of content, perhaps based on UUIDs, and an API for searching on descriptive metadata (actors, locations, scripts, awards) that may return results including related UUIDs? These APIs could be WSDL or ReSTful in style. For example, I personally think the musicbrainz example should be a location where you find out information about ³Blur² ... http://musixbrainz.org/artist/blur Where an item is currently published is really an item of descriptive metadata. Every generation of the page should have its own ID within a content management system and the published URL refers to the currently published version. The API I propose would allow you to find out the ID of the currently published version and, with appropriate permissions, to explore previous versions of the page via ID relationships. UUID, URL, maiden name, doesn¹t matter as long as the relationships are consistent. In summary, I believe that you could use many different ID schemes and many different descriptive metadata schemas. The important things are: understanding relationships between IDs are how they managed over time; how to map between the ontologies of the various different descriptive schema. Within an organisation such as the BBC, maybe what is most important in the first instance is a common set of principles for managing and publishing IDs rather than a one size fits all system? Cheers, Richard On 4/3/08 23:17, Chris Sizemore [EMAIL PROTECTED] wrote: cool stuff richard. so how do/should we expose
Re: [backstage] What would you love to see coming out of BBC Vision in the near future?
Hi Chris It¹s not the size or form of your ID that matters, it is what you do with it that counts ;-) For UUIDs, UMIDs or URLs, you need a common understanding of what happens to them in inevitable change. I think of one use for a URL as a reference to a location where content can be expected to change, such as a news service home page, whereas I consider a UUID is immutable, it refers to one item of content for ever. Create a new version of the content and you have to create a new ID. However, this is a way of thinking and true for most ID schemes ... it all depends on how you choose to manage your identifiers. My excursion into the world of AAF has taught me a lot about comprehensive techniques for structuring and managing IDs for, and relationships between, all kinds of different media material. Most of what AAF is about is structural metadata, how one thing relates to another in a package, along a timeline, encoded with a particular codec etc.. This allows you to trace relationships between content through its various authoring stages back to its original source, a kind of super edit decision list. Structural metadata can be enhanced with descriptive metadata, normally using a schema of your own choosing as there is limited agreement between organisations about what this should be. So to build and expose your EverythingBrainz, perhaps what is needed is an API for exploring structural relationships between items of content, perhaps based on UUIDs, and an API for searching on descriptive metadata (actors, locations, scripts, awards) that may return results including related UUIDs? These APIs could be WSDL or ReSTful in style. For example, I personally think the musicbrainz example should be a location where you find out information about ³Blur² ... http://musixbrainz.org/artist/blur Where an item is currently published is really an item of descriptive metadata. Every generation of the page should have its own ID within a content management system and the published URL refers to the currently published version. The API I propose would allow you to find out the ID of the currently published version and, with appropriate permissions, to explore previous versions of the page via ID relationships. UUID, URL, maiden name, doesn¹t matter as long as the relationships are consistent. In summary, I believe that you could use many different ID schemes and many different descriptive metadata schemas. The important things are: understanding relationships between IDs are how they managed over time; how to map between the ontologies of the various different descriptive schema. Within an organisation such as the BBC, maybe what is most important in the first instance is a common set of principles for managing and publishing IDs rather than a one size fits all system? Cheers, Richard On 4/3/08 23:17, Chris Sizemore [EMAIL PROTECTED] wrote: cool stuff richard. so how do/should we expose GUIDs to the outside world, in a sorta Web kind of way? cause it's not enough to just generate unique IDs internally, we also have to broadcast their, um, meaning to the world at large... in other words, seems like you need the ID, some metadata to describe the thing ID'd, and a publishing/broadcasting mechanism so that other people/systems know you have info to communicate. a la: http://musicbrainz.org/artist/ba853904-ae25-4ebb-89d6-c44cfbd71bd2.html sounds like the Web to me... and MusicBrainz, for instance, is an example of all of the above, no? but now, don't we need an EverythingBrainz (as a colleague of mine recently put it)? (BTW, i'm a person that feels that URLs, by definition, are GUIDs) best-- --cs -Original Message- From: [EMAIL PROTECTED] on behalf of Richard Cartwright Sent: Tue 3/4/2008 5:31 PM To: BBC Backstage Subject: Re: [backstage] What would you love to see coming out of BBC Vision in the near future? Chris I¹ve a lot of recent experience with 16-byte UUIDs for identifying content (RFC 4122) and the slightly more media-savy 32-byte Unique Material Identification (UMID) from SMPTE (SMPTE 330M). Both standards are the basis for the Advanced Authoring Format, an industry standard used by video production tools from companies such as Avid and Quantel, and the related Material Exchange Format (MXF) used for production material interchange and now supported by a number of broadcast quality cameras, transcoders etc.. UUIDs are also known as GUIDs and are common to Microsoft Windows OS. Many unix OSs have a ³uuidgen² command to create UUIDs. Java has a ³java.util.UUID² class for generating and representing UUIDs. UUIDs are very well supported and have been the subject of some interesting security issues as without careful use they can expose your host ids outside your network. I am working on a media-specific Java API for AAF and MXF that includes support for UUIDs and UMIDs. Both can be generated at source and, as long as a
Re: [backstage] What would you love to see coming out of BBC Vision in the near future?
Yes I see the odd one out :) Tim Dobson wrote: Ian Forrester wrote: I was hoping to get a brainstorm of ideas for APIs and Feeds you would love to play with in the near future, while focusing on Vision/TV After Barcamp I think there are a few ideas in a more generally direction, not just about feeds and API's... Anything more? - Free Software Orientated Stuff - Open Standards Orientated Stuff - Freely Licenced Stuff - Stuff that works Up North - Stuff that I need Vista + Digital Restrictions Management(DRM) to use See if you can spot the one I put in to test whether you were awake :P Bet you could see those coming ;) - 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] What would you love to see coming out of BBC Vision in the near future?
Yes awesome Matthew! Phil Wilson wrote: I knocked up a little unsophisticated something: http://www.dracos.co.uk/play/bbc-iplayer-quick/ :-) This is ace, thanks Matthew. Phil - 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/
Re: [backstage] What would you love to see coming out of BBC Vision in the near future?
I like the idea of this, hard sell but who knows maybe a prototype could bring this to life. David Greaves wrote: Ian Forrester wrote: Hi All, I was hoping to get a brainstorm of ideas for APIs and Feeds you would love to play with in the near future, while focusing on Vision/TV I got most of the obvious stuff like, - A reference page or service for all programmes (/programmes in XML) - keywords Anything more? I'm not sure of the scope of the above points... Given concepts like crossover and product placement it may be worth looking at in-program timing of generic 'objects'. eg: 25:00-26:23 Music: Band:Ah-ha Track:Take On Me Album:... 25:00-26:23 Actor: Bruce Lee Character: Benny 25:00-26:23 Product: Coca Cola 25:00-26:23 Actual Location : Slough GPS-coords:39729358734652 25:00-26:23 Fictional Location : Monaco for *that* famous scene :) This does not need to be commercial - I could see it being used to identify concepts in educational material too. Who does this? Well, collaborative approaches could be used (FreeDB/CDDB worked), some companies would provide product/media info (would need guidelines), some programme makers would find it added value (education) - heck maybe an actor's agent would provide the data as part of the service (or the actor themselves if they were on the 'bronze' package ;) ) Clearly this works when it's about providing meta-information rather than links to a page. Those come from the apps using the meta-data. Tied to this (and many of the other points raised) would be a UUID system for uniquely identifying objects, resolving duplicates and possibly establishing relationships. Clearly one or two minor issues to resolve but... David - 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/
Re: [backstage] What would you love to see coming out of BBC Vision in the near future?
How about an Air app that allows one to edit the DMI metadata in a web browser. If there were a published BBC metadata schema we could do this outside the BBC; as it is it would need to be an internal effort. On 05/03/2008 06:38, Chris Sizemore [EMAIL PROTECTED] wrote: any BBC DMI guys lurking on the list? Rupert Watson www.root6.com +44 7787 554 801 ROOT 6 LIMITED Registered in the UK at 4 WARDOUR MEWS, LONDON W1F 8AJ Company No. 03433253 - 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] What would you love to see coming out of BBC Vision in the near future?
Mr I Forrester wrote: I like the idea of this, hard sell but who knows maybe a prototype could bring this to life. It might be nice to see something like the BBC Annotatable Audio project that the BBC Radio Music Interactive RD team worked on back in 2005, but on the iPlayer stream. e.g. a prototype could see a greasemonkey script which paused the video (if possible) and allowed the viewer to add a text annotation (and UUID reference if available) to what was happening on screen. Tom Coates posted some screenshots and video for how Annotatable Audio worked: http://www.plasticbag.org/archives/2005/10/on_the_bbc_annotatable_audio_project/ I guess I'm talking about something like Annodex, but for iPlayer content. http://www.annodex.net/ Phil - 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] What would you love to see coming out of BBC Vision in the near future?
Thanks to everyone who answered, some really interesting thoughts for DMI and other advanced prototypes. I'm presenting your ideas on Friday, so this is what I have across two slides In-programme timing of generic objects or people Access to the Edit logs of programme makers Access to the scripts with timings TV schedules as a API with past and future ability Direct links to iplayer programmes XML of upcoming iplayer programmes XML of programmes about to drop off iplayer (see Matthews prototype next slide) Links between programmes and their programme catalogue entry The Programme Catalogue and synced with DBpedia A reference page or service for all programmes (/programmes in XML) Small image/icon per programme with the rights cleared XML or pub/sub messages for upcoming and favourite programmes Ability to link BBC identity with favourite programmes Keywords, Tags and Search across them and other data Access to Subtitle data in XML Videos in alternative formats Wmv, Theora, Dirac, etc I'm going to spend at least 25% of my presentation on these points alone. Who knows maybe they will sink in and we might get some traction in certain areas. Cheers, Ian Ian Forrester wrote: Hi All, I was hoping to get a brainstorm of ideas for APIs and Feeds you would love to play with in the near future, while focusing on Vision/TV I got most of the obvious stuff like, - A 31 day schedule in XML - TV schedules as a API with past and future ability - Direct links to iplayer programmes - XML/RSS/ATOM/JSON of upcoming iplayer programmes - XML/RSS/ATOM/JSON of programmes about to drop off iplayer - Links between programmes and their programme catalogue entry - The Programme Catalogue! :) - A reference page or service for all programmes (/programmes in XML) - XMPP pub/sub messages for upcoming programmes - keywords Anything more? Ian Forrester This e-mail is: [x] private; [] ask first; [] bloggable Senior Producer, BBC Backstage BC5 C3, Media Village, 201 Wood Lane, London W12 7TP email: [EMAIL PROTECTED] work: +44 (0)2080083965 mob: +44 (0)7711913293 - 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/
Re: [backstage] What would you love to see coming out of BBC Vision in the near future?
Just a list of what we're planning in /programmes world: In-programme timing of generic objects or people in the first instance just for music content - in the future possible tagging of programme segments as interviews with people, profiles of, recipes, news stories etc TV schedules as a API with past and future ability So soon you wouldn't believe Direct links to iplayer programmes Soon XML of upcoming iplayer programmes Not properly considered but we should do yes XML of programmes about to drop off iplayer (see Matthews prototype next slide) Ditto Links between programmes and their programme catalogue entry Not soon but hopefully not too distant either The Programme Catalogue and synced with Dbpedia Now you're talking - we hope to provide /programmes as linked open data soon - linking to dbpedia still to be solved - see chris sizemore emails A reference page or service for all programmes (/programmes in XML) Soon XML or pub/sub messages for upcoming and favourite programmes Xml soon for upcoming Ability to link BBC identity with favourite programmes One day Keywords, Tags and Search across them and other data Soon On 5/3/08 12:09, Mr I Forrester [EMAIL PROTECTED] wrote: Thanks to everyone who answered, some really interesting thoughts for DMI and other advanced prototypes. I'm presenting your ideas on Friday, so this is what I have across two slides In-programme timing of generic objects or people Access to the Edit logs of programme makers Access to the scripts with timings TV schedules as a API with past and future ability Direct links to iplayer programmes XML of upcoming iplayer programmes XML of programmes about to drop off iplayer (see Matthews prototype next slide) Links between programmes and their programme catalogue entry The Programme Catalogue and synced with DBpedia A reference page or service for all programmes (/programmes in XML) Small image/icon per programme with the rights cleared XML or pub/sub messages for upcoming and favourite programmes Ability to link BBC identity with favourite programmes Keywords, Tags and Search across them and other data Access to Subtitle data in XML Videos in alternative formats Wmv, Theora, Dirac, etc I'm going to spend at least 25% of my presentation on these points alone. Who knows maybe they will sink in and we might get some traction in certain areas. Cheers, Ian Ian Forrester wrote: Hi All, I was hoping to get a brainstorm of ideas for APIs and Feeds you would love to play with in the near future, while focusing on Vision/TV I got most of the obvious stuff like, - A 31 day schedule in XML - TV schedules as a API with past and future ability - Direct links to iplayer programmes - XML/RSS/ATOM/JSON of upcoming iplayer programmes - XML/RSS/ATOM/JSON of programmes about to drop off iplayer - Links between programmes and their programme catalogue entry - The Programme Catalogue! :) - A reference page or service for all programmes (/programmes in XML) - XMPP pub/sub messages for upcoming programmes - keywords Anything more? Ian Forrester This e-mail is: [x] private; [] ask first; [] bloggable Senior Producer, BBC Backstage BC5 C3, Media Village, 201 Wood Lane, London W12 7TP email: [EMAIL PROTECTED] work: +44 (0)2080083965 mob: +44 (0)7711913293 - 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/
RE: [backstage] What would you love to see coming out of BBC Vision in the near future?
Sorry Chris, missed your reply. I'm no SPARQL expert but storing some additional contextual info in tuples in-house shouldn't require overhauling how things currently work. More media pipelines are quietly syphoning off stuff, into semantic knowledge stores, as a byproduct of regular publishing. I'd certainly recommend an iterative approach rather than keeping everything under wraps till some uber (BBC3.0?? ;) solution is available. Drafting ontologies, publishing static RDF files from current systems, could help get the ball rolling because early adoptors like us could independently pilot and feedback what data mining is and isn't that useful to storytellers. Cheers .M. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Sizemore Sent: 05 March 2008 18:03 To: backstage@lists.bbc.co.uk; backstage@lists.bbc.co.uk Subject: RE: [backstage] What would you love to see coming out of BBC Vision in the near future? oh, but you mention SPARQL queries, so doesn't that mean that we'd need full resource/RDF/URIs approach at least internally at the Beeb? or at least the capability and internal structure and data model in place internally to publish our data out to the world at a SPARQL end-point? to really offer SPARQL GUIDs are probably neither here nor there, but we'd need to do pretty well with URIs, no? personally, i liked the suggestion earlier to use dBpedia.org URIs as a starter lingua franca of URIs... clearly that wouldn't be relevant for IDing many of the resources pertinent to the editing suite, but even there it'd be relevant for some (people the video clip was about, etc) best-- --cs -Original Message- From: Chris Sizemore Sent: Wed 3/5/2008 6:38 AM To: backstage@lists.bbc.co.uk; backstage@lists.bbc.co.uk Subject: RE: [backstage] What would you love to see coming out of BBC Vision in the near future? wow, now that's a cool idea. any BBC DMI guys lurking on the list? -Original Message- From: [EMAIL PROTECTED] on behalf of Michela Ledwidge Sent: Wed 3/5/2008 1:08 AM To: backstage@lists.bbc.co.uk Subject: Re: [backstage] What would you love to see coming out of BBC Vision in the near future? BBC Vision edit log data would be good. Lots of useful meta-data there. As for getting the meaning out there. GUIDs might be less important than being able to perform semantic queries on whatever naming conventions exist already around the Beeb. e.g. creating a pool of edit log data and opening it up for SPARQL queries would perhaps be very useful. Not necessarily that useful having a particular tape ID as a GUID The ability to run queries over film/video logs, typically only viewed by editors, would no doubt reveal gems for repurposing and redistribution, let along allowing the Beeb to track and re-use source material better. Cheers .M. On Wed, Mar 5, 2008 at 10:17 AM, Chris Sizemore [EMAIL PROTECTED] wrote: cool stuff richard. so how do/should we expose GUIDs to the outside world, in a sorta Web kind of way? cause it's not enough to just generate unique IDs internally, we also have to broadcast their, um, meaning to the world at large... in other words, seems like you need the ID, some metadata to describe the thing ID'd, and a publishing/broadcasting mechanism so that other people/systems know you have info to communicate. a la: HYPERLINK http://musicbrainz.org/artist/ba853904-ae25-4ebb-89d6-c44cfbd71bd2.htmlhtt p://musicbrainz.org/artist/ba853904-ae25-4ebb-89d6-c44cfbd71bd2.html sounds like the Web to me... and MusicBrainz, for instance, is an example of all of the above, no? but now, don't we need an EverythingBrainz (as a colleague of mine recently put it)? (BTW, i'm a person that feels that URLs, by definition, are GUIDs) best-- --cs -Original Message- From: [EMAIL PROTECTED] on behalf of Richard Cartwright Sent: Tue 3/4/2008 5:31 PM To: BBC Backstage Subject: Re: [backstage] What would you love to see coming out of BBC Vision in the near future? Chris I¹ve a lot of recent experience with 16-byte UUIDs for identifying content (RFC 4122) and the slightly more media-savy 32-byte Unique Material Identification (UMID) from SMPTE (SMPTE 330M). Both standards are the basis for the Advanced Authoring Format, an industry standard used by video production tools from companies such as Avid and Quantel, and the related Material Exchange Format (MXF) used for production material interchange and now supported by a number of broadcast quality cameras, transcoders etc.. UUIDs are also known as GUIDs and are common to Microsoft Windows OS. Many unix OSs have a ³uuidgen² command to create UUIDs. Java has a ³java.util.UUID² class for generating and representing UUIDs. UUIDs are very well supported and have been the subject of some interesting security issues as without careful use they can expose your host ids outside your network. I am working on a media-specific
Re: [backstage] What would you love to see coming out of BBC Vision in the near future?
On 03/03/2008, Ian Forrester [EMAIL PROTECTED] wrote: Hi All, I was hoping to get a brainstorm of ideas for APIs and Feeds you would love to play with in the near future, while focusing on Vision/TV I got most of the obvious stuff like, - A 31 day schedule in XML - TV schedules as a API with past and future ability - Direct links to iplayer programmes - XML/RSS/ATOM/JSON of upcoming iplayer programmes - XML/RSS/ATOM/JSON of programmes about to drop off iplayer - Links between programmes and their programme catalogue entry - The Programme Catalogue! :) - A reference page or service for all programmes (/programmes in XML) - XMPP pub/sub messages for upcoming programmes - keywords Anything more? Either a feed of the text used for subtitles, or at least a search API that takes terms and returns the ID and time offset of the programme containing the search text. It would be handy for programme Astons to be searchable in this way. The idea would be that could could do a text search for a name or phrase and then link directly to the content using the Flash iPlayer. Ian Forrester This e-mail is: [x] private; [] ask first; [] bloggable Senior Producer, BBC Backstage BC5 C3, Media Village, 201 Wood Lane, London W12 7TP email: [EMAIL PROTECTED] work: +44 (0)2080083965 mob: +44 (0)7711913293 - 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/ -- Please email me back if you need any more help. Brian Butterworth http://www.ukfree.tv
Re: [backstage] What would you love to see coming out of BBC Vision in the near future?
Ian Forrester wrote: - XML/RSS/ATOM/JSON of programmes about to drop off iplayer I knocked up a little unsophisticated something: http://www.dracos.co.uk/play/bbc-iplayer-quick/ :-) You can restrict to a particular title or part of title by adding it to the end of the URL, e.g. http://www.dracos.co.uk/play/bbc-iplayer-quick/rss/candleford ATB, Matthew - 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] What would you love to see coming out of BBC Vision in the near future?
I knocked up a little unsophisticated something: http://www.dracos.co.uk/play/bbc-iplayer-quick/ :-) This is ace, thanks Matthew. Phil - 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] What would you love to see coming out of BBC Vision in the near future?
- A 31 day schedule in XML - TV schedules as a API with past and future ability - Direct links to iplayer programmes - XML/RSS/ATOM/JSON of upcoming iplayer programmes - XML/RSS/ATOM/JSON of programmes about to drop off iplayer - Links between programmes and their programme catalogue entry - The Programme Catalogue! :) - A reference page or service for all programmes (/programmes in XML) - XMPP pub/sub messages for upcoming programmes in worst case, this could be generated from the other content Anything more? I'd like to be able to tie some of this to my BBC username/password so I can mark favourite TV shows and get notification that a new ep is on iPlayer via email/rss/atom :) Phil - 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] What would you love to see coming out of BBC Vision in the near future?
Ian Forrester wrote: Hi All, I was hoping to get a brainstorm of ideas for APIs and Feeds you would love to play with in the near future, while focusing on Vision/TV I got most of the obvious stuff like, - A reference page or service for all programmes (/programmes in XML) - keywords Anything more? I'm not sure of the scope of the above points... Given concepts like crossover and product placement it may be worth looking at in-program timing of generic 'objects'. eg: 25:00-26:23 Music: Band:Ah-ha Track:Take On Me Album:... 25:00-26:23 Actor: Bruce Lee Character: Benny 25:00-26:23 Product: Coca Cola 25:00-26:23 Actual Location : Slough GPS-coords:39729358734652 25:00-26:23 Fictional Location : Monaco for *that* famous scene :) This does not need to be commercial - I could see it being used to identify concepts in educational material too. Who does this? Well, collaborative approaches could be used (FreeDB/CDDB worked), some companies would provide product/media info (would need guidelines), some programme makers would find it added value (education) - heck maybe an actor's agent would provide the data as part of the service (or the actor themselves if they were on the 'bronze' package ;) ) Clearly this works when it's about providing meta-information rather than links to a page. Those come from the apps using the meta-data. Tied to this (and many of the other points raised) would be a UUID system for uniquely identifying objects, resolving duplicates and possibly establishing relationships. Clearly one or two minor issues to resolve but... David - 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] What would you love to see coming out of BBC Vision in the near future?
anyone got any thoughts or experiences with the UUID system for uniquely identifying objects mentioned below? in our collective opinion and experience, is there anything like that, or close to that, in existence yet? does MusicBrainz qualify in terms of Music object identification and IDs? best-- --cs -Original Message- From: [EMAIL PROTECTED] on behalf of David Greaves Sent: Tue 3/4/2008 12:23 PM To: backstage@lists.bbc.co.uk Subject: Re: [backstage] What would you love to see coming out of BBC Vision in the near future? Ian Forrester wrote: Hi All, I was hoping to get a brainstorm of ideas for APIs and Feeds you would love to play with in the near future, while focusing on Vision/TV I got most of the obvious stuff like, - A reference page or service for all programmes (/programmes in XML) - keywords Anything more? I'm not sure of the scope of the above points... Given concepts like crossover and product placement it may be worth looking at in-program timing of generic 'objects'. eg: 25:00-26:23 Music: Band:Ah-ha Track:Take On Me Album:... 25:00-26:23 Actor: Bruce Lee Character: Benny 25:00-26:23 Product: Coca Cola 25:00-26:23 Actual Location : Slough GPS-coords:39729358734652 25:00-26:23 Fictional Location : Monaco for *that* famous scene :) This does not need to be commercial - I could see it being used to identify concepts in educational material too. Who does this? Well, collaborative approaches could be used (FreeDB/CDDB worked), some companies would provide product/media info (would need guidelines), some programme makers would find it added value (education) - heck maybe an actor's agent would provide the data as part of the service (or the actor themselves if they were on the 'bronze' package ;) ) Clearly this works when it's about providing meta-information rather than links to a page. Those come from the apps using the meta-data. Tied to this (and many of the other points raised) would be a UUID system for uniquely identifying objects, resolving duplicates and possibly establishing relationships. Clearly one or two minor issues to resolve but... David - 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] What would you love to see coming out of BBC Vision in the near future?
On 03/03/2008, Ian Forrester [EMAIL PROTECTED] wrote: - XML/RSS/ATOM/JSON of upcoming iplayer programmes - XML/RSS/ATOM/JSON of programmes about to drop off iplayer How about a full iPlayer API so we can actually create programs that use that data? Screen scraping is hugely inefficient, to get a list of all iPlayer programs and their details would take hundreds of page requests using screen scraping. Links to products relevant to programs in the API would be useful, e.g. a link to the DVD of the series, however I think the Trust would be a bit upset if you tried linking to Amazon or something similar (might get away with a reference to the BBC shop though). Of course if there are books that accompany the series then you could list an ISBN, and it's not interfering with commercial markets as all book shops can use ISBNs! (OT: Do DVDs and CDs etc. have an equivalent of an ISBN? Should TV programs themselves have some kind of globally unique identifier? If so who do we get to assign such identifiers?) And iPlayer video/streaming in a format/protocol programs can actually use would be nice, how about Dirac than Kamaelia would be able to play it[1]? And the obligatory Moon on a stick, see previous implementation[2] courtesy of PuTTY[3]. Andy [1] http://kamaelia.sourceforge.net/Components/pydoc/Kamaelia.Codec.Dirac.html [2] http://www.chiark.greenend.org.uk/~sgtatham/moon-on-stick.jpeg [3] http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/moon-on-stick.html -- Computers are like air conditioners. Both stop working, if you open windows. -- Adam Heath - 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] What would you love to see coming out of BBC Vision in the near future?
Chris I¹ve a lot of recent experience with 16-byte UUIDs for identifying content (RFC 4122) and the slightly more media-savy 32-byte Unique Material Identification (UMID) from SMPTE (SMPTE 330M). Both standards are the basis for the Advanced Authoring Format, an industry standard used by video production tools from companies such as Avid and Quantel, and the related Material Exchange Format (MXF) used for production material interchange and now supported by a number of broadcast quality cameras, transcoders etc.. UUIDs are also known as GUIDs and are common to Microsoft Windows OS. Many unix OSs have a ³uuidgen² command to create UUIDs. Java has a ³java.util.UUID² class for generating and representing UUIDs. UUIDs are very well supported and have been the subject of some interesting security issues as without careful use they can expose your host ids outside your network. I am working on a media-specific Java API for AAF and MXF that includes support for UUIDs and UMIDs. Both can be generated at source and, as long as a consistent generation strategy is used, should be globally unique. Richard On 4/3/08 12:40, Chris Sizemore [EMAIL PROTECTED] wrote: anyone got any thoughts or experiences with the UUID system for uniquely identifying objects mentioned below? in our collective opinion and experience, is there anything like that, or close to that, in existence yet? -- Dr Richard Cartwright media systems architect portability4media.com [EMAIL PROTECTED] mobile +44 (0)7792 799930
Re: [backstage] What would you love to see coming out of BBC Vision in the near future?
Clearly one or two minor issues to resolve but... lol! :) - 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] What would you love to see coming out of BBC Vision in the near future?
cool stuff richard. so how do/should we expose GUIDs to the outside world, in a sorta Web kind of way? cause it's not enough to just generate unique IDs internally, we also have to broadcast their, um, meaning to the world at large... in other words, seems like you need the ID, some metadata to describe the thing ID'd, and a publishing/broadcasting mechanism so that other people/systems know you have info to communicate. a la: http://musicbrainz.org/artist/ba853904-ae25-4ebb-89d6-c44cfbd71bd2.html sounds like the Web to me... and MusicBrainz, for instance, is an example of all of the above, no? but now, don't we need an EverythingBrainz (as a colleague of mine recently put it)? (BTW, i'm a person that feels that URLs, by definition, are GUIDs) best-- --cs -Original Message- From: [EMAIL PROTECTED] on behalf of Richard Cartwright Sent: Tue 3/4/2008 5:31 PM To: BBC Backstage Subject: Re: [backstage] What would you love to see coming out of BBC Vision in the near future? Chris I¹ve a lot of recent experience with 16-byte UUIDs for identifying content (RFC 4122) and the slightly more media-savy 32-byte Unique Material Identification (UMID) from SMPTE (SMPTE 330M). Both standards are the basis for the Advanced Authoring Format, an industry standard used by video production tools from companies such as Avid and Quantel, and the related Material Exchange Format (MXF) used for production material interchange and now supported by a number of broadcast quality cameras, transcoders etc.. UUIDs are also known as GUIDs and are common to Microsoft Windows OS. Many unix OSs have a ³uuidgen² command to create UUIDs. Java has a ³java.util.UUID² class for generating and representing UUIDs. UUIDs are very well supported and have been the subject of some interesting security issues as without careful use they can expose your host ids outside your network. I am working on a media-specific Java API for AAF and MXF that includes support for UUIDs and UMIDs. Both can be generated at source and, as long as a consistent generation strategy is used, should be globally unique. Richard On 4/3/08 12:40, Chris Sizemore [EMAIL PROTECTED] wrote: anyone got any thoughts or experiences with the UUID system for uniquely identifying objects mentioned below? in our collective opinion and experience, is there anything like that, or close to that, in existence yet? -- Dr Richard Cartwright media systems architect portability4media.com [EMAIL PROTECTED] mobile +44 (0)7792 799930
Re: [backstage] What would you love to see coming out of BBC Vision in the near future?
BBC Vision edit log data would be good. Lots of useful meta-data there. As for getting the meaning out there. GUIDs might be less important than being able to perform semantic queries on whatever naming conventions exist already around the Beeb. e.g. creating a pool of edit log data and opening it up for SPARQL queries would perhaps be very useful. Not necessarily that useful having a particular tape ID as a GUID The ability to run queries over film/video logs, typically only viewed by editors, would no doubt reveal gems for repurposing and redistribution, let along allowing the Beeb to track and re-use source material better. Cheers .M. On Wed, Mar 5, 2008 at 10:17 AM, Chris Sizemore [EMAIL PROTECTED] wrote: cool stuff richard. so how do/should we expose GUIDs to the outside world, in a sorta Web kind of way? cause it's not enough to just generate unique IDs internally, we also have to broadcast their, um, meaning to the world at large... in other words, seems like you need the ID, some metadata to describe the thing ID'd, and a publishing/broadcasting mechanism so that other people/systems know you have info to communicate. a la: http://musicbrainz.org/artist/ba853904-ae25-4ebb-89d6-c44cfbd71bd2.html sounds like the Web to me... and MusicBrainz, for instance, is an example of all of the above, no? but now, don't we need an EverythingBrainz (as a colleague of mine recently put it)? (BTW, i'm a person that feels that URLs, by definition, are GUIDs) best-- --cs -Original Message- From: [EMAIL PROTECTED] on behalf of Richard Cartwright Sent: Tue 3/4/2008 5:31 PM To: BBC Backstage Subject: Re: [backstage] What would you love to see coming out of BBC Vision in the near future? Chris I¹ve a lot of recent experience with 16-byte UUIDs for identifying content (RFC 4122) and the slightly more media-savy 32-byte Unique Material Identification (UMID) from SMPTE (SMPTE 330M). Both standards are the basis for the Advanced Authoring Format, an industry standard used by video production tools from companies such as Avid and Quantel, and the related Material Exchange Format (MXF) used for production material interchange and now supported by a number of broadcast quality cameras, transcoders etc.. UUIDs are also known as GUIDs and are common to Microsoft Windows OS. Many unix OSs have a ³uuidgen² command to create UUIDs. Java has a ³java.util.UUID² class for generating and representing UUIDs. UUIDs are very well supported and have been the subject of some interesting security issues as without careful use they can expose your host ids outside your network. I am working on a media-specific Java API for AAF and MXF that includes support for UUIDs and UMIDs. Both can be generated at source and, as long as a consistent generation strategy is used, should be globally unique. Richard On 4/3/08 12:40, Chris Sizemore [EMAIL PROTECTED] wrote: anyone got any thoughts or experiences with the UUID system for uniquely identifying objects mentioned below? in our collective opinion and experience, is there anything like that, or close to that, in existence yet? -- Dr Richard Cartwright media systems architect portability4media.com [EMAIL PROTECTED] mobile +44 (0)7792 799930 -- MOD Films http://modfilms.com +44 208 144 8981 (UK) +61 2 8003 4811 (AU)
RE: [backstage] What would you love to see coming out of BBC Vision in the near future?
wow, now that's a cool idea. any BBC DMI guys lurking on the list? -Original Message- From: [EMAIL PROTECTED] on behalf of Michela Ledwidge Sent: Wed 3/5/2008 1:08 AM To: backstage@lists.bbc.co.uk Subject: Re: [backstage] What would you love to see coming out of BBC Vision in the near future? BBC Vision edit log data would be good. Lots of useful meta-data there. As for getting the meaning out there. GUIDs might be less important than being able to perform semantic queries on whatever naming conventions exist already around the Beeb. e.g. creating a pool of edit log data and opening it up for SPARQL queries would perhaps be very useful. Not necessarily that useful having a particular tape ID as a GUID The ability to run queries over film/video logs, typically only viewed by editors, would no doubt reveal gems for repurposing and redistribution, let along allowing the Beeb to track and re-use source material better. Cheers .M. On Wed, Mar 5, 2008 at 10:17 AM, Chris Sizemore [EMAIL PROTECTED] wrote: cool stuff richard. so how do/should we expose GUIDs to the outside world, in a sorta Web kind of way? cause it's not enough to just generate unique IDs internally, we also have to broadcast their, um, meaning to the world at large... in other words, seems like you need the ID, some metadata to describe the thing ID'd, and a publishing/broadcasting mechanism so that other people/systems know you have info to communicate. a la: http://musicbrainz.org/artist/ba853904-ae25-4ebb-89d6-c44cfbd71bd2.html sounds like the Web to me... and MusicBrainz, for instance, is an example of all of the above, no? but now, don't we need an EverythingBrainz (as a colleague of mine recently put it)? (BTW, i'm a person that feels that URLs, by definition, are GUIDs) best-- --cs -Original Message- From: [EMAIL PROTECTED] on behalf of Richard Cartwright Sent: Tue 3/4/2008 5:31 PM To: BBC Backstage Subject: Re: [backstage] What would you love to see coming out of BBC Vision in the near future? Chris I¹ve a lot of recent experience with 16-byte UUIDs for identifying content (RFC 4122) and the slightly more media-savy 32-byte Unique Material Identification (UMID) from SMPTE (SMPTE 330M). Both standards are the basis for the Advanced Authoring Format, an industry standard used by video production tools from companies such as Avid and Quantel, and the related Material Exchange Format (MXF) used for production material interchange and now supported by a number of broadcast quality cameras, transcoders etc.. UUIDs are also known as GUIDs and are common to Microsoft Windows OS. Many unix OSs have a ³uuidgen² command to create UUIDs. Java has a ³java.util.UUID² class for generating and representing UUIDs. UUIDs are very well supported and have been the subject of some interesting security issues as without careful use they can expose your host ids outside your network. I am working on a media-specific Java API for AAF and MXF that includes support for UUIDs and UMIDs. Both can be generated at source and, as long as a consistent generation strategy is used, should be globally unique. Richard On 4/3/08 12:40, Chris Sizemore [EMAIL PROTECTED] wrote: anyone got any thoughts or experiences with the UUID system for uniquely identifying objects mentioned below? in our collective opinion and experience, is there anything like that, or close to that, in existence yet? -- Dr Richard Cartwright media systems architect portability4media.com [EMAIL PROTECTED] mobile +44 (0)7792 799930 -- MOD Films http://modfilms.com +44 208 144 8981 (UK) +61 2 8003 4811 (AU)
RE: [backstage] What would you love to see coming out of BBC Vision in the near future?
oh, but you mention SPARQL queries, so doesn't that mean that we'd need full resource/RDF/URIs approach at least internally at the Beeb? or at least the capability and internal structure and data model in place internally to publish our data out to the world at a SPARQL end-point? to really offer SPARQL GUIDs are probably neither here nor there, but we'd need to do pretty well with URIs, no? personally, i liked the suggestion earlier to use dBpedia.org URIs as a starter lingua franca of URIs... clearly that wouldn't be relevant for IDing many of the resources pertinent to the editing suite, but even there it'd be relevant for some (people the video clip was about, etc) best-- --cs -Original Message- From: Chris Sizemore Sent: Wed 3/5/2008 6:38 AM To: backstage@lists.bbc.co.uk; backstage@lists.bbc.co.uk Subject: RE: [backstage] What would you love to see coming out of BBC Vision in the near future? wow, now that's a cool idea. any BBC DMI guys lurking on the list? -Original Message- From: [EMAIL PROTECTED] on behalf of Michela Ledwidge Sent: Wed 3/5/2008 1:08 AM To: backstage@lists.bbc.co.uk Subject: Re: [backstage] What would you love to see coming out of BBC Vision in the near future? BBC Vision edit log data would be good. Lots of useful meta-data there. As for getting the meaning out there. GUIDs might be less important than being able to perform semantic queries on whatever naming conventions exist already around the Beeb. e.g. creating a pool of edit log data and opening it up for SPARQL queries would perhaps be very useful. Not necessarily that useful having a particular tape ID as a GUID The ability to run queries over film/video logs, typically only viewed by editors, would no doubt reveal gems for repurposing and redistribution, let along allowing the Beeb to track and re-use source material better. Cheers .M. On Wed, Mar 5, 2008 at 10:17 AM, Chris Sizemore [EMAIL PROTECTED] wrote: cool stuff richard. so how do/should we expose GUIDs to the outside world, in a sorta Web kind of way? cause it's not enough to just generate unique IDs internally, we also have to broadcast their, um, meaning to the world at large... in other words, seems like you need the ID, some metadata to describe the thing ID'd, and a publishing/broadcasting mechanism so that other people/systems know you have info to communicate. a la: http://musicbrainz.org/artist/ba853904-ae25-4ebb-89d6-c44cfbd71bd2.html sounds like the Web to me... and MusicBrainz, for instance, is an example of all of the above, no? but now, don't we need an EverythingBrainz (as a colleague of mine recently put it)? (BTW, i'm a person that feels that URLs, by definition, are GUIDs) best-- --cs -Original Message- From: [EMAIL PROTECTED] on behalf of Richard Cartwright Sent: Tue 3/4/2008 5:31 PM To: BBC Backstage Subject: Re: [backstage] What would you love to see coming out of BBC Vision in the near future? Chris I¹ve a lot of recent experience with 16-byte UUIDs for identifying content (RFC 4122) and the slightly more media-savy 32-byte Unique Material Identification (UMID) from SMPTE (SMPTE 330M). Both standards are the basis for the Advanced Authoring Format, an industry standard used by video production tools from companies such as Avid and Quantel, and the related Material Exchange Format (MXF) used for production material interchange and now supported by a number of broadcast quality cameras, transcoders etc.. UUIDs are also known as GUIDs and are common to Microsoft Windows OS. Many unix OSs have a ³uuidgen² command to create UUIDs. Java has a ³java.util.UUID² class for generating and representing UUIDs. UUIDs are very well supported and have been the subject of some interesting security issues as without careful use they can expose your host ids outside your network. I am working on a media-specific Java API for AAF and MXF that includes support for UUIDs and UMIDs. Both can be generated at source and, as long as a consistent generation strategy is used, should be globally unique. Richard On 4/3/08 12:40, Chris Sizemore [EMAIL PROTECTED] wrote: anyone got any thoughts or experiences with the UUID system for uniquely identifying objects mentioned below? in our collective opinion and experience, is there anything like that, or close to that, in existence yet? -- Dr Richard Cartwright media systems architect portability4media.com [EMAIL PROTECTED] mobile +44 (0)7792 799930 -- MOD Films http://modfilms.com +44 208 144 8981 (UK) +61 2 8003 4811 (AU)
[backstage] What would you love to see coming out of BBC Vision in the near future?
Hi All, I was hoping to get a brainstorm of ideas for APIs and Feeds you would love to play with in the near future, while focusing on Vision/TV I got most of the obvious stuff like, - A 31 day schedule in XML - TV schedules as a API with past and future ability - Direct links to iplayer programmes - XML/RSS/ATOM/JSON of upcoming iplayer programmes - XML/RSS/ATOM/JSON of programmes about to drop off iplayer - Links between programmes and their programme catalogue entry - The Programme Catalogue! :) - A reference page or service for all programmes (/programmes in XML) - XMPP pub/sub messages for upcoming programmes - keywords Anything more? Ian Forrester This e-mail is: [x] private; [] ask first; [] bloggable Senior Producer, BBC Backstage BC5 C3, Media Village, 201 Wood Lane, London W12 7TP email: [EMAIL PROTECTED] work: +44 (0)2080083965 mob: +44 (0)7711913293 - 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] What would you love to see coming out of BBC Vision in the near future?
can you get hold of subtitle data from broadcasts? That would be amazing! So many possibilities. Someone I know who's been working on video tagging software was telling me that broadcasters (like the beeb) use a similar system, and sometimes broadcast some of the meta data. Apparently they use it for tagging events in sports matches and use that for pulling together highlights quickly. I'm sure production staff at the bbc are adding all kinds of meta richness to their video content, it would be great to be able to open some of that up. Ian Forrester wrote: Hi All, I was hoping to get a brainstorm of ideas for APIs and Feeds you would love to play with in the near future, while focusing on Vision/TV I got most of the obvious stuff like, - A 31 day schedule in XML - TV schedules as a API with past and future ability - Direct links to iplayer programmes - XML/RSS/ATOM/JSON of upcoming iplayer programmes - XML/RSS/ATOM/JSON of programmes about to drop off iplayer - Links between programmes and their programme catalogue entry - The Programme Catalogue! :) - A reference page or service for all programmes (/programmes in XML) - XMPP pub/sub messages for upcoming programmes - keywords Anything more? Ian Forrester This e-mail is: [x] private; [] ask first; [] bloggable Senior Producer, BBC Backstage BC5 C3, Media Village, 201 Wood Lane, London W12 7TP email: [EMAIL PROTECTED] work: +44 (0)2080083965 mob: +44 (0)7711913293 - 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/ -- *** OPEN COFFEE 8 - http://upcoming.yahoo.com/event/421269/ *** Glow New Media t: 0151 707 9770 m: 07730 987 574 www.glow-internet.com Suite 712 Gostins Building 32-36 Hanover Street Liverpool L1 4LN Map: http://tinyurl.com/2f5nxd - 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] What would you love to see coming out of BBC Vision in the near future?
Maybe it's implicit in your list but it'd be great if there could be some kind of image per item in the feed. I'm thinking mostly of iPlayer schedule and having some kind of still from each show. Call me superficial but I think an rss feed is a much more attractive prospect to work with when you can use it to sprinkle a bit of imagery over your page/ flash app/ whatever. I realise rights, server load etc might be an issue here though of course. S. On Mon, Mar 3, 2008 at 7:13 PM, Ian Forrester [EMAIL PROTECTED] wrote: Hi All, I was hoping to get a brainstorm of ideas for APIs and Feeds you would love to play with in the near future, while focusing on Vision/TV I got most of the obvious stuff like, - A 31 day schedule in XML - TV schedules as a API with past and future ability - Direct links to iplayer programmes - XML/RSS/ATOM/JSON of upcoming iplayer programmes - XML/RSS/ATOM/JSON of programmes about to drop off iplayer - Links between programmes and their programme catalogue entry - The Programme Catalogue! :) - A reference page or service for all programmes (/programmes in XML) - XMPP pub/sub messages for upcoming programmes - keywords Anything more? Ian Forrester This e-mail is: [x] private; [] ask first; [] bloggable Senior Producer, BBC Backstage BC5 C3, Media Village, 201 Wood Lane, London W12 7TP email: [EMAIL PROTECTED] work: +44 (0)2080083965 mob: +44 (0)7711913293 - 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] What would you love to see coming out of BBC Vision in the near future?
On Mon, Mar 3, 2008 at 7:13 PM, Ian Forrester [EMAIL PROTECTED] wrote: Hi All, I was hoping to get a brainstorm of ideas for APIs and Feeds you would love to play with in the near future, while focusing on Vision/TV I got most of the obvious stuff like, - A 31 day schedule in XML - TV schedules as a API with past and future ability - Direct links to iplayer programmes - XML/RSS/ATOM/JSON of upcoming iplayer programmes - XML/RSS/ATOM/JSON of programmes about to drop off iplayer - Links between programmes and their programme catalogue entry - The Programme Catalogue! :) It'd be nice if the BBC could publish RDF of their whole programme catalogue and add it to the already growing sphere of Linked Open Data: http://esw.w3.org/topic/SweoIG/TaskForces/CommunityProjects/LinkingOpenData Hook the programmes in with parts of the diagram on the page - eg: - for all programmes, link them to the DBPedia resource for that programme if it exists on Wikipedia - for actors and presenters, link them to their DBPedia resource - for music programmes, link bands and songs in - for news and factual programmes, link them to online stories that cover the same story - for review programmes (like Newsnight Review), link in the relevant discussed books/authors/films/plays etc. - for things which happen in a particular place, link them into Geonames - for dramatic re-enactments, link them to what they were re-enacting (historical events, books, plays etc.) - in political coverage, link through to details about the relevant politicians and legislation Less hacking RSS and Atom to do things for which they were not intended (they are feed formats, not universal containers). -- Tom Morris http://tommorris.org/ - 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] What would you love to see coming out of BBC Vision in the near future?
sounds like a great plan, tom -- many of us inside the BBC are quite into dbpedia and linked data, so i think it's not out of the question to attempt what you suggest... here's an example of some work in that direction by my colleague michael smethurst: http://bbc-hackday.dyndns.org:2825/programmes/29xn (currently down, tho -- michael?) my followup question for you and the list, though, is this: what algorithms and methods exist to bootstrap the kind of linking you advocate? it's doubtful that we're going to be able to do all this linking, however valuable, by hand. i.e. what (semi-)automated methods exist for linking all the BBC programme catalogue resources to their corresponding dbpedia/wikipedia/musicbrainz et al resources? for instance, we should be linking: http://www.bbc.co.uk/programmes/b009070m perhaps http://www.bbc.co.uk/iplayer/page/item/b0091v4d.shtml to http://en.wikipedia.org/wiki/Find_Me_The_Face (or rather its dbpedia URI: http://dbpedia.org/resource/Find_Me_The_Face, i guess) but what ways exist to do this script-o-matically? thoughts? best-- --cs -Original Message- From: [EMAIL PROTECTED] on behalf of Tom Morris Sent: Mon 3/3/2008 8:37 PM To: backstage@lists.bbc.co.uk Subject: Re: [backstage] What would you love to see coming out of BBC Vision in the near future? On Mon, Mar 3, 2008 at 7:13 PM, Ian Forrester [EMAIL PROTECTED] wrote: Hi All, I was hoping to get a brainstorm of ideas for APIs and Feeds you would love to play with in the near future, while focusing on Vision/TV I got most of the obvious stuff like, - A 31 day schedule in XML - TV schedules as a API with past and future ability - Direct links to iplayer programmes - XML/RSS/ATOM/JSON of upcoming iplayer programmes - XML/RSS/ATOM/JSON of programmes about to drop off iplayer - Links between programmes and their programme catalogue entry - The Programme Catalogue! :) It'd be nice if the BBC could publish RDF of their whole programme catalogue and add it to the already growing sphere of Linked Open Data: http://esw.w3.org/topic/SweoIG/TaskForces/CommunityProjects/LinkingOpenData Hook the programmes in with parts of the diagram on the page - eg: - for all programmes, link them to the DBPedia resource for that programme if it exists on Wikipedia - for actors and presenters, link them to their DBPedia resource - for music programmes, link bands and songs in - for news and factual programmes, link them to online stories that cover the same story - for review programmes (like Newsnight Review), link in the relevant discussed books/authors/films/plays etc. - for things which happen in a particular place, link them into Geonames - for dramatic re-enactments, link them to what they were re-enacting (historical events, books, plays etc.) - in political coverage, link through to details about the relevant politicians and legislation Less hacking RSS and Atom to do things for which they were not intended (they are feed formats, not universal containers). -- Tom Morris http://tommorris.org/ - 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/ winmail.dat
Re: [backstage] What would you love to see coming out of BBC Vision in the near future?
Ian Forrester wrote: I was hoping to get a brainstorm of ideas for APIs and Feeds you would love to play with in the near future, while focusing on Vision/TV After Barcamp I think there are a few ideas in a more generally direction, not just about feeds and API's... Anything more? - Free Software Orientated Stuff - Open Standards Orientated Stuff - Freely Licenced Stuff - Stuff that works Up North - Stuff that I need Vista + Digital Restrictions Management(DRM) to use See if you can spot the one I put in to test whether you were awake :P Bet you could see those coming ;) -- www.blog.tdobson.net If each of us have one object, and we exchange them, then each of us still has one object. If each of us have one idea, and we exchange them, then each of us now has two ideas. - George Bernard Shaw - 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] What would you love to see coming out of BBC Vision in the near future?
On the back of Tim's suggestions about broadening the scope wider than just feeds, would it ever be possible to register for a dev account like youtube, delicious etc and get greater access to data in a way that tech bods at the BBC could 'control' more? S. On Mon, Mar 3, 2008 at 10:50 PM, Tim Dobson [EMAIL PROTECTED] wrote: Ian Forrester wrote: I was hoping to get a brainstorm of ideas for APIs and Feeds you would love to play with in the near future, while focusing on Vision/TV After Barcamp I think there are a few ideas in a more generally direction, not just about feeds and API's... Anything more? - Free Software Orientated Stuff - Open Standards Orientated Stuff - Freely Licenced Stuff - Stuff that works Up North - Stuff that I need Vista + Digital Restrictions Management(DRM) to use See if you can spot the one I put in to test whether you were awake :P Bet you could see those coming ;) -- www.blog.tdobson.net If each of us have one object, and we exchange them, then each of us still has one object. If each of us have one idea, and we exchange them, then each of us now has two ideas. - George Bernard Shaw - 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/
