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-1923 Next: LC-1943
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, dur, and end attributes can contain references to DOM events [DOM2Events]." This limits the usefulness of timesheets. Host languages should be allowed to extend the set of allowed events. --- "The events specified are beginEvent event, which is dispatched when an element starts and endEvent event, which is dispatched when an element stops." Why is there no repeatEvent? --- "When specified by the begin attribute, an inactive or started but not yet activated element will be activated when it receives the specified event. The parent time containers and item elements have to be active, though." We don't understand this. Please clarify. --- "When the element is specified to stop according to an event, the element informs its parent that it has stopped and parent then decides what should happen next. Of course, some other element could be waiting to beactivated according to the endEvent event from the particular element." Why is this normative, and why is there no example? Define what "not supported" means. What is the behavior if an unsupported value is used (this question should be answered everywhere the statement"not supported" is used? --- Define how timesheets interoperate with script and the DOM. Regards- -Doug Schepers, on behalf of the SVG WG