Re: What "URI" identifier for local TV resources?
From: Craig A. Finseth (fin@finseth.com)
Date: Tue, May 04 1999
Date: Tue, 4 May 1999 10:12:56 -0500 (CDT)
Message-Id: <199905041512.KAA16963@isis.visi.com>
From: "Craig A. Finseth" <fin@finseth.com>
To: jim@nc.com
Cc: www-tv@w3.org, gomer@lgerca.com
Subject: Re: What "URI" identifier for local TV resources?
...
But there are user-interface applications (e.g. TV UI, EGP,
etc.) on the client or within a local system which do need to be
able to specify details such as tuner and channel number. For
example, a UI app that goes through all the autoscanned channels
on the first tuner and then on the second one might need to
display tv:69?tuner=first followed by tv:2?tuner=second.
A UI application that is going through local resources using an API
uses the API data structures to name the resource: these structures
need not be represented as UR*s at all.
For example, an API can return an array of channel objects. The
array would be indexed by a small integer.
...
Structured namespaces for physical TV channels already exist
(e.g. NTSC, PAL, ATSC, etc.); so there is a sound basis on
which to build a structured, uniform naming scheme (certainly
more uniform that file:!). Please let me know your thoughts.
Well, that's the point behind btv: it provides such a uniform,
transport-independant scheme.
Craig