- From: Henning Timcke <henning.timcke@werft22.com>
- Date: Tue, 20 Oct 1998 22:44:43 +0200
- 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>
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 > >
Received on Tuesday, 20 October 1998 16:47:16 UTC