W3C home > Mailing lists > Public > www-smil@w3.org > October to December 2007

Re: Re: [SMIL30 LC comment] 6. SMIL 3.0 Linking

From: <tmichel@w3.org>
Date: Tue, 23 Oct 2007 09:18:48 +0000
To: thierry <tmichel@w3.org>
Cc: www-smil@w3.org,www-smil@w3.org
Message-Id: <E1IkFuS-0003bL-0H@wiggum.w3.org>


 Dear thierry ,

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/E1IkFkG-000333-Lx@wiggum.w3.org
 2. http://www.w3.org/TR/2007/WD-SMIL3-20070713/


=====

Your comment on Synchronized Multimedia Integration Language (SMIL
3.0)...:
> 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/200708111319.16650.Dr.O.Hoffmann@gmx.de
>  2. http://www.w3.org/TR/2007/WD-SMIL3-20070713/
> 
> 
> =====
> 
> Your comment on 6. SMIL 3.0 Linking:
> > Hello SMIL working group,
> > 
> > some comments on chapter 6:
> > 
> > 6.7/8
> > 
> > 
> > - Examples: 
> >         reference the definition of the id attribute and
> >         of elements like seq, par, img, video, text, previously 
> >         not defined or referenced...
> >         (bad document structure, because these features are
> >          defined in later chapters but used and not explained here)
> > 
> > ------------------------
> > 6.8
> > 
> > - wouldn't it be useful to have a type (and a title attribute
> >   it think it has, but the reader cannot identify this at this
> >   point of the specification, because this is defined in chapter
> >   10 - somehow opaque document structure)
> >   for the a element as in (X)HTML?
> > 
> > ------------------------
> > 
> > 6.8.2
> > 
> > 'The semantics of the area element in SMIL 3.0 is the same as it is
> for
> > 
> > HTML in that it can specify that a spatial portion of a visual
> object
> > can 
> > be selected to trigger the appearance of the link's destination.'
> > 
> > -> reference the module that defines visual objects?
> > I think, in HTML, area can only appear inside map, therefore
> > the sematics here seems to be slightly different, if there is
> > no map but visual objects...
> > 
> > ---------------
> > 
> > 'as in HTML [HTML4], the area element that is encoded earliest 
> > in the document takes precedence.'
> > 
> > - I looked for this in HTML4.01, but could not find it.
> >  Which chapter? Which section?
> > 
> > --------
> > 
> > What happens, if the used visual object is itself interactive,
> > for example a SVG or (X)HTML document with a elements?
> > Is a 'click' in an area of such an object related to its
> interactivity
> > or to the linking behaviour of the area element?
> > 
> > Does it only depend on the sensitivity attribute of the 
> > MediaRenderAttributes module?
> > If yes - maybe useful to mention it here as an informational
> > note with a reference to the module...
> > And because the object is on top and the a is the parent, the
> > a will never get an event? 
> > And because the area is inside the object, the area will always
> > get the event?
> > 
> > I think, there is a paragraph in 6.6.1 about this, but it is
> > neither indicated as normative nor informative, therefore I'm
> > not sure if this is applicable here.
> > 
> > 
> > --------
> > Examples:
> > 
> > If it is strongly recommended that all media object elements have an
> 
> > "alt" attribute, why do especially the area elements of the example 
> > do not have them (in HTML alt is required for area for example)?
> > 
> > 
> > Example 1:
> > 
> > '<smil xmlns="http://www.w3.org/2007/07/SMIL30/Language">
> >   <body>
> >     <video src="video" title="Interview" >
> >         <area id="firstQ" begin="0s" dur="20s" title="first
> question"
> > /> 
> >         <area id="firstA" begin="first0.end" dur="50s" title="first
> > answer" />
> >     </video>
> >   </body>
> > </smil>'
> > 
> > -> really begin="first0.end" or begin="firstQ.end" ?
> >      first0 would be outside the example?
> > 
> > 
> > ------------------
> > 
> > 6.9.1 
> > 
> > '  <ref src="menu.html" region="menubar">
> >     <area fragment="menuitem1" href="#selection1"/>
> >   </ref>'
> >   
> > -> define or reference definition or ref...
> 
> 
> Working Group Resolution:
> > Hello SMIL working group,
> > 
> > some comments on chapter 6:
> > 
> > 6.7/8
> > 
> > 
> > - Examples: 
> >         reference the definition of the id attribute and
> >         of elements like seq, par, img, video, text, previously 
> >         not defined or referenced...
> >         (bad document structure, because these features are
> >          defined in later chapters but used and not explained here)
> 
> We changed the order of the chapters, so that the elements and
> attributes are now defined before this chapter.
> 
> > ------------------------
> > 6.8
> > 
> > - wouldn't it be useful to have a type (and a title attribute
> >   it think it has, but the reader cannot identify this at this
> >   point of the specification, because this is defined in chapter
> >   10 - somehow opaque document structure)
> >   for the a element as in (X)HTML?
> 
> This might indeed be useful, but we feel that it is too late in the
> game to add this feature now.  We will add this to the list of items
> to
> consider for a next version of SMIL.
> 
> > ------------------------
> > 
> > 6.8.2
> > 
> > 'The semantics of the area element in SMIL 3.0 is the same as it is
> for
> 
> > HTML in that it can specify that a spatial portion of a visual
> object
> can 
> > be selected to trigger the appearance of the link's destination.'
> > 
> > -> reference the module that defines visual objects?
> > I think, in HTML, area can only appear inside map, therefore
> > the sematics here seems to be slightly different, if there is
> > no map but visual objects...
> 
> We reordered the chapters so that visual object should be defined
> before this chapter.
> The semantics between the HTML and SMIL variants of area are indeed
> different, so the comparison is purposely limited in the text.
> 
> > ---------------
> > 
> > 'as in HTML [HTML4], the area element that is encoded earliest 
> > in the document takes precedence.'
> > 
> > - I looked for this in HTML4.01, but could not find it.
> >  Which chapter? Which section?
> 
> HTML 4.01, section 13.6.1, the paragraph starting with "If two or
> more...".
> 
> > --------
> > 
> > What happens, if the used visual object is itself interactive,
> > for example a SVG or (X)HTML document with a elements?
> > Is a 'click' in an area of such an object related to its
> interactivity
> > or to the linking behaviour of the area element?
> > 
> > Does it only depend on the sensitivity attribute of the 
> > MediaRenderAttributes module?
> > If yes - maybe useful to mention it here as an informational
> > note with a reference to the module...
> > And because the object is on top and the a is the parent, the
> > a will never get an event? 
> > And because the area is inside the object, the area will always
> > get the event?
> > 
> > I think, there is a paragraph in 6.6.1 about this, but it is
> > neither indicated as normative nor informative, therefore I'm
> > not sure if this is applicable here.
> 
> Section 6.6 was not marked normative or informative.  We will mark it
> as normative, resolving this issue.
> 
> > --------
> > Examples:
> > 
> > If it is strongly recommended that all media object elements have an
> 
> > "alt" attribute, why do especially the area elements of the example 
> > do not have them (in HTML alt is required for area for example)?
> > 
> > 
> > Example 1:
> > 
> > '<smil xmlns="http://www.w3.org/2007/07/SMIL30/Language">
> >   <body>
> >     <video src="video" title="Interview" >
> >         <area id="firstQ" begin="0s" dur="20s" title="first question"
> />
> 
> >         <area id="firstA" begin="first0.end" dur="50s" title="first
> answer" />
> >     </video>
> >   </body>
> > </smil>'
> > 
> > -> really begin="first0.end" or begin="firstQ.end" ?
> >      first0 would be outside the example?
> 
> We added ellipses (...) to the example.
> first0 was a typo and should be firstQ.
> 
> > ------------------
> > 
> > 6.9.1 
> > 
> > '  <ref src="menu.html" region="menubar">
> >     <area fragment="menuitem1" href="#selection1"/>
> >   </ref>'
> >   
> > -> define or reference definition or ref...  
> 
> By reordering the chapters, ref is now defined before this chapter.
> 
> 
> ----


Working Group Resolution:
WG resolution:WG resolution:WG resolution:WG resolution:

----
Received on Tuesday, 23 October 2007 09:19:00 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:34:27 UTC