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
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
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
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
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
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
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
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
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
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
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
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
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
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.
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.
- 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
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
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?
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
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
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/
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
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
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
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
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
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
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
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
-
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:
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?
-
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,
32 matches
Mail list logo
