W3C

List of comments on “SMIL Timesheets 1.0” (dated 10 January 2008)

Quick access to

There are 28 comments (sorted by their types, and the section they are about).

1-20 21-28

substantive comments

Comment LC-1925: [Timesheets LC comment] Abstract and Introduction
Commenter: Doug Schepers <schepers@w3.org> on behalf of SVG WG (archived message)
Context: in
Dear SYMM WG-

This is a Last Call review comment from the SVG WG on the SMIL
Timesheets 1.0 specification, W3C Working Draft 10 January 2008,
http://www.w3.org/TR/2008/WD-timesheets-20080110/ . Please let us know
if you have any questions by replying to www-svg@w3.org.


It's not clear that setting the 'active' or 'inactive' status of an
element toggles its visibility. This should be stated in the abstract
or introduction.

The abstract should describe the primary use cases, which seem to be
slideshows and photo galleries. Are there other use cases, either now
or planned for future versions?

---

It would be useful to explain very early on, in the abstract or
introduction, that "active" and "inactive" refer (exclusively?) to
states of perceivability, and that the purpose of timesheets is to
switch between these states.

---

"XML-based languages"

Can timesheets be used with text/html documents? Maybe you should say
DOM-based syntaxes?

---

Throughout the document, it's sometimes unclear when you are making
normative statements. We suggest strict use of the RFC 2119 keywords
("MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD
NOT", "RECOMMENDED", "MAY", and "OPTIONAL"), in either upper or lower
case, instead of looser terms like "are", "has to", etc. This will
clarify the spec for implementors, and will also make it easier to
develop a comprehensive test suite. We also recommend that you mark
informational asides as such. Subsequent emails will point out specific
instances that we feel need addressing, but there may be more.


Regards-
-Doug Schepers, on behalf of the SVG WG
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1936: [Timesheets LC comment] 5.1 Attributes
Commenter: Doug Schepers <schepers@w3.org> on behalf of SVG WG (archived message)
Context: in
Dear SYMM WG-

This is a Last Call review comment from the SVG WG on the SMIL
Timesheets 1.0 specification, W3C Working Draft 10 January 2008,
http://www.w3.org/TR/2008/WD-timesheets-20080110/ . Please let us know
if you have any questions by replying to www-svg@w3.org.


"The begin attribute supports offset and event values, "indefinite", or
a semi-colon separated list of values. All other values are not
supported. The allowed values and semantics of the begin attribute are
defined in the SMIL 3.0 Timing and Synchronization module."

Please add links to the definition of "offset" and "event" values.

Please consider allowing the full range of begin values, or provide
reasons why SMIL Timesheets needs to be different from the rest of SMIL
(and SVG).

Please clarify what happens if an unsupported value is encountered. Or
if is it intended that the host language defines it, please state that.

---

"The dur attribute supports the clock values, "media", and "indefinite".
The allowed values and semantics of the dur attribute are defined in the
SMIL 3.0 Timing and Synchronization module."

The listed values are exactly the same as in SMIL 3.0 Timing and
Synchronization specifies for dur. Repeated it here increases the risk
of errors and outdated definitions. We recommend pointing to the dur
definition and saying it MUST be exactly as defined there.

---

"The end attribute supports offset and event values, "indefinite", or a
semi-colon separated list of values. All other values are not
supported.The allowed values and semantics of the end attribute are
defined in theSMIL 3.0 Timing and Synchronization module."

Same comments apply here as for the 'begin' attribute.

---

"Since SMIL Timesheets does not include transitions, the
fill="transition"value of fill attribute is not supported. Also, since
the fillDefault attribute is not included in the SMIL Timesheets, the
fill="default" is interpreted the same as fill="auto"."

Note that the SMIL defaults are different from the SVG 'fill' attribute
defaults. See http://www.w3.org/TR/SVG11/animate.html#TimingAttributes.
That can be confusing, so please provide an example and some informative
text to explain this.

Why are there no transitions? This is something that authors will want,
and which is common in many script libraries (such as when a button
glows then fades when activated, or photo galleries blend between
images). Perhaps describing transitions in the form of opacity
animations and the like would be useful. If this functionality that is
intended for a later specification?

---

"The first attribute sets the current active child of a time
container"inactive". Then, it selects the first child element and sets
it "active". The first attribute can only be used for the excl time
container. The allowed value of the first attribute is a DOM event
[DOM2Events]."

Please clarify what it mean to set a time container to "inactive"/"active".

Please allow host languages to extend the set of allowed values to
include events that are not defined in DOM2Events.

---

"The prev attribute first checks, whether the current active child is
the first child. If not, it sets the current active child of a time
container "inactive". Then, it selects the previous child of the time
container and sets it "active". The prev attribute can only be used for
the excl timecontainer. The allowed value of the prev attribute is a DOM
event [DOM2Events]."

Please clarify that these attributes (first,next,prev,last) only operate
on elements, not on textnodes. As it is now it might mean for example a
previous child textnode.

Also it's not clear why the attribute has to be restricted to <excl>
only, we think just specifying that it only applies to <excl> might be
better. Host languages might want to reuse these attributes, so perhaps
leave that open too.

These comments apply to all of the first, prev, next, last attributes.

While the next, prev etc might be useful for creating a slideshow, it
seems to be lacking something like a "skip multiple", say next+10 or
prev-5 elements. Although this might be difficult to add as an
attribute, it shows that the current set of prev, next, first, last may
not cover all common use-cases, and that they should be thought over
once more to see if there's a better solution.



Regards-
-Doug Schepers, on behalf of the SVG WG
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1926: [Timesheets LC comment] Editorial
Commenter: Doug Schepers <schepers@w3.org> on behalf of SVG WG (archived message)
Context: in
Dear SYMM WG-

This is a Last Call review comment from the SVG WG on the SMIL
Timesheets 1.0 specification, W3C Working Draft 10 January 2008,
http://www.w3.org/TR/2008/WD-timesheets-20080110/ . Please let us know
if you have any questions by replying to www-svg@w3.org.


Typos
-----
"a-temporal" -> "atemporal"
"Timeshets" -> "Timesheets"
"Timsheets" -> "Timesheets"
"Timesshets" -> "Timesheets"
"meadiaSize" -> "mediaSize"
"meadiaTime" -> "mediaTime"
"allways" -> "always"
"severall" -> "several"
"oredered" -> "ordered"
"attibute" -> "attribute"
"semi-colon" -> "semicolon"

Grammatical and Punctuation Corrections
---------------------------------------
"SMIL Timesheets includes the SMIL 3.0 PrefetchControl module and the
SMIL 3.0 BasicAnimation module is used for controlling animations." ->
"SMIL Timesheets includes the SMIL 3.0 PrefetchControl module, and the
SMIL 3.0 BasicAnimation module is used for controlling animations."

"On the other hand, the begin attribute of a children of a excl
timecontainer is "indefinite"." -> "By contrast, the begin attribute of
the children of a excl time container is "indefinite"."

"The par element short for "parallel", defines a simple time grouping in
which multiple elements can play back at the same." -> "The par element,
short for "parallel", defines a simple time grouping in which multiple
elements can play back simultaneously."

"checks, whether the current active child is the first child" -> "checks
whether the current active child is the first child"

---

There are several incidents of missing definite or indefinite articles,
or where the article or verb conjugation does not agree with the number.
Here are a few examples:
"The children of the seq element consider the end time of preceding
child as their syncbase."
"Figure 1: Timeline of a Timesheets"
"Host document's" -> "A host document's"
"By default the begin attibute of a children of a seq and a par
timecontainers is "0s"."


Regards-
-Doug Schepers, on behalf of the SVG WG
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1937: [Timesheets LC comment] 5.2 Elements
Commenter: Doug Schepers <schepers@w3.org> on behalf of S (archived message)
Context: in
Dear SYMM WG-

This is a Last Call review comment from the SVG WG on the SMIL
Timesheets 1.0 specification, W3C Working Draft 10 January 2008,
http://www.w3.org/TR/2008/WD-timesheets-20080110/ . Please let us know
if you have any questions by replying to www-svg@w3.org.


The explanations of the par, seq and excl elements seem informative.
Please make them so, and add a normative statement saying that these
elements are defined in the SMIL 3.0 Timing and Synchronization module.

---

"The excl element defines a time container with semantics based upon
par,but with the additional constraint that only one child element may
play at any given time."

It's not clear to the SVG WG whether this is a constraint added by
Timesheets or by SMIL Timing and Synchronization.

---

"If any element begins playing while another is already playing, the
element that was playing is stopped."

Please clarify what it means that "playing is stopped". Is the timeline
paused, reset, or something else? What happens if the time first
animation is started again?

What happens if an animation is running in one "slide", and the user
navigates away, then returns? What state is the animation in?



Regards-
-Doug Schepers, on behalf of the SVG WG
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1927: [Timesheets LC comment] Definitions
Commenter: Doug Schepers <schepers@w3.org> on behalf of SVG WG (archived message)
Context: in
Dear SYMM WG-

This is a Last Call review comment from the SVG WG on the SMIL
Timesheets 1.0 specification, W3C Working Draft 10 January 2008,
http://www.w3.org/TR/2008/WD-timesheets-20080110/ . Please let us know
if you have any questions by replying to www-svg@w3.org.


As with the SMIL specs themselves, a definition list would be very
helpful. Here are some terms that should be defined, either in this
document, or in some other document with a direct reference link:

* time container [1]
* syncbase [2]
* host language

[1] http://www.w3.org/TR/SMIL3/smil-timing.html#q167
[2] http://www.w3.org/TR/SMIL3/smil-timing.html#q159


In general, the SVG WG finds the SVG spec notation to be more readable
than SMIL Timesheets for all attribute values, and encourage the SYMM WG
to use similar notation in SMIL Timesheets. See for example:
http://www.w3.org/TR/SVG11/painting.html#MarkerElement


Regards-
-Doug Schepers, on behalf of the SVG WG
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1938: [Timesheets LC comment] 6 Prefetch
Commenter: Doug Schepers <schepers@w3.org> on behalf of SVG WG (archived message)
Context: in
Dear SYMM WG-

This is a Last Call review comment from the SVG WG on the SMIL
Timesheets 1.0 specification, W3C Working Draft 10 January 2008,
http://www.w3.org/TR/2008/WD-timesheets-20080110/ . Please let us know
if you have any questions by replying to www-svg@w3.org.


"In the SMIL Timesheets, the src attribute is replaced with the select
attribute."

Please clarify, this can be read as, "'src' is renamed 'select' and
accepts the same values as 'src'".

It's not clear from the section what exactly SMIL Timesheets uses from
the PrefetchControl module, and what it doesn't use.

A few normative references to SMIL 3.0 PrefetchControl would be helpful,
since the Appendix A lists PrefetchControl as an informative reference only.



Regards-
-Doug Schepers, on behalf of the SVG WG
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1928: [Timesheets LC comment] Relationships to Other Specifications
Commenter: Doug Schepers <schepers@w3.org> on behalf of SVG WG (archived message)
Context: in
Dear SYMM WG-

This is a Last Call review comment from the SVG WG on the SMIL
Timesheets 1.0 specification, W3C Working Draft 10 January 2008,
http://www.w3.org/TR/2008/WD-timesheets-20080110/ . Please let us know
if you have any questions by replying to www-svg@w3.org.


1 Introduction

"An alternative to Timesheets is XHTML+SMIL [XHTMLplusSMIL] which gives
full SMIL functionality as in-line in non-SMIL XML documents. On the
other hand, SMIL itself gives full SMIL functionality as in-line
XML-based document."

The wording here is unclear, and seems to undermine the need for
timesheets when XHTML+SMIL already exists. Can you please clarify? The
first example seems to imply that timesheets can be used inline or
externally, but this passages seems to counterindicate that.

Also, what is the relationship of Timesheets and XHTML+SMIL to
HTML+Time? [1]

[1] http://www.w3.org/TR/NOTE-HTMLplusTIME




Regards-
-Doug Schepers, on behalf of the SVG WG
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1939: [Timesheets LC comment] 7.1 Attributes
Commenter: Doug Schepers <schepers@w3.org> on behalf of SVG WG (archived message)
Context: in
Dear SYMM WG-

This is a Last Call review comment from the SVG WG on the SMIL
Timesheets 1.0 specification, W3C Working Draft 10 January 2008,
http://www.w3.org/TR/2008/WD-timesheets-20080110/ . Please let us know
if you have any questions by replying to www-svg@w3.org.


"If no explicit target is specified, that is, the animation element does
not specify the select attribute, the implicit target element is the
host language element or elements referenced by the parent or ancestor
item element."

Please define the term 'animation element'.

Please clarify what is meant by 'the implicit target element is the host
language element'.

'parent or ancestor item' seems to allow arbitrary depth nesting of <item>
is that intended?

Please clarify the order in which the implicit target element is resolved.

---

"The origin attribute specifies the origin of motion for the animation."

Note that origin has no meaning in SVG. Please add informative text and
an example showing that.

---

"Timesheets uses the select attribute to specify the target element."

The paragraph this sentence start seems to be informative, not
normative, and should be marked as such.


Regards-
-Doug Schepers, on behalf of the SVG WG
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1929: [Timesheets LC comment] Examples and Figures
Commenter: Doug Schepers <schepers@w3.org> on behalf of SVG WG (archived message)
Context: in
Dear SYMM WG-

This is a Last Call review comment from the SVG WG on the SMIL
Timesheets 1.0 specification, W3C Working Draft 10 January 2008,
http://www.w3.org/TR/2008/WD-timesheets-20080110/ . Please let us know
if you have any questions by replying to www-svg@w3.org.


The figure numbering scheme is broken, all figures are listed as figure 1

As a general comment, the diagram images do not have adequate alt text,
and the first one contains a code snippet that could be extracted and
included in the main body as text. Members of the SVG WG could make SVG
versions of the diagrams if desired, which might be more accessible.

The examples all use the "smil:" prefix; this is not necessary. It's
extra characters to type, and also adds to the filesize. Please remake
the examples so that the default namespace is opened on the topmost SMIL
<timesheet> element.

The example of the first, prev, next, and last attributes would be more
clear if the button ids were not "first", "prev", "next", and "last"; it
may lead to the mistaken impression that those are somehow magic IDs or
values. Maybe name them "start", "back", "forward", and "end"?


Regards-
-Doug Schepers, on behalf of the SVG WG
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1940: [Timesheets LC comment] 7.2 Elements
Commenter: Doug Schepers <schepers@w3.org> on behalf of SVG WG (archived message)
Context: in
Dear SYMM WG-

This is a Last Call review comment from the SVG WG on the SMIL
Timesheets 1.0 specification, W3C Working Draft 10 January 2008,
http://www.w3.org/TR/2008/WD-timesheets-20080110/ . Please let us know
if you have any questions by replying to www-svg@w3.org.


"The SMIL Timesheets includes all elements of the SMIL 3.0
BasicAnimationmodule: animate, set, animateMotion, and animateColor."

Please allow host languages to add elements, e.g <svg:animateTransform>.

---

"The animateMotion element moves an element along a path. It is defined
inthe SMIL 3.0 BasicAnimation module."

Actually it's not fully defined, it requires a host language to define
it further. The <svg:animateMotion> element is fully defined however,
and it's different from the <smil:animateMotion> definitions. The SVG
WG, and SVG authors, would expect to be able to use all of
<svg:animateMotions> functionality in SMIL Timesheets, such as the 'd'
attribute, the <svg:mpath> element etc.


Regards-
-Doug Schepers, on behalf of the SVG WG
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1945: Theora and SVG:
Commenter:
Context: in
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1930: [Timesheets LC comment] Visibility
Commenter: Doug Schepers <schepers@w3.org> on behalf of SVG WG (archived message)
Context: in
Dear SYMM WG-

This is a Last Call review comment from the SVG WG on the SMIL
Timesheets 1.0 specification, W3C Working Draft 10 January 2008,
http://www.w3.org/TR/2008/WD-timesheets-20080110/ . Please let us know
if you have any questions by replying to www-svg@w3.org.


"In case of an element in the document that is not referenced by the
Timsheets, the element will be visible as dictated by the stylesheet."

Stylesheet == timesheet? This above is unclear to me. In SVG the
visibility may be defined not in a CSS stylesheet but in the document
itself, either by <style> elements, by 'style' attributes, or by
presentation attributes.

Could this be better worded, "In the case of an element in the document
which is not referenced by the Timesheets, the visibility of that
element will be dictated by the default visibility of host-language, or
as defined by the styling mechanism."?

---

"By default the element will remain visible all the time."

Define "visible".


Regards-
-Doug Schepers, on behalf of the SVG WG
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1941: [Timesheets LC comment] 8 Integration with CSS Layout
Commenter: Doug Schepers <schepers@w3.org> on behalf of SVG WG (archived message)
Context: in
Dear SYMM WG-

This is a Last Call review comment from the SVG WG on the SMIL
Timesheets 1.0 specification, W3C Working Draft 10 January 2008,
http://www.w3.org/TR/2008/WD-timesheets-20080110/ . Please let us know
if you have any questions by replying to www-svg@w3.org.


Where is the normative text for CSS Layout integration?

Can SMIL Timesheets be used in HTML+CSS with predictable and defined
results?


Regards-
-Doug Schepers, on behalf of the SVG WG
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1946: Theora and SVG:
Commenter:
Context: in
A small and simple specification is good, better chance to have the whole language implemented.

Opera has a preview of the next gen browser with native Theora and SVG:

http://dev.opera.com/articles/view/a-call-for-video-on-the-web-opera-vid/

First time I saw this, I was impressed, all that was missing was Vorbis audio and SMIL Timesheets.
Timesheets should be able to make fade in and out transitions by animating volume and opacity values on the audio/visual media.

With fade transitions, it's possible to make presentations presentable, the other feature could be added later.

The important thing is that the W3C provide an option for multimedia content other than the prevailing proprietary ones.

SMIL Timesheets, SVG, Theora, Vorbis in a Web browser is a winning combo IMHO :)


