Re: Reigistry for tv:URI's

Keith Moore <moore@cs.utk.edu> Thu, 05 October 2006 07:45 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVNvB-0003er-CQ; Thu, 05 Oct 2006 03:45:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GVNvA-0003em-7N for discuss@apps.ietf.org; Thu, 05 Oct 2006 03:45:32 -0400
Received: from ka.cs.utk.edu ([160.36.56.221]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GVNv8-0001CJ-Vz for discuss@apps.ietf.org; Thu, 05 Oct 2006 03:45:32 -0400
Received: from localhost (localhost [127.0.0.1]) by ka.cs.utk.edu (Postfix) with ESMTP id 5B3ED2F227; Thu, 5 Oct 2006 03:46:19 -0400 (EDT)
X-Virus-Scanned: by amavisd-new with ClamAV and SpamAssasin at cs.utk.edu
Received: from ka.cs.utk.edu ([127.0.0.1]) by localhost (ka.cs.utk.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YXJPTl+15zUZ; Thu, 5 Oct 2006 03:46:16 -0400 (EDT)
Received: from [192.168.0.4] (user-119b1dm.biz.mindspring.com [66.149.133.182]) by ka.cs.utk.edu (Postfix) with ESMTP id 1185A2F21D; Thu, 5 Oct 2006 03:46:16 -0400 (EDT)
Message-ID: <4524B814.3060600@cs.utk.edu>
Date: Thu, 05 Oct 2006 03:45:24 -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: <42F3BE57026C6E49B09E267EEF639D56D38E17@ms-dt01thalia.tsn.tno.nl>
In-Reply-To: <42F3BE57026C6E49B09E267EEF639D56D38E17@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: 0bc60ec82efc80c84b8d02f4b0e4de22
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

> 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? 

perhaps.  that's why I was asking the questions I asked.  I don't 
understand where you want to draw the line between a "TV broadcast" and 
some other source of video programming. for example, we have "Internet 
radio" stations now, why not Internet TV stations?

offhand I think the difference between what I would call a "TV 
broadcast" and some other video program source is that a "TV broadcast" 
is immediate - that is, there are some set of viewers watching "in real 
time" (although of course it might also be possible to watch portions of 
it later) and the programming can therefore be chosen to fit the time at 
which it is broadcast.

> 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.

that's fine.  I just don't think that the notion of TV broadcasts 
covered by tv: URLs should exclude internet-only broadcasters.

Keith