RE: Reigistry for tv:URI's

"Keesmaat, N.W. \(Iko\)" <iko.keesmaat@tno.nl> Thu, 05 October 2006 07:37 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVNnC-0006CT-0k; Thu, 05 Oct 2006 03:37:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVNnA-0006CO-Sb for discuss@apps.ietf.org; Thu, 05 Oct 2006 03:37:16 -0400
Received: from mail93.messagelabs.com ([194.106.220.67]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GVNn4-0006QJ-Fs for discuss@apps.ietf.org; Thu, 05 Oct 2006 03:37:16 -0400
X-VirusChecked: Checked
X-Env-Sender: iko.keesmaat@tno.nl
X-Msg-Ref: server-13.tower-93.messagelabs.com!1160033768!2224580!1
X-StarScan-Version: 5.5.10.7; banners=tno.nl,-,-
X-Originating-IP: [134.221.2.2]
Received: (qmail 2865 invoked from network); 5 Oct 2006 07:36:08 -0000
Received: from zeus.tno.nl (HELO zeus.tno.nl) (134.221.2.2) by server-13.tower-93.messagelabs.com with SMTP; 5 Oct 2006 07:36:08 -0000
Received: from ms-dt01vs01.tsn.tno.nl (cl-dt01castor.tno.nl [134.221.225.7]) by zeus.tno.nl (8.11.7p1+Sun/8.11.7) with ESMTP id k957a8B08917; Thu, 5 Oct 2006 09:36:08 +0200 (MEST)
Received: from ms-dt01thalia.tsn.tno.nl ([134.221.225.157]) by ms-dt01vs01.tsn.tno.nl with Microsoft SMTPSVC(6.0.3790.1830); Thu, 5 Oct 2006 09:36:07 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: RE: Reigistry for tv:URI's
Date: Thu, 05 Oct 2006 09:36:06 +0200
Message-ID: <42F3BE57026C6E49B09E267EEF639D56D38E17@ms-dt01thalia.tsn.tno.nl>
In-Reply-To: <45242EC6.9090902@cs.utk.edu>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Reigistry for tv:URI's
Thread-Index: AcboAGeO17JjwDpbR5mIEjN0Pt7BBwATezOw
From: "Keesmaat, N.W. (Iko)" <iko.keesmaat@tno.nl>
To: Keith Moore <moore@cs.utk.edu>
X-OriginalArrivalTime: 05 Oct 2006 07:36:07.0389 (UTC) FILETIME=[EB9228D0:01C6E850]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Cc: discuss@apps.ietf.org, "Zigmond, Dan" <djz@google.com>
X-BeenThere: discuss@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: general discussion of application-layer protocols <discuss.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@apps.ietf.org>
List-Help: <mailto:discuss-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=subscribe>
Errors-To: discuss-bounces@apps.ietf.org

Keith,

I do not understand what you driving at here. In RFC2838 the tv:URI was
explicitly defined as an identifier of television broadcasts.

Are we having a misunderstanding about what a TV broadcast is? 

What we are needing is a way to identify what people would call *the* TV
broadcast, i.e. if you have a device that can display NBC as received
over the air and NBC as received over the cable and they are displaying
the same television content at the same time, then that is what we would
like to refer to.

Whether or not you need NTSC decoding software/hardware to view the one
and PAL decoding software/hardware to view the other is not important.
That is lower level information that may be locally configured.

Does this make sense to you?

Iko.

===============================
Iko Keesmaat
TNO Information and Communication Technology
E-mail: iko.keesmaat@tno.nl

-----Original Message-----
From: Keith Moore [mailto:moore@cs.utk.edu] 
Sent: donderdag 5 oktober 2006 0:00
To: Keesmaat, N.W. (Iko)
Cc: discuss@apps.ietf.org
Subject: Re: Reigistry for tv:URI's

> In our view the tv:URI should identify a TV broadcast. 

I am not sure that this is a good thing.  What is important about 
distinguishing tv: from other URIs?  Is it that the signal is encoded 
using NTSC or PAL?  Or will MPEG do?  Is it that the signal is 
transmitted using radio frequency electromagnetic radiation through the 
air?  Or is it okay if the signal is transmitted over cable?  What about

satellite? Does it matter how it's modulated?

IMO, one of the goals of the tv: URI should be to permit convergence so 
that different sources of video programming can be viewed by the same 
computer program (or set-top box, whatever) while at the same time 
presenting the viewer with a reasonably clean user interface for 
selecting between different sources, and probably allowing those program

sources to be linked to from other sources - say from a web page or 
email reader.  That doesn't inherently mean that tv: URI should be 
usable by any kind of video programming source, but it probably does 
mean that there should be _some_ level of naming which can be used by 
any kind of video programming source.

 From my point-of-view, whether tv: is the higher-level name that maps 
to one or more lower-level services, or whether tv: is a specific 
lower-level service and there's a higher-level name (say a URN) to 
describe the video programming source, is almost arbitrary - as long as 
the relationship between the two levels of naming is clear.  Though it 
seems that there is already some investment in the tv: URL prefix along 
the former lines.


Keith


This e-mail and its contents are subject to the DISCLAIMER at http://www.tno.nl/disclaimer/email.html