Re: inline sounds

• Mail folder: WWW Talk Oct 93-present
• Next message: ira@linus.mitre.org: "presentations"
• Previous message: A.C.Holtham@exeter.ac.uk: "Indexes in HTML"
• Maybe in reply to: Dave_Raggett: "Re: inline sounds"
• Reply: Vinay Kumar: "Re: inline sounds"

From: Dave_Raggett <dsr@hplb.hpl.hp.com>
Message-id: <9312081351.AA17111@manuel.hpl.hp.com>
Subject: Re: inline sounds
To: Guido.van.Rossum@cwi.nl
Date: Wed, 8 Dec 93 13:51:24 GMT
Cc: ctrbdo%iapa.uucp@constellation.ecn.uoknor.edu, www-talk@nxoc01.cern.ch
Mailer: Elm [revision: 66.36.1.1]

>>     <A HREF="#prologue" PLAY="fanfare.au">The Prologue</A>

> This would mean that if you wanted to change the accompanying effects
> you would have to change all pointers.  Perhaps what we really need is
> URLs that point to a group of files which should be fetched and
> presented simultaneously (a "compound node" in the terminology of the
> Dexter hypertext reference model).  I don't know enough about HTTP,
> but possibly a variant of Content-type: multipart could be used here?

The MIME spec includes multipart/parallel which is defined as:

   "This type is syntactically identical to multipart/mixed, but the
    semantics are different. In particular, in a parallel entity, all
    of the parts are intended to be presented in parallel, i.e.,
    simultaneously, on hardware and software that are capable of doing
    so. Composing agents should be aware that many mail readers will
    lack this capability and will show the parts serially in any event."

So all we need is to make PLAY specify a URL for a multipart/parallel
document, and to enthuse browser writers about the idea.

Dave Raggett