Re: looking for tv-related URI use cases/application scenarios

Mike,

I agree that the actual transport encoding per se is not very important. What is
very important is understanding the circumstances of the resource relative to
the circumstances of the reference, so that it is possible to assess the
assumptions which can be made in resolving the reference. If both the reference
and the resource always appear in the same (virtual) channel, then it is may not
be too important whether they appear in NTSC VBI line 21, PAL VBI line 22, ATSC
data carousel, DVB object carousel or whatever. However, it is very important to
understand whether one needs to deal with a situation where the reference
appears in VBI line 21 of an NTSC channel, and the referenced resource may
appear in a data carousel of an ATSC virtual channel with a different major
channel number. The whole point of use cases is to help discover such things
which people often don't think to mention when they write down requirements.

Gomer

Michael A. Dolan wrote:

> Gomer-
>
> Both Ted's work at ATSC on synchronization, as well as the ATVEF spec,
> provide some more details on this general concept.  ATVEF usage is in the
> current public spec.  The ATSC paper is private, but was sent out on the
> ATSC BHTML list and/or can be obtained from Ted.
>
> The actual transport (VBI in Tim's example) encoding is less important than
> the concept of using a URI as a reference in a synchronization notification
> message to point at some object - HTML or application or whatever.
>
>         Mike
>
> At 12:33 PM 12/16/98 -0500, Gomer Thomas wrote:
> >This looks like an excellent use case. Can you provide a little more
> >detail? Where is the actual "jump page" which is to be loaded up? Is it on
> >an Internet web site? Or is it also encoded in line 21 of the VBI? If it is
> >encoded in line 21, is it in the same channel as the trigger, or can it be
> >in a different channel?
> >
> >Chambers, Tim wrote:
> >
> >> Let's start this off with basics:
> >>
> >> It would be a trigger encoded into the line21 of the VBI (which is must
> >> carry for broadcasters) of a tv show that loads up a "jump page" of
> >> enhanced tv content that supplements the television program.
> >>
> >> Tim
> >>
> >> > -----Original Message-----
> >> > From: Philipp Hoschka [mailto:Philipp.Hoschka@sophia.inria.fr]
> >> > Sent: Tuesday, December 15, 1998 12:46 PM
> >> > To: www-tv@w3.org
> >> > Subject: looking for tv-related URI use cases/application scenarios
> >> >
> >> >
> >> >
> >> > To better motivate the requirements, and evaluate their priorities,
> >> > the URI telecon this morning decided that we're lacking application
> >> > scenarios how tv-related URIs would be used
> >> >
> >> > So, if you have a particular idea of how tv URIs will be used,
> >> > please send it to this mailing list
> >> >
> >> > We have an editor (Craig Finseth) who will summarrize these
> >> > scenarios in a coherent document
> >> >
> >> > -Philipp Hoschka, W3C
> >> >
> >
> >
> >
> >--
> >Gomer Thomas
> >LGERCA, Inc.
> >40 Washington Road
> >Princeton Junction, NJ 08550
> >phone: 609-716-3513
> >fax: 609-716-3503
> >
> >
> >
> >
> ---------------------------------------------------------------------------
> Michael A. Dolan  TerraByte Technology  (619)445-9070    FAX: (619)445-6122
> PO Box 1673 Alpine, CA 91903, Overnight: 20239 Japatul Rd, Alpine, CA 91901
> URL:http://www.tbt.com



--
Gomer Thomas
LGERCA, Inc.
40 Washington Road
Princeton Junction, NJ 08550
phone: 609-716-3513
fax: 609-716-3503

Received on Wednesday, 16 December 1998 14:52:14 UTC