This document:Public document·View comments·Disposition of Comments·
Nearby:SYMM Working Group Other specs in this tool
Quick access to LC-1920 LC-1921 LC-1922 LC-1923 LC-1924 LC-1925 LC-1926 LC-1927 LC-1928 LC-1929 LC-1930 LC-1931 LC-1932 LC-1933 LC-1934 LC-1935 LC-1936 LC-1937 LC-1938 LC-1939 LC-1940 LC-1941 LC-1942 LC-1943 LC-1944 LC-1945 LC-1946 LC-1947
Previous: LC-1921 Next: LC-1936
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