Ben O'Neill wrote:
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 ...
Not if you're delivering a CRI service via the digital TV network.
Which is the stuff I was working on. :-)
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.
Only if you think of a location URL as a key, not a value. It's
certainly convenient to be able to do so, and it can work well in a
web-centric world under circumstances where you can uniquely identify
content by its location. In general, URIs and URLs are different beasts
though, and for good reasons.
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.
Would it help if I suggested that (subject to the BBC running such a
service), a CRID could be converted to a valid URL by prepending it with
"http://www.bbc.co.uk/cridlookup/";? :-) In the meantime you'll have to
make do with
http://www0.rdthdo.bbc.co.uk/services/api/bbc.programme.getLocations.html
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/[email protected]/