Jose Ramirez


Free your Media
'Xiph it'
at xiph.org
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1931: [Timesheets LC comment] External Linking
Commenter: Doug Schepers <schepers@w3.org> on behalf of SVG WG (archived message)
Context: in
Dear SYMM WG-

This is a Last Call review comment from the SVG WG on the SMIL
Timesheets 1.0 specification, W3C Working Draft 10 January 2008,
http://www.w3.org/TR/2008/WD-timesheets-20080110/ . Please let us know
if you have any questions by replying to www-svg@w3.org.


This specification shouldn't define the semantics of how a host
languages references the timesheet. (Option, neither would be defined
outside either document, in a manifest. , but optionally may be defined
by the host language.

While it's good to provide well-defined examples for a host language to
consider, these definitions should be a MAY or RECOMMENDED, or be
informative, not normative.

---

Please define what happens when multiple timesheets interact, such as
when several timesheets are referenced from the same document.

---

Can a timesheet import or reference another timesheet, to allow modular
timesheets and reuse? If not, why not? If so, what are the
implications for the timelines?

---

4.1 The timesheet element
-------------------------
"The timesheet element is located in the head section of the document.
It defines a parent container for other SMIL Timesheet elements."

Please change this to allow the host language to define that "head
section". In SVG there's no "head" element, the closest thing is
<defs>, which can occur any number of times anywhere in the document.

A better definition would be to say that the <timesheet> element can
occur anywhere that the <style> element can. It may be that host
languages will want to define this further though, especially in the
cases where there is no <style> element, so please allow for that too.

"The timesheet element defines two attributes: src and media."

This makes it stand out in SVG, since SVG uses xlink:href for other
references.

---

"The src attribute tells the location of an external timesheet. With
this attribute a common timesheet can be reused in multiple documents.
The attribute must contain a valid URI."

What happens if the timesheet element has no src attribute? What
happens if the attribute contains an invalid URI? What is a valid URI in
this context? Please add a normative reference to "valid URI".

Why is there no example and spec definition for how to use
<?xml-stylesheet?> for including a SMIL Timesheet? Please add that.

We don't see the need for having the src attribute on <timesheet> given
that <?xml-stylesheet?> can be used instead, and since the
<smil:timesheet> is limited to referencing SMIL Timesheets it's not
re-usable for other types of stylesheets. Please consider removing the
src attribute altogether. In HTML the <link> element might be used
instead, see http://www.w3.org/TR/html401/struct/links.html#edef-LINK.

---

"The media attribute is used for selecting the most suitable timesheet
for the current media device."

That's informative, make it clear.

---

"It works in the same way as the @media rule in the CSS stylesheets [CSS2]."

If that's a normative statement please reword it to say it MUST be
exactly as defined in CSS2.

---

"The media attribute contains a comma separated list of CSS media types."

Informative or normative? Is that not defined in CSS2?

---

"The timesheet timing and animation information is applied to the host
language document, only when the target device media type matches one of
the media types defined by the media attribute. If the media attribute
isnot defined, the default value is "all"."

Normative? Again isn't this defined in CSS2?

---

"The timesheet element contains the par, seq, and excl time containers."

What happens when it contains something else? For example if it was to
contain one of SVG's declarative animation elements?

---

"The semantics and restrictions are specified in the the time container
attributes."

Semantics and restrictions of what? The timesheet element or the par,
seq, and excl elements? Please clarify.

---

"In addition, it contains the item and prefetch elements. Finally, it
also contains the animation elements: animate, set, animateMotion,
andanimateColor."

Umm, why not list all of the elements allowed in one sentence? This is
simply confusing. Please allow the host language to extend the elements
allowed. In SVG there's the <animateTransform> element which is very
useful to include here.

Please explain what should happen when a timesheet is in conflict with a
host language animation? Also if another SMIL animation being applied on
the same element that is animated by a timesheet - how do they interact?



Regards-
-Doug Schepers, on behalf of the SVG WG
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1942: [Timesheets LC comment] Appendix A. References
Commenter: Doug Schepers <schepers@w3.org> on behalf of SVG WG (archived message)
Context: in
Dear SYMM WG-

This is a Last Call review comment from the SVG WG on the SMIL
Timesheets 1.0 specification, W3C Working Draft 10 January 2008,
http://www.w3.org/TR/2008/WD-timesheets-20080110/ . Please let us know
if you have any questions by replying to www-svg@w3.org.


"This section is informative.
E.1 Normative References"

That's a contradiction. Please fix.

Please reference CSS 2.1 and DOM 3 Events, or explain the rationale for
not doing so.

All of the SMIL 3 modules that are normatively referenced in the spec
should be listed as normative references.



Regards-
-Doug Schepers, on behalf of the SVG WG
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1947: Theora and SVG:
Commenter: <jose@multimedia4everyone.com> (archived message)
Context: in
A small and simple specification is good, better chance to have the whole language implemented.

Opera has a preview of the next gen browser with native Theora and SVG:

http://dev.opera.com/articles/view/a-call-for-video-on-the-web-opera-vid/

First time I saw this, I was impressed, all that was missing was Vorbis audio and SMIL Timesheets.
Timesheets should be able to make fade in and out transitions by animating volume and opacity values on the audio/visual media.

With fade transitions, it's possible to make presentations presentable, the other feature could be added later.

The important thing is that the W3C provide an option for multimedia content other than the prevailing proprietary ones.

SMIL Timesheets, SVG, Theora, Vorbis in a Web browser is a winning combo IMHO :)


Jose Ramirez


Free your Media
'Xiph it'
at xiph.org
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1932: [Timesheets LC comment] 3.1 Timing and Synchronization
Commenter: Doug Schepers <schepers@w3.org> (archived message)
Context: in
Dear SYMM WG-

This is a Last Call review comment from the SVG WG on the SMIL
Timesheets 1.0 specification, W3C Working Draft 10 January 2008,
http://www.w3.org/TR/2008/WD-timesheets-20080110/ . Please let us know
if you have any questions by replying to www-svg@w3.org.

"Host document's elements are set to "active" and "inactive" following
the semantics of the defined time containers."

Of which defined time containers? In the host language? Please
elaborate, and include links to where the behavior is defined, or
clarify that it's the host language that defines the behavior.

---

"The base time, or the syncbase of a timesheet element is the moment
when the element is started by its parent."

We suggest replacing "when the element is started" with "when it is
started".

Started by its parent, does that mean "started by its parents time
container"? If so, say so.

---

"Starting an element does not necessarily make the referenced media
element visible. Rather, it sets the time moment "0s", to which the
element's attributes are compared."

This sounds like an informative note, please make it so.

---

"The duration of an element is primarily defined by the dur attribute."

This section is normative, and We would expect the behavior of dur to be
either fully defined here or the section to be made informative.


Regards-
-Doug Schepers, on behalf of the SVG WG
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1920: Only a few post-deadline questions ...
Commenter: Dr. Olaf Hoffmann <Dr.O.Hoffmann@gmx.de> on behalf of Dr. Olaf Hoffmann (archived message)
Context: Document as a whole
Hello SYMM Working Group,

just a few post-deadline questions, I'd like to ask:


1) If several external, internal timesheets are provided and
the document contains for example some SMIL animation inside
(like SVG) - how are the priorities? Similar to CSS priority
rules/specifities? Priority by timing or in case of collisions
the order in the source code of the host document?

2) I think, for details about the interaction with CSS for
example something like the SMIL animation sandwich model
is applicable as usual?

3) What about adopting animateTransform from SVG?
Because many 'designers' seem to like to rotate, to distort
content for decorative purposes, this might be a useful
feature especially for timesheets to cover more of the
stuff people might be interested in.
I think, there were already some efforts from
apple to integrate such feature into CSS, could be
better covered by SMIL/SYMM of course...

4) Why no path-animation for animateMotion
(SplineAnimation Module)? and could be useful to
adopt keyPoints from SVG ...
With only values-animation there are no really
smooth paths available and some 'designer'
might prefer the soft trajectories more than
the hard edges of values-animations.

5) Because animate anyway animates any property or attribute,
is animateColor really required for timesheets - if yes, why?

6) Now something like
'<link href="timesheet.smil" rel="timesheet" type="application/smil+xml">'
is allowed in the current draft for non-XML. This is pretty nice.
Why not to add something like this for XML:
<?xml-stylesheet href="timesheet.smil" type="application/smil+xml"
title="timed styling" alternate="yes" ?>

In both cases it is already defined by the type attribute, what the
user-agent has to expect, therefore I cannot see a specific problem
with this variant for XML and it avoids confusing messages from validators
without the ability to validate multiple namespaces in one document.
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1923: [Timesheets LC comment] bravo user control
Commenter: Al Gilman <Alfred.S.Gilman@IEEE.org> (archived message)
Context: in
<note
class="inTransmittal">

The following is a consensus comment on the SMIL Timesheets
Last Call from PFWG.

Al
/chair, PFWG
http://www.w3.org/WAI/PF
</note>

The Protocols & Formats group, having reviewed SMIL Timesheets, has the
following comments for the SYMM WG:

1. The PFWG believes the timesheet model to be an extremely elegant
engineering solution, as it allows for user control over timing (pause,
stop, replay, rewind, fast forward, slow rate of play, accelerate
rate of
play, etc.) through a user timesheet. Thus a user can
exercise control over the author-defined timing. The UA or an assistive
plugin wizard can help the user to manage the timing settings.

2. SMIL Timesheets provides a mechanism for timing control. This
mechanism allows for user adjustment of the timing. This adjustment
is an
important requirement for access to interaction by People With
Disabilities. Therefore, the PFWG would like the HCG to foster the
reuse of the mechanism in SMIL Timesheets, or -- at the very least --
ensure that the personalization capabilities are not lost as other
formats implement timing control.

3. The PFWG also recommends and supports the adoption of the SMIL
Timesheet model in XHTML2, XHTML 1.1, and XHTML Modularizations.

In sum, the PFWG is intrigued and interested in the accessibility and
user-control aspects of timesheets. Because of this, and the importance
to the user-experience over control of timing cues and rates, the PFWG
approves of the timesheets model and shall follow the development of
SMIL
Timesheets closely and with great interest, and anticipates cooperating
with the editors and working group in order to ensure that the
accessibility and user-control offered by the SMIL Timesheets model is
realized.
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

1-20 21-28

Add a comment.


Developed and maintained by Dominique Hazaël-Massieux (dom@w3.org).
$Id: Overview.php,v 1.46 2013-10-04 08:11:33 dom Exp $
Please send bug reports and request for enhancements to w3t-sys.org