- From: Doug Schepers <schepers@w3.org>
- Date: Sat, 01 Mar 2008 17:43:49 -0500
- To: www-smil@w3.org
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
Received on Saturday, 1 March 2008 22:43:57 UTC