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

Re: [SMIL30 LC comment] Feedback on the SMIL 3.0 LCWD specification from the Multimodal Interaction WG

From: Kazuyuki Ashimura <ashimura@w3.org>
Date: Thu, 01 Nov 2007 03:14:42 +0900
Message-ID: <4728C612.2040609@w3.org>
To: tmichel@w3.org
CC: www-smil@w3.org

Hi Thierry,

We're very sorry but we couldn't discuss this at the MMI call this
week because there were some urgent topics needed to be solved
before the Technical Plenary in the next week.

Could we suggest (1) we hold a joint meeting with you about this
at the Plenary and (2) submit the response after that?

Best regards,

Kazuyuki


tmichel@w3.org wrote:
>  Dear Kazuyuki Ashimura ,
>
> 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/46F01650.8030506@w3.org
>  2. http://www.w3.org/TR/2007/WD-SMIL3-20070713/
>
>
> =====
>
> Your comment on Synchronized Multimedia Integration Language (SMIL 3.0)
> W...:
>> b) Editorial comments:
>>
>> 2.1 We're afraid SMIL 3.0 specification is very big, and would like to
>> suggest the SYMM group provide a primer document like "XHTML+SMIL
>> Profile" [4] which mainly describes how to integrate SMIL modules
>> and other specs e.g. HTML and SVG so that authors can generate
>> SMIL ready Web applications easily.
>>
>> The document should include:
>> - 1.4.2 Profiles affected by SMIL 3.0
>> - 22.5 SMIL 3.0 Document Scalability Guidelines
>> - etc.
>>
>> Regarding "11.4.3 Attributes"
>>
>> Style:
>> 3.1 Following text bothers other text around it. So the style should
>> be modified:
>> [[
>> Since the event will never be raised on the specified element, the
>> event-base value will never be resolved.
>> ]]
>>
>> 4. Comments on "11.6 Document object model support"
>>
>> Typo:
>> 4.1 Maybe something is wrong in following sections:
>> [[
>> 11.6.6 Java language binding
>> 11.6.7 org/w3c/dom/smil/ElementTimeControl.java:
>> 11.6.8 org/w3c/dom/smil/TimeEvent.java:
>> ]]
>>
>> - The content of 11.6.6 is empty. Maybe 11.6.7 should be 11.6.6.1 and
>> 11.6.8 should be 11.6.6.2 ?
>>
>> - The titles of 11.6.7 and 11.6.8 should be rather
>> "org.w3c.dom.smil/..."?
>>
>>
>> 5. Comments on "15. SMIL 3.0 State"
>>
>> Regarding "15.2 Introduction"
>> ------------------------------
>>
>> Typo:
>> 5.1 "etc" in "higher priority node has preempted them, etc" should be
>> "etc." (missing "." at the end of the sentence).
>>
>> Regarding "15.6.4 Examples"
>> ----------------------------
>>
>> 5.2 Is this example really the one for "15.6 The SMIL UserState
>> Module"?
>> It seems a bit strange because it says "Here is a SMIL 3.0 Language
>> Profile example" but doesn't mention <state> element at all.
>>
>> Regarding "15.6.6 Data Model Events"
>> -------------------------------------
>>
>> 5.3 "contentControlChange(attrname)" event and "contentControlChange"
>> event should be also raised by each state, considering the
>> possibility of substate or Russian-doll usage of SMIL.
>>
>> Regarding "15.7.4 Examples"
>> ----------------------------
>>
>> 5.5 The examples for this StateSubmission Module must be added ASAP,
>> because I can't imagine how to use <submission> element or <send>
>> element without the examples.
>>
>> ----------------------------------------------
>> 6. Comment on "17. SMIL 3.0 Language Profile"
>> ----------------------------------------------
>>
>> Regarding "17.4.13 Timing and Synchronization Modules"
>> -------------------------------------------------------
>>
>> 6.1 "Supported Event Symbols" should be links to their detailed
>> description.
>>
>> --------------------------------------------
>> 7. Comments on "20. SMIL 3.0 DAISY Profile"
>> --------------------------------------------
>>
>> Regarding "20.4.7 Media Object Modules"
>> ----------------------------------------
>>
>> 7.1 There is some simple description of <param> element for TTS
>> (=speech output) here, however, no description on ASR (=speech
>> input). What should we do to integrate speech recognition
>> (=speech input)?
>>
>> e.g. (of TTS)
>> <param name="daisy:use-renderer" value="tts"/>
>> <param name="daisy:renderer-parameters" value="voice=joe"/>
>>
>> Regarding "20.4.13 Playback Guidelines"
>> ----------------------------------------
>>
>> Typo:
>> 7.2 The link to "UAAG checkpoint 2.4" should be
>> not
>> "http://www.w3.org/tr/UAAG10/guidelines.html#tech-time-independent"
>> but
>> "http://www.w3.org/TR/UAAG10/guidelines.html#tech-time-independent"
>> ^^
>> ("TR" should be capital letters)
>>
>> ------------------------------------------
>> 8. Comment on "21. SMIL 3.0 Tiny Profile"
>> ------------------------------------------
>>
>> Regarding "21.3 SMIL 3.0 Tiny Profile"
>> ---------------------------------------
>>
>> 8.1 M3U, PLP, PLS and WPL should be described by <acronym>
>>
>> ------------------------------------------
>> 9. Comment on "Appendix A. SMIL 3.0 DTDs"
>> ------------------------------------------
>>
>> Typo:
>> 9.1 All the headings have duplicated section number e.g. "A.1 A.1".
>>
>>
>> -------------------------------------------------
>> 10. Comments on "Appendix E. SMIL 3.0 Reference"
>> -------------------------------------------------
>>
>> Typo:
>> 10.1 The title of this page is "SMIL 2.1 References" which should be
>> "SMIL 3.0 References".
>>
>> 10.2 There is an extra ">" (&gt;) right before the <h1> heading.
>
>
> Working Group Resolution (LC-1835):
> Here is the response proposal:
>
> ------------------------------------------------------------------
> Q: 2.1 We're afraid SMIL 3.0 specification is very big, and would like to
> suggest the SYMM group provide a primer document like "XHTML+SMIL
> Profile" [4] which mainly describes how to integrate SMIL modules
> and other specs e.g. HTML and SVG so that authors can generate
> SMIL ready Web applications easily.
>
> The document should include:
> - 1.4.2 Profiles affected by SMIL 3.0
> - 22.5 SMIL 3.0 Document Scalability Guidelines
> - etc.
>
> A: The SYMM group will prepare a primer document to facilitate reading the
> specification. A primer will accompany the final specification content, and
> will be published after implementation testing is completed.
> ------------------------------------------------------------------
>
> ------------------------------------------------------------------
> Q: Regarding "11.4.3 Attributes"
>
> Style:
> 3.1 Following text bothers other text around it. So the style should
> be modified:
> [[
> Since the event will never be raised on the specified element, the
> event-base value will never be resolved.
> ]]
>
> A: There was some problems in the styling of the document. The style of
> the document has been modified.
> ------------------------------------------------------------------
>
> ------------------------------------------------------------------
> Q: 4. Comments on "11.6 Document object model support"
>
> Typo:
> 4.1 Maybe something is wrong in following sections:
> [[
> 11.6.6 Java language binding
> 11.6.7 org/w3c/dom/smil/ElementTimeControl.java:
> 11.6.8 org/w3c/dom/smil/TimeEvent.java:
> ]]
>
> A: There was a problem in the document with the numbering. The number in
> this chapter will be fixed in the next version.
> ------------------------------------------------------------------
>
> -----------------------------------------------------------------
> Q: - The content of 11.6.6 is empty. Maybe 11.6.7 should be 11.6.6.1 and
> 11.6.8 should be 11.6.6.2 ?
>
> - The titles of 11.6.7 and 11.6.8 should be rather
> "org.w3c.dom.smil/..."?
>
> A: These are editorial issues that will be taken into account before the
> next publication of the specifications.
> -------------------------------------------------------------------
>
> -------------------------------------------------------------------
> Q: 5. Comments on "15. SMIL 3.0 State"
>
> Typo:
> 5.1 "etc" in "higher priority node has preempted them, etc" should be
> "etc." (missing "." at the end of the sentence).
>
> A: The dot is missing; It will be added in the specification.
> ----------------------------------------------------------------
>
> ----------------------------------------------------------------
> Q: 5.2 Is this example really the one for "15.6 The SMIL UserState
> Module"?
> It seems a bit strange because it says "Here is a SMIL 3.0 Language
> Profile example" but doesn't mention <state> element at all.
>
> A: The document will include an example that includes the <state>
> element.
> ------------------------------------------------------------------
>
> ------------------------------------------------------------------
> Q: 5.3 "contentControlChange(attrname)" event and "contentControlChange"
> event should be also raised by each state, considering the possibility of
> substate or Russian-doll usage of SMIL.
>
> A: - We can understand this questions in two different manners:
>  1. You really mean contentControlChange. In this case  there is no issue:
> contentControlChange events are not related to state items: they are raised
> when something in the environment (or user preferences) changes such as
> screen size or language preferences.
>  2. You actually mean stateChange instead of contentControlChange. Here it
> would indeed be more logical to raise them on the corresponding state item
> but unfortunately this is impossible: the "state document" is not
> logically part of the SMIL document, and may also be physically separate.
> Hence, the rest of the SMIL document would have no way to refer to those
> events.
> -------------------------------------------------------------------
>
> ------------------------------------------------------------------
> Q: 5.5 The examples for this StateSubmission Module must be added ASAP,
> because I can't imagine how to use <submission> element or <send> element
> without the examples.
>
> A: An example with the use of <send> and <submission> will be added in the
> next version of the document.
> ----------------------------------------------
>
> ---------------------------------------------------------------------
> Q: 6.1 "Supported Event Symbols" should be links to their detailed
> description.
>
> A: The links are missing in the current version of the document, but will
> be added for "supported events symbols"
> --------------------------------------------------------------------
>
> --------------------------------------------------------------------
> Q: 7.1 There is some simple description of <param> element for TTS
> (=speech output) here, however, no description on ASR (=speech
> input). What should we do to integrate speech recognition
> (=speech input)?
>
> e.g. (of TTS)
> <param name="daisy:use-renderer" value="tts"/>
> <param name="daisy:renderer-parameters" value="voice=joe"/>
>
> A: This question is answered in comment LC-1834 because it deals with the
> actual integration of SMIL and MMI architecture.
> -----------------------------------------------------------------
>
> ------------------------------------------------------------------
> Q: Typo:
> 7.2 The link to "UAAG checkpoint 2.4" should be
> not "http://www.w3.org/tr/UAAG10/guidelines.html#tech-time-independent"
> but "http://www.w3.org/TR/UAAG10/guidelines.html#tech-time-independent"
> ^^
> ("TR" should be capital letters)
>
> A: The link of UUAG will be modified (tr in capital letters) in the
> document
> -------------------------------------------------------------
>
> -------------------------------------------------------------
> Q: 8.1 M3U, PLP, PLS and WPL should be described by <acronym>
>
> A: The acronyms will be described as <acronym> in SMIL 3.0.
> -----------------------------------------------------------------
>
> -----------------------------------------------------------------
> Q: Typo:
> 9.1 All the headings have duplicated section number e.g. "A.1 A.1".
>
> A: The duplication of headings in the Appendix will be removed from the
> document
> ------------------------------------------------------------------
>
> ------------------------------------------------------------------
> Q: Typo:
> 10.1 The title of this page is "SMIL 2.1 References" which should be
> "SMIL 3.0 References".
>
> A: The title of the page will be renamed as "SMIL 3.0 References"
> ---------------------------------------------------------------
>
> ---------------------------------------------------------------
> Q: 10.2 There is an extra ">" (&gt;) right before the <h1> heading.
>
> A: The extra ">" will be removed from the specification
> ------------------------------------------------------------------
>
> Thank you very much for the input
>
> ----
>
>

-- 
Kazuyuki Ashimura / W3C Multimodal & Voice Activity Lead
mailto: ashimura@w3.org
voice: +81.466.49.1170 / fax: +81.466.49.1171
Received on Wednesday, 31 October 2007 18:14:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:53:29 GMT