For those of you who don't know, this is an XML format for storing
"subtitles" or "captions" (if you're in the USA).
Also known as "closed captioning"
See:-
http://en.wikipedia.org/wiki/Closed_captioning
http://www.robson.org/capfaq/
Gordo
--
"Think Feynman"/
http://pobox.com
On Thu, 2005-09-15 at 11:39 +0100, Ben Metcalfe wrote:
> > So here's a thought : Supposing each broadcast program is
> > subtitled - most
> > are, to meet disability guidelines for deaf viewers. How
> > about publishing
> > the subtitle files as part of backstage, in W3C TT format
> > (maybe
At 09:47 15/09/2005 +0100, you wrote:
Could you also see if it's possible to review the names, the mix of
upper case and lower case etc make them
look really bad if you display them directly and having to manually
edit them is a pain!
I agree - the capitalised text represent top level genres b
At 10:23 15/09/2005 +0200, you wrote:
Are you just changing the genres or are you also introducing some 2004
elements with namespace and all? TVA's atrocious practice of changing
namespaces when they change versions could introduce all manners of
problems for implementations if the upgrade isn
Perhaps you could get around copyright issues by 'doing a Google' and launching a 'beta' service ;)
On 9/15/05, Hywel Williams <[EMAIL PROTECTED]> wrote:
At 11:15 15/09/2005 +0100, you wrote:>At 18:32 14/09/2005 +0100, you wrote:>>Some bug fixes and modifications have been made to the data set - th
At 11:15 15/09/2005 +0100, you wrote:
At 18:32 14/09/2005 +0100, you wrote:
Some bug fixes and modifications have been made to the data set - these
are outlined below.
2. When audio description is being provided for a programme, this is
indicated with an extra AudioAtrributes entry with an Au
> So here's a thought : Supposing each broadcast program is
> subtitled - most
> are, to meet disability guidelines for deaf viewers. How
> about publishing
> the subtitle files as part of backstage, in W3C TT format
> (maybe in the
> final draft format until the complete spec is ratified).
Neil Smith [MVP Digital Media] wrote:
Food for thought ?
That's a really nice idea. Obviously there could be a copyright problem,
but then if all the TV programmes are (eventually) going to be available
to download to us in the UK, why not?
--
From the North, this is Kirk
www.broadcastings
At 18:32 14/09/2005 +0100, you wrote:
Some bug fixes and modifications have been made to the data set - these
are outlined below.
2. When audio description is being provided for a programme, this is
indicated with an extra AudioAtrributes entry with an AudioLanguage
purpose of type 1 (Audio d
On 14 Sep 2005, at 18:32, Hywel Williams wrote:
Some forthcoming changes/issues.
1. It has been pointed out that the format of the DVB locator used
in the ContentReferencing Tables and the ProgramLocation tables
don't conform to the DVB standard! Essentially the divider between
the date
Hywel Williams wrote:
1. The character set being used is now correctly identified as
ISO-8859-9. This was always the case but the ISO-8859-1 ident was
incorrectly displayed.
Really? Isn't -9 Turkish? Why not use UTF-8 and be safe no matter what
happens?
3. Currently, the 2002 genre classif
On Wed, 2005-09-14 at 18:32 +0100, Hywel Williams wrote:
> 2. More channels have been requested. I'm currently testing the inclusion
> of almost all BBC regional radio stations in the schedules. The main
> issue is that at present they don't represent occasions when more than one
> regional s
Some bug fixes and modifications have been made to the data set - these are
outlined below.
1. The character set being used is now correctly identified as
ISO-8859-9. This was always the case but the ISO-8859-1 ident was
incorrectly displayed.
2. When audio description is being provided for
13 matches
Mail list logo
