- From: <tmichel@w3.org>
- Date: Tue, 23 Oct 2007 09:08:16 +0000
- To: Dr. Olaf Hoffmann <Dr.O.Hoffmann@gmx.de>
- Cc: www-smil@w3.org
Dear Dr. Olaf Hoffmann , The SYMM Working Group has reviewed the comments you sent [1] on the Last Call Working Draft [2] of the Synchronized Multimedia Integration Language (SMIL 3.0) published on 13 Jul 2007. Thank you for having taken the time to review the document and to send us comments! The Working Group's response to your comment is included below. Please review it carefully and let us know by email at www-smil@w3.org if you agree with it or not before 02 nov 2007. In case of disagreement, you are requested to provide a specific solution for or a path to a consensus with the Working Group. If such a consensus cannot be achieved, you will be given the opportunity to raise a formal objection which will then be reviewed by the Director during the transition of this document to the next stage in the W3C Recommendation Track. Thanks, For the SYMM Working Group, Thierry Michel W3C Staff Contact 1. http://www.w3.org/mid/200708181501.58994.Dr.O.Hoffmann@gmx.de 2. http://www.w3.org/TR/2007/WD-SMIL3-20070713/ ===== Your comment on 11.4.3 Attributes: > Hello SMIL working group, > > > some comments related to the chapter > 11.4.3: > > end, examples: > > > '<html ...> > .... > <video dur="media" end="click" src="movie.mpg" .../> > .... > </html>' > > -> (1) This looks like a mixture of XHTML and SMIL? > XHTML does not have a video element > (ok, maybe HTML5 will have one, but > unfortunately no SMIL timing for it). > SMIL does not have a html element. > But if it is a mixture, doesn't either the > html or the video or the attributes need a > xmlns prefix? > Or another element with a xmlns attribute > for SMIL? > -> maybe better to use a smil element > instead of html to simplify the example... > > ---------- > > > '<html ...> > .... > <img src="image.jpg" end="click" /> > .... > </html>' > > -> in XHTML for the img element an alt attribute is > required, even if this is combined somehow with as > as suggested here... > And maybe either the html, img elements or the > end attribute need some XMLNS prefix? > -> maybe better to use a smil element > instead of html to simplify the example... > > > ----------------- > > min, max examples: > > '<html ...> > .... > <par endsync="first" min="12s" fill="freeze" > > <video id="video_of_15s" end="click" ...> > <video id="video_of_10s" .../> > </par> > .... > </html>' > > -> see comment (1) correspondingly > > '<par dur="5s" min="12s" > > <video id="video_of_15s"/> > <video id="video_of_10s" /> > </par>' > > -> missing '...'? > -> > '<par dur="5s" min="12s" > > <video id="video_of_15s" .../> > <video id="video_of_10s" .../> > </par>'? > else the src attribute is missing ... > > -------------- > > > event value syntax > > 'Since the event will never be raised on the specified element, > the event-base value will never be resolved.' > > -> the CSS box for this informative indicated container > covers some normative text on top and below. > -> change styling... > > -------------- > > '<html ...> > .... > <video id="foo" repeatCount="10" end="endVideo.click" ... /> > <img id="endVideo" begin="foo.repeat(2)" .../> > .... > </html>' > > -> > see comment (1) correspondingly > > ----------- > > repeat values > > typo? > > 'If this qualified form is used, the eventbase value will only be > resolved > when a repeat is observed that has a iteration value that matches the > specified iteration.' > > -> > '... has an iteration value ...'? > > --------------- > > The endsync attribute > > 'the child elements must complete all instances of active durations for > > resolved begin times.' > > and > > 'In the case of an element that restarts (e.g. because of multiple > begin > times), the element is considered to have ended its active duration > when > one active duration instance has completed. It is not a requirement > that > all instances associated with multiple begin and end times complete, > to > satisfy the semantics of endsync. This means that if the element is > playing > a second or later instance of an active duration, it may be cut short > by a > parent, once the other children satisfy the endsync semantics.' > > > -> define or reference definition of an 'instance' > > ------------- > > The fill attribute: > > styling inconsistency? > > 'This section is normative > > The fill attribute allows an author to specify that an element should > be > extended beyond the active duration by freezing the final state of the > > element. > The fill attribute is also used to determine the behavior when the > active > duration is less than the duration specified in the min attribute. > For this reason, rather than referring to the end of the active > duration, > this description refers to the "last instance of the simple > duration".' > > --> This box has a styling of an informative text, not normative... > > ------------- > > 'For this reason, rather than referring to the end of the active > duration, > this description refers to the "last instance of the simple > duration".' > > and > > 'For visual continuous media, the "frame" that corresponds to the end > of the > last instance of the simple duration is shown. > For algorithmic media like animation, the value defined for the end of > the > last instance of the simple duration should be used. > For time containers, freezing extends the state of all children that > are > active or frozen at the end of the last instance of the time container > simple > duration. > The children are frozen as they appear at the end of the last instance > of the > time container simple duration. If a child element ends its active > duration > coincident to the end of the last instance of its parent time container > > simple duration, the child element fill value determines whether the > child > will be frozen after the end of the parent time container's last simple > > duration.' > > and > > 'Freezing an element extends it, using the final state defined in the > last instance of the simple duration.' > > and maybe more of this in this section > > -> (2) define or reference definition of a > 'last instance of the simple duration' > At this point the reader cannot understand what this means. > Is it for example the last value of a simple duration? > The current value if the active duration ends? Is it the last frame > of a video or the current frame when the simple duration is > cut short? > > ------------------ > Resetting element state > > 'Any instance times associated with past event-values...' > > -> > see comment (2) correspondingly > > ---------------- > The restart attribute > > -> is any list entry of the begin list (except the first begin and > indefinite) > related to the restart attribute? > -> for example begin="0s;20s;60s" restarts at 20s and 60s? > if yes (I think so), maybe useful to mention this simple situation > in the informative list... > -> I think, it would be useful to list or explain here exactly, when > an element restarts or to reference to a normative section, where > this is explained. It does not really help to reference an > informative > section to 'define' this. > > ------------- > > example: > > '<html ...> > .... > <span begin="click" end="click" timeAction="class:highlight" > restart="whenNotActive"> > Click here to highlight. Click again to remove highlight. > </span> > .... > </html>' > > -> reference definition of 'timeAction' > -> (3) (X)HTML does not have such an attribute > (and no begin, end, restart) > maybe use xmlns prefixes to avoid confusion > > ------------ > > ' restartDefault = ( "always" | "whenNotActive" | "never" | "inherit" > ) > Defines the default value for the restart behavior for an element. > The values "always", "whenNotActive" and "never" specify that the > element restart behavior is the respective value...' > > -> '... as defined for the restart attribute.'? > > ------------ > > 'syncBehaviorDefault = ( "canSlip" | "locked" | "independent" | > "inherit" ) > Defines the default value for the runtime synchronization behavior for > an > element. > The values "canSlip", "locked" and "independent" specify that the > element's > runtime > synchronization behavior is the respective value.' > > -> '... as defined for the syncBehavior attribute.'? > > > 'syncToleranceDefault = ( Clock-value | "inherit" ) > Defines the default value for the runtime synchronization tolerance > value > for an element. Clock values specify that the element's runtime > synchronization tolerance value is the respective value.' > > -> '... as defined for the syncTolerance attribute.'? > > --------------- > > The timeAction attribute > > examples: > > -> > see comment (2) correspondingly if this is (X)HTML Working Group Resolution: > some comments related to the chapter > 11.4.3: > > end, examples: > > > '<html ...> > .... > <video dur="media" end="click" src="movie.mpg" .../> > .... > </html>' > > -> (1) This looks like a mixture of XHTML and SMIL? > XHTML does not have a video element > (ok, maybe HTML5 will have one, but > unfortunately no SMIL timing for it). > SMIL does not have a html element. > But if it is a mixture, doesn't either the > html or the video or the attributes need a > xmlns prefix? > Or another element with a xmlns attribute > for SMIL? > -> maybe better to use a smil element > instead of html to simplify the example... We will change these and other examples to use a <smil> container. Where appropriate (i.e. for XHTML+SMIL attributes) we will keep using the <html> container but add a namespace prefix. > ---------- > > > '<html ...> > .... > <img src="image.jpg" end="click" /> > .... > </html>' > > -> in XHTML for the img element an alt attribute is > required, even if this is combined somehow with as > as suggested here... > And maybe either the html, img elements or the > end attribute need some XMLNS prefix? > -> maybe better to use a smil element > instead of html to simplify the example... > > We will use a <smil> element and an ellipsis (...) to indicate left out attributes. Note that the examples are only there to illustrate particular points of the SMIL semantics, and therefore we don't think these examples need to be complete SMIL fragments. > ----------------- > > min, max examples: > > '<html ...> > .... > <par endsync="first" min="12s" fill="freeze" > > <video id="video_of_15s" end="click" ...> > <video id="video_of_10s" .../> > </par> > .... > </html>' > > -> see comment (1) correspondingly > > '<par dur="5s" min="12s" > > <video id="video_of_15s"/> > <video id="video_of_10s" /> > </par>' > > -> missing '...'? > -> > '<par dur="5s" min="12s" > > <video id="video_of_15s" .../> > <video id="video_of_10s" .../> > </par>'? > else the src attribute is missing ... See above. > -------------- > > > event value syntax > > 'Since the event will never be raised on the specified element, > the event-base value will never be resolved.' > > -> the CSS box for this informative indicated container > covers some normative text on top and below. > -> change styling... Made the text normative, removing the bad styling. > -------------- > > '<html ...> > .... > <video id="foo" repeatCount="10" end="endVideo.click" ... /> > <img id="endVideo" begin="foo.repeat(2)" .../> > .... > </html>' > > -> > see comment (1) correspondingly See above. > ----------- > > repeat values > > typo? > > 'If this qualified form is used, the eventbase value will only be resol= ved > when a repeat is observed that has a iteration value that matches the > specified iteration.' > > -> > '... has an iteration value ...'? Fixed typo. > --------------- > > The endsync attribute > > 'the child elements must complete all instances of active durations for= > resolved begin times.' > > and > > 'In the case of an element that restarts (e.g. because of multiple begi= n > times), the element is considered to have ended its active duration whe= n > one active duration instance has completed. It is not a requirement tha= t > all instances associated with multiple begin and end times complete, to= > satisfy the semantics of endsync. This means that if the element is pla= ying > a second or later instance of an active duration, it may be cut short b= y a > parent, once the other children satisfy the endsync semantics.' > > > -> define or reference definition of an 'instance' Added a reference to the section The instance times lists. > ------------- > > The fill attribute: > > styling inconsistency? > > 'This section is normative > > The fill attribute allows an author to specify that an element should b= e > extended beyond the active duration by freezing the final state of the = > element. > The fill attribute is also used to determine the behavior when the acti= ve > duration is less than the duration specified in the min attribute. > For this reason, rather than referring to the end of the active duratio= n, > this description refers to the "last instance of the simple duration".'= > > --> This box has a styling of an informative text, not normative... Made the styling of the paragraph also be normative. > ------------- > > 'For this reason, rather than referring to the end of the active durati= on, > this description refers to the "last instance of the simple duration".'= > > and > > 'For visual continuous media, the "frame" that corresponds to the end o= f the > last instance of the simple duration is shown. > For algorithmic media like animation, the value defined for the end of = the > last instance of the simple duration should be used. > For time containers, freezing extends the state of all children that ar= e > active or frozen at the end of the last instance of the time container = simple > duration. > The children are frozen as they appear at the end of the last instance = of the > time container simple duration. If a child element ends its active dura= tion > coincident to the end of the last instance of its parent time container= > simple duration, the child element fill value determines whether the ch= ild > will be frozen after the end of the parent time container's last simple= > duration.' > > and > > 'Freezing an element extends it, using the final state defined in the > last instance of the simple duration.' > > and maybe more of this in this section > > -> (2) define or reference definition of a > 'last instance of the simple duration' > At this point the reader cannot understand what this means. > Is it for example the last value of a simple duration? > The current value if the active duration ends? Is it the last frame > of a video or the current frame when the simple duration is > cut short? Added a paragraph here (i.e. in the section on the fill attribute) to define this last instance: The last instance of the simple duration is the last frame or value that was played during the last instance (see <a href="#Timing-BeginEnd-InstanceTimesLists">The instance times lists</a>= ) of the simple duration of the element before it finished or was stopped because of an end attribute. > ------------------ > Resetting element state > > 'Any instance times associated with past event-values...' > > -> > see comment (2) correspondingly Added reference. > ---------------- > The restart attribute > > -> is any list entry of the begin list (except the first begin and inde= finite) > related to the restart attribute? > -> for example begin="0s;20s;60s" restarts at 20s and 60s? > if yes (I think so), maybe useful to mention this simple situation > in the informative list... > -> I think, it would be useful to list or explain here exactly, when > an element restarts or to reference to a normative section, where > this is explained. It does not really help to reference an informati= ve > section to 'define' this. Added a bullet: An element with begin specified as a begin-value-list. Added a reference to the section where restart semantics are precisely defined. > ------------- > > example: > > '<html ...> > .... > <span begin="click" end="click" timeAction="class:highlight" > restart="whenNotActive"> > Click here to highlight. Click again to remove highlight. > </span> > .... > </html>' > > -> reference definition of 'timeAction' > -> (3) (X)HTML does not have such an attribute > (and no begin, end, restart) > maybe use xmlns prefixes to avoid confusion timeAction does not occur in any SMIL language profile, so this has to be XHTML. Added a namespace prefix. Also did this for examples using timeContainer. > ------------ > > ' restartDefault = ( "always" | "whenNotActive" | "never" | "inherit"= ) > Defines the default value for the restart behavior for an element. > The values "always", "whenNotActive" and "never" specify that the > element restart behavior is the respective value...' > > -> '... as defined for the restart attribute.'? > > ------------ > > 'syncBehaviorDefault = ( "canSlip" | "locked" | "independent" | "inhe= rit" ) > Defines the default value for the runtime synchronization behavior for = an > element. > The values "canSlip", "locked" and "independent" specify that the eleme= nt's > runtime > synchronization behavior is the respective value.' > > -> '... as defined for the syncBehavior attribute.'? > > > 'syncToleranceDefault = ( Clock-value | "inherit" ) > Defines the default value for the runtime synchronization tolerance val= ue > for an element. Clock values specify that the element's runtime > synchronization tolerance value is the respective value.' > > -> '... as defined for the syncTolerance attribute.'? Rephrased the definitions. > --------------- > > The timeAction attribute > > examples: > > -> > see comment (2) correspondingly if this is (X)HTML See above. ----
Received on Tuesday, 23 October 2007 09:08:36 UTC