Re: How do authors use TV URLs? (was RE: URL: Background and Requirements)

From: Rob Glidden (
Date: Thu, Nov 05 1998

Message-ID: <012c01be08f0$d8deb5c0$4c989ccc@default>
From: "Rob Glidden" <>
To: "Ted Wugofski" <>, "dean blackketter" <>
Cc: <>
Date: Thu, 5 Nov 1998 11:15:55 -0800
Subject: Re: How do authors use TV URLs? (was RE: URL: Background and   Requirements)

>At 10:11 AM 11/5/98 -0600, Ted Wugofski wrote:
>>I can't imagine a usable and reuseable URI scheme (for a television
>>transport) unless there is a level of indirection.  In other words, the
>>URI points to the table and RDF is used to "find" the particular
>>transport, stream, and packet.
>The electronic program guides built into the kinds of devices we're
>imagining usually have this kind of table, though the naming conventions
>for channels and broadcasters haven't been standardized.

I think standardizing the naming conventions is not necessarily the critical
path, it is the "level of indirection" to "find" particular resources that
needs to be defined, enabled, or standardized.

If you can query the URI for what resources it contains (IE if it is an XML
data structure in itself -- ie a sub DOM) --  the level of indirection that
is needed can be built.

If an author can say, in essence, to the cache or streaming resource -- so
do you have pictureX available for display?  Is it coming soon?  What
pictures do you have, and which are available to be subscribed to? Then an
author can work with this.

If the author can say -- so what channels are available on this streaming
resource -- give me a text based list so I can present it to the user so
they can select one -- then this could work.


>Dean Blackketter
>WebTV Networks, Inc.
>1295 Charleston Road
>Mountain View CA 94043
>Work:     (650) 614-5521
>VM & Fax: (415) 680-2357
>Home:     (415) 863-5737
>Mobile:   (415) 819-6564