W3C home > Mailing lists > Public > public-tt@w3.org > January 2003

RE: Data Tunneling

From: Glenn A. Adams <glenn@xfsi.com>
Date: Fri, 31 Jan 2003 12:57:43 -0500
Message-ID: <7249D02C4D2DFD4D80F2E040E8CAF37C01FA9E@longxuyen.xfsi.com>
To: <Johnb@screen.subtitling.com>
Cc: <public-tt@w3.org>
I'm not sure I would agree about V-chip ratings. From my
perspective, they are more of the nature of announcement or
signaling data, which, depending on the device, may have
a way to display some of their aspects, e.g., in an EPG.
On the other hand, I can see timed text content that may
include semantic markup indicating that it is to be somehow
interpreted as rating related.
Yes, I suppose that a teletext clock field could also
be considered as timed text as well.

	-----Original Message-----
	From: Johnb@screen.subtitling.com [mailto:Johnb@screen.subtitling.com] 
	Sent: Friday, January 31, 2003 12:48 PM
	To: Glenn A. Adams
	Cc: public-tt@w3.org
	Subject: Data Tunneling

		I wrote: 
		Teletext magazine transmissions consist of timed text where different text instances are repeated at intevals (page refresh). In addition other features such as clock and fasttext require periodic transmission much the same as V-Chip ratings. TT might be a useful format for the definition and exchange of Teletext magazine content.

	Glenn wrote: 

	Are you saying you support adding data tunneling features to TT?
	If so, please attempt to justify this based on our charter.  

		I'm not sure quite what you mean by data tunneling - V-chip ratings are IMHO not data, they are short hand for text that is periodically displayed (at user request). The same argument can be extended to Teletext clock - its timed text in some senses - being periodically transmitted, but it differs from V-chip ratings by having a changing value. Why should TT be limited to non repeating (from a display perspective) text. In short - I would support the inclusion of repeated periodic transmission of static text elements in TT. It would be a pity if such a mechanism could not include an ability to send non static text too (e.g. clocks etc). This is where I see TT and HTML radically differ - HTML is static (with add ons to make it dynamic) TT is dynamic (at least from the user perspective). 

		regards John Birch 


	The views and opinions expressed are the author's own and do not necessarily reflect the views and opinions of the Screen Subtitling Systems Limited.
Received on Friday, 31 January 2003 12:57:45 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 5 October 2017 18:23:58 UTC