W3C home > Mailing lists > Public > public-tt@w3.org > December 2008

RE: TT telecon - agenda for 12 Dec

From: John Birch <john.birch@screen.subtitling.com>
Date: Mon, 15 Dec 2008 10:53:49 -0000
Message-ID: <4476B296B92A4741A49B0BD017590700AA79B2@sss-uk-ex-02.screen.subtitling.local>
To: "Glenn A. Adams" <gadams@xfsi.com>, <Sean.Hayes@microsoft.com>, <david.kirby@rd.bbc.co.uk>, "Public TTWG List" <public-tt@w3.org>
Hi Glenn,
 
I've (carefully) read the current CR and can now see how the existing
DFXP specification allows the same behaviour as SVG. 
I do feel that (in light of my experience) it might be a reasonable idea
to add some text to the dfxp spec that highlights this section as being
applicable to 'extensibility' as well as conformance.
 
It may be just me, but I didn't think to look in this section for
information on what type of extensions are permitted... though in
hindsight it is a reasonable location within the DFXP document
structure.
The current text within the DFXP spec requires very careful reading (in
an almost reverse sense) to determine what type of extensions are
permitted.
 
Certainly for me, the SVG document made finding and understanding
similar information easier.
 
I do specifically like the prose from 23.1 of the SVG spec. I find it to
be very informative... and I like the example (I personally love
examples).
 
regards
 
John
 
________________________________

From: Glenn A. Adams [mailto:gadams@xfsi.com] 
Sent: 13 December 2008 10:33
To: John Birch; Sean.Hayes@microsoft.com; david.kirby@rd.bbc.co.uk;
Public TTWG List
Subject: Re: TT telecon - agenda for 12 Dec



Please read (carefully) Sections 3.1 and 4 of the current DFXP CR, which
yields the same behavior as SVG with regard to foreign namespace items,
but specifies it in a more precise manner. If you have specific issues
with the current language, then please say so.

On 12/13/08 5:15 PM, "John Birch" <john.birch@screen.subtitling.com>
wrote:



	So would the use of foreign namespaces match that defined in
section 23 of the svg document? I particularly like the descriptive text
in section 23.1? And the example... The comment about the reasons for
allowing this feature are particularly relevant to me (private data).
Can we include similar text and examples in the dfxp spec?
	


John Birch | Screen Subtitling Systems Ltd | Strategic Partnerships Manager
Main Line : +44 (0)1473 831700 | Ext : 270 | Office :  
Mobile: +44 (0)7919 558380 | Fax: +44 (0)1473 830078
john.birch@screen.subtitling.com | www.screen.subtitling.com
The Old Rectory, Claydon Curch Lane, Claydon,Ipswich,IP6 0EQ,United Kingdom


See us at Broadcast Video Expo - February 17th - 19th 2009, Earls Court 2, London, Stand number K56


Before Printing, think about the environment


This message may contain confidential and/or privileged information. If you are not the intended recipient you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. Screen Subtitling Systems Ltd. Registered in England No. 2596832. Registered Office: The Old Rectory, Claydon Church Lane, Claydon, Ipswich, Suffolk, IP6 0EQ
Received on Monday, 15 December 2008 10:54:34 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 2 November 2009 22:41:39 GMT