W3C home > Mailing lists > Public > smil-editors@w3.org > July to September 1998

Re: Timingmodel loops and deadlocks. Errata

From: Patrick J Deunhouwer <deunhwr@natlab.research.philips.com>
Date: Wed, 22 Jul 1998 16:30:17 +0200
Message-Id: <35B5F778.F68D11A@natlab.research.philips.com>
To: smil-editors@w3.org
Cc: Philipp Hoschka <Philipp.Hoschka@sophia.inria.fr>, "dr. W.R.T. ten Kate" <tenkate@natlab.research.philips.com>
Philipp Hoschka wrote:

> you're right, that got lost on the way
>
> any idea where it should be added, and how ?
>
> if so, please send it in as errata to "smil-editors@w3.org",
> and i'll give it the appropriate treatement (probably needs
> a discusion with the IG, but first things first)
>
> On 21/07/1998, Patrick J Deunhouwer <deunhwr@natlab.research.philips.com>  wrote:
> >Hi,
> >
> >In the current SMIL 1.0 specification I couldn't find anything about
> >deadlocks and loops (maybe I have missed it?).
> >In the SMIL draft 25 February 1998, there was a section Error Handling
> >(with four bullets). I read an e-mail that the first three bullets where
> >removed because they where covered by the timing model. But what happend
> >to the fourth bullet? (In my opinion this bullet covered all
> >possible synchronization errors). If I have the following SMIL document
> >(see example below), I assume the SMIL document is
> >invalid. But which rules do apply and where can I find them in the SMIL
> >specification or is the behavior unspecified?
> >
> ><smil>
> >  <body>
> >     <par dur="5s" >
> >          <img id="a" src="pict1.gif" begin="id(b)(2s)" dur="4s"  />
> >          <img id="b" src="pict2.gif" begin="id(a)(2s)" dur="4s"  />
> >     </par>
> >  </body>
> ></smil>
> >
> >
> >
> >
> >regards,
> > Patrick
> >
> >----------------------------------------------------
> >Deunhouwer, ing. P.J.  (PJD)
> >Building: WY 2 052
> >E-Mail: deunhwr@natlab.research.philips.com
> >----------------------------------NMS&A-------------
> >
> >

suggestion :

Add the following section to the SMIL specification

4.2.4.3. Error Handling

All documents containing errors caused by synchronization attributes are
invalid. Possible errors are for example a loop in the graph specifying begin or
end end times or any other situation which can cause a deadlock. Documents containing

timing attributes not covered by the timing model in Section 4.2.4. are invalid.




regards,
 Patrick Deunhouwer


----------------------------------------------------
Deunhouwer, ing. P.J.  (PJD)
Building: WY 2 052
Phone: +31 40 2744898
Fax:   +31 40 2744648
E-Mail: deunhwr@natlab.research.philips.com
----------------------------------NMS&A-------------
Received on Wednesday, 22 July 1998 10:29:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 15 December 2011 18:25:00 GMT