Re: What "URI" identifier for local TV resources?

From: Craig A. Finseth (fin@finseth.com)
Date: Fri, Mar 26 1999


Date: Fri, 26 Mar 1999 17:05:52 -0600 (CST)
Message-Id: <199903262305.RAA05768@isis.visi.com>
From: "Craig A. Finseth" <fin@finseth.com>
To: jim@nc.com
Cc: www-tv@w3.org
Subject: Re: What "URI" identifier for local TV resources?

   Applications which are _local_ to a particular cable
   infrastructure, such as EPGs, often need to designate explicit
   channel number (and sometimes tuner) to the settop client in a

Such local applications can make use of global infrastructure with no
more effort than would be required to use any less-global mechanism.

   web page.  Similarly, the settop itself may generate HTML
   content with explicit channel numbers.  Under the tv: scheme,
   this would be done with tv:<chan#>.

The box can use any scheme that it likes to do this -- including
vendor proprietary.

   Just as many desktop applications require "file:" to identify
   local file resources, some STB content and appliations need a
   scheme to identify local TV resources.

Actually, since it's within a box, "file:" would work quite well.  Try
"file:/tuner/###" or something.

   So are local, client-relative channels specifiable under the
   current URI proposal?  I didn't see any examples.  By analogy
	...

See above.

Craig