Re: Reigistry for tv:URI's

Keith Moore <moore@cs.utk.edu> Wed, 04 October 2006 21:59 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVEmI-00039C-25; Wed, 04 Oct 2006 17:59:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVEmG-000389-48 for discuss@apps.ietf.org; Wed, 04 Oct 2006 17:59:44 -0400
Received: from shu.cs.utk.edu ([160.36.56.39]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GVEmE-00017f-Sf for discuss@apps.ietf.org; Wed, 04 Oct 2006 17:59:44 -0400
Received: from localhost (localhost [127.0.0.1]) by shu.cs.utk.edu (Postfix) with ESMTP id 2C96D5644D; Wed, 4 Oct 2006 17:58:42 -0400 (EDT)
X-Virus-Scanned: by amavisd-new with ClamAV and SpamAssasin at cs.utk.edu
Received: from shu.cs.utk.edu ([127.0.0.1]) by localhost (shu.cs.utk.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3Jf+PIYdLNEA; Wed, 4 Oct 2006 17:58:37 -0400 (EDT)
Received: from [10.100.110.213] (adsl-070-147-143-107.sip.tys.bellsouth.net [70.147.143.107]) by shu.cs.utk.edu (Postfix) with ESMTP id A37965644B; Wed, 4 Oct 2006 17:58:36 -0400 (EDT)
Message-ID: <45242EC6.9090902@cs.utk.edu>
Date: Wed, 04 Oct 2006 17:59:34 -0400
From: Keith Moore <moore@cs.utk.edu>
User-Agent: Thunderbird 1.5.0.7 (Macintosh/20060909)
MIME-Version: 1.0
To: "Keesmaat, N.W. (Iko)" <iko.keesmaat@tno.nl>
Subject: Re: Reigistry for tv:URI's
References: <42F3BE57026C6E49B09E267EEF639D56D38E14@ms-dt01thalia.tsn.tno.nl>
In-Reply-To: <42F3BE57026C6E49B09E267EEF639D56D38E14@ms-dt01thalia.tsn.tno.nl>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: discuss@apps.ietf.org
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

> 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