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.html"htt
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 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
HYPERLINK "http://modfilms.com"http://modfilms.com
+44 208 144 8981 (UK)
+61 2 8003 4811 (AU)
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.516 / Virus Database: 269.21.4/1310 - Release Date: 04/03/2008
08:35
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.516 / Virus Database: 269.21.5/1314 - Release Date: 05/03/2008
18:38
