Re: AW: work on url for television started

From: Rob Glidden (robg@quadramix.com)
Date: Wed, Oct 21 1998


Message-ID: <000401bdfd29$d2f06be0$4c989ccc@default>
From: "Rob Glidden" <robg@quadramix.com>
To: "Henning Timcke" <henning.timcke@werft22.com>, "Simon Gibbs" <simon@arch.sel.sony.com>
Cc: <www-tv@w3.org>, "Philipp Hoschka" <Philipp.Hoschka@sophia.inria.fr>, "Rodger Lea" <rodger@arch.sel.sony.com>
Date: Wed, 21 Oct 1998 12:32:45 -0700
Subject: Re: AW: work on url for television started


-----Original Message-----
From: Henning Timcke <henning.timcke@werft22.com>
To: 'Rob Glidden' <robg@quadramix.com>; Simon Gibbs
<simon@arch.sel.sony.com>
Cc: www-tv@w3.org <www-tv@w3.org>; Philipp Hoschka
<Philipp.Hoschka@sophia.inria.fr>; Rodger Lea <rodger@arch.sel.sony.com>
Date: Wednesday, October 21, 1998 11:12 AM
Subject: AW: AW: work on url for television started


>Rob:
>I will try
>Where do I find information about data carousels ?
>Henning


Conceptually -- data carousels are "constantly refreshed client-side caches
of broadcast data objects".  Think of tuning in to a TV channel -- if it is
a web page -- how often does the web page have to be rebroadcast so you can
see it when you tune into it?  Does all of the page have to be rebroadcast
every second?  how about just the top level page more often, with images
refreshed every few seconds (for example..)

For background

ATSC Specialist Group T3/S16 for Interactive Service Protocols:

http://toocan.philabs.research.philips.com/misc/atsc/t3s16/

A faq on DSM-CC is at
http://drogo.cselt.stet.it/mpeg/faq/faq_dsm-cc.htm

An Introduction to Digital Storage Media - Command and Control (DSM-CC)
http://drogo.cselt.stet.it/mpeg/documents/dsmcc.htm

Rob


>
>
>
>-----Ursprüngliche Nachricht-----
>Von: Rob Glidden [SMTP:robg@quadramix.com]
>Gesendet am: Mittwoch, 21. Oktober 1998 19:25
>An: Henning Timcke; Simon Gibbs
>Cc: www-tv@w3.org; Philipp Hoschka; Rodger Lea
>Betreff: Re: AW: work on url for television started
>
>Henning:
>
>Yes, I think assistance would be helpful. Could you elaborate a little on
>how XML could meet these kinds of requirements?
>
>1) "referencing cache data"  -- in transient caches and data carousels
>
>2) "querying caches"  -- to determine what is currently in them and
>available
>
>3) "supporting session management"  -- i.e. identifying, launching,
>subscribing, terminating multiple streaming sessions.
>
>I think a key challenge if finding the right level of abstraction -- some
>people think of all this a high-level, authoring issue, some think of it as
>low level exposing of the syntax of things like MPEG transport streams.
>
>Rob
>
>-----Original Message-----
>From: Henning Timcke <henning.timcke@werft22.com>
>To: Simon Gibbs <simon@arch.sel.sony.com>
>Cc: www-tv@w3.org <www-tv@w3.org>; Philipp Hoschka
><Philipp.Hoschka@sophia.inria.fr>; Rodger Lea <rodger@arch.sel.sony.com>;
>'Rob Glidden' <robg@quadramix.com>
>Date: Tuesday, October 20, 1998 1:54 PM
>Subject: AW: AW: work on url for television started
>
>
>>Hi Simon
>>As far as I can see: your requirements can be met with XML.
>>Please let me know if we can be of assistance in working this out.
>>Henning
>>
>>-----Ursprüngliche Nachricht-----
>>Von: Rob Glidden [SMTP:robg@quadramix.com]
>>Gesendet am: Montag, 19. Oktober 1998 03:37
>>An: Simon Gibbs; Henning Timcke
>>Cc: www-tv@w3.org; Philipp Hoschka; Rodger Lea
>>Betreff: Re: AW: work on url for television started
>>
>>Throwing in a generic look at URIs, namespaces, and "looking into" a
>>resource to see what it contains:
>>
>>"Namespaces in XML" World Wide Web Consortium Working Draft
>>16-September-1998
>>
>>at
>>http://www.w3.org/TR/WD-xml-names
>>
>>This is a proposed general solution to using URIs in namespaces, which
>could
>>be a way to "point into" resources.
>>
>>This "pointing into"/namespace could be a "channel space", stream, or data
>>cache.  This may be a more flexible tool than URIs alone (particularly if
>>you assume that the resource pointed into could contain structured data
>>itself, say an XML data structure).
>>
>>Rather than hardwire all possible resources, available
>>sessions/sessions/stream/cache resources may need to be queryable, and the
>>namespace identifier may need to be separable from the authored content.
>>
>>Such an approach may offer greater flexibility, authorability, and
resource
>>abstraction.
>>
>>Rob
>>
>>
>>
>>-----Original Message-----
>>From: Simon Gibbs <simon@arch.sel.sony.com>
>>To: Henning Timcke <henning.timcke@werft22.com>
>>Cc: www-tv@w3.org <www-tv@w3.org>; Philipp Hoschka
>><Philipp.Hoschka@sophia.inria.fr>; Rodger Lea <rodger@arch.sel.sony.com>
>>Date: Friday, October 16, 1998 2:06 PM
>>Subject: Re: AW: work on url for television started
>>
>>
>>>Henning Timcke wrote:
>>>
>>>> Sorry
>>>> This problem is already solved with UR*.
>>>> There is no difference between a local device and broadcast device.
>>>
>>>Well  - there's alot of difference between a local device anda broadcast
>>device. For one, broadcast devices deliver ATSC
>>>or DVB
>>>or DSS ... MPEG-2 transport streams (not worrying about analog
>>>for the moment). Local devices may or may not - depends what
>>>type of device we're dealing with. Another difference, broadcast
>>>transport streams have unique names based on things like
>>>network ids and service ids - this does not simply carry over
>>>for in-home content.
>>>
>>>> It is no problem to give every device an IP.
>>>
>>>Are you saying it's no problem to give my camcorder, DVD playeretc an IP
>>address? It may be no problem imagining that
>>>every
>>>device in the house has an IP address - but this is different
>>>from reality: many existing home-networkable AV products
>>>are not IP-based, and many CE companies are working
>>>on non-IP architectures for home networking.
>>>
>>>Simon
>>>
>>>
>>
>>
>
>