- From: thierry michel <tmichel@w3.org>
- Date: Fri, 6 Jul 2001 16:52:07 +0200
- To: <www-smil@w3.org>, "Susan Lesch" <lesch@w3.org>
Susan, Thank you very much for this review. I have updated the upcoming SMIL REC draft with you input. ----- Original Message ----- From: "Susan Lesch" <lesch@w3.org> To: <www-smil@w3.org> Sent: Friday, July 06, 2001 12:07 AM Subject: Minor typos in PR-smil20-20010605 > These are very minor typos in the SMIL 2.0 Proposed Recommendation > at http://www.w3.org/TR/2001/PR-smil20-20010605/. There are no > show stoppers here, just minor editorial suggestions. > > Below, a section and paragraph number is followed by a quote and then > a suggestion. > > Status par. 7 > specification, these may > specification; these may > > 2.1 par. 3 > Identical constructs eases authoring > Identical constructs ease authoring > > 2.1 par. 5 > XML-namespaces > XML namespaces (or, Namespaces in XML) > > 2.1.1 par. 1 > SMIL Modularization and Profiling > SMIL modularization and profiling > > 2.1.1 par. 4 > both; "SMIL 2.0" in the example > both - "SMIL 2.0" in the example > > 2.1.1 par. 7 > an integration set does not. > an integration set need not. > > 2.2.1 par. 1 > In future, > In the future, > > 2.2.1 par. 2 > DOM being supported, corresponds > DOM being supported corresponds > > 2.5 par. 13 > attributes on the media objects, other attributes > attributes on the media objects; other attributes > > 3.2.1 par. ~12 > thate > that > > 3.4.1 attributeName and attributeType > XMLNS > xmlns > > 4.2.2 Predefined Test Attributes > system-required > (system-required) > > There seems to be an extra [XML-NS]. > > as list of XML Namespace prefixes > as a list of XML namespace prefixes > > 4.3.1 last par. > If the user have not > If the user has not > > 5.2 par. 2 > Like SMIL 1.0, SMIL 2.0 BasicLayout modules includes > Like SMIL 1.0, the SMIL 2.0 BasicLayout module includes > > In 5.3.1, the tables have this markup: > <TABLE width="856" border="1"> > <TABLE width="852" border="1"> > On the Web, the width of the viewport is usually unknown. Please remove > width attributes. > > 5.5.1 > region's > regions (twice) > > 5.5.1 last par. > it's > its > > 5.6.2 > [[SMIL 1.0]] > [SMIL 1.0] > > 5.7.1 par. 5 > and given a method > and give a method (or be given) > > 5.9.1 last list item 1 > z-index of "inset > z-index of "inset" > > 5.10.1 > SMIL HierarchicalLayout module does not > The SMIL HierarchicalLayout module does not > > 5.10.2 Sub-region Positioning Attributes > element . > element. > > 5.10.2 Region fit override par. 1 > >region </SPAN> > >region</SPAN> > > 6.2.4 > both language's > both languages' > > 6.4 accesskey > This accounts for the possibility > This allows for the possibility > > 6.4 example two > the two link inside > the two links inside > > 6.5.2 nohref > boolean > Boolean > > 6.5.2 example 1 > answering ) > answering) > > 6.6.1 fragment > If this user clicks > If the user clicks > > 7.1 par. 2 > Requirements > requirements > > 7.3.1 type needs links for [RTSP], [HTTP], [FTP], and [URI]. > > 7.4.1 valuetype and 7.10.1 second list item 1 > URI ( [URI] ) > URI ([URI]) > > 7.9.1 abstract > Metadata > metadata, unless you mean the module in chapter 8 (SMIL > Metainformation) and if so, this could have a link > > 7.10 Appendicies > 7.10 Appendices > > 8. Title element > The SMIL 2.0 Metadata Module > The SMIL 2.0 Metainformation Module > > Globally in 8, Metadata -> metadata (except in DC) > > 8.1 > elements and attributes allowing to describe SMIL documents. > elements and attributes that allow description of SMIL documents. > > 8.2.2 par. 1 > with a SMIL documents > with a SMIL document > > 8.2.3 twice > Metadata RDF Schema > metadata RDF schema > > use standard Metadata schema > use standard Metadata schemas > > 8.3.1 name > depreciates > deprecates > > 8.3.2 > the root element to RDF tree > the root element of the RDF tree > > 8.4 > The example uses the Dublin Core version 1.0 RDF Schema [DC] and > an hypothetic SMIL Metadata RDF Schema: > becomes (five small changes) > The example uses the Dublin Core version 1.0 RDF schema [DC] and > a hypothetical SMIL metadata RDF schema: > > 9.1 par. 2 > is composed out of the > is composed of the > > 9.2.1 > X HTML > XHTML > > 9.3 par. 1 > must be added included on all elements > must be included on all elements > > 9.3 par. 3 > This realizes a so-called hybrid document type > This creates a so-called hybrid document type > > XML-namespaces > XML namespaces > > 10. TOC last item in 10.3.1 > Examples: > Examples > > 10.3.1 begin and end > either a SMIL 1.0 syncbase declaration, > a semi-colon separated list of values. > either a SMIL 1.0 syncbase declaration, > or a semi-colon separated list of values. > ^^? > > 10.3.1 > In addition, Id-values and Event-symbols are XML NMTOKEN values > and as such are allowed to contain the dot '.' and hyphen '-' > characters. The backslash character '\ > It would be nice to use current Unicode names: > In addition, Id-values and Event-symbols are XML NMTOKEN values > and as such are allowed to contain the full stop '.' and > hyphen-minus '-' characters. The reverse solidus character '\' > and > dot separator and minus sign > becomes > full stop and hyphen-minus > and globally > backslash '\' escape character > becomes > reverse solidus '\' escape character > > 10.3.1 clock values > Can the BNF indicate the leading zero in one-digit hours? > > 10.3.1 ID-Reference values > "Author" can be any gender. > If an author wishes to simulate this behavior in this version of > SMIL Timing and Synchronization, she can include the value > "indefinite" in the list of values for the begin or end > attribute. > becomes > When this behavior needs to be simulated in this version of > SMIL Timing and Synchronization, an author can include the > value "indefinite" in the list of values for the begin or end > attribute. > > [[SMIL Animation]] > [SMIL Animation] (and needs a link) > > Begin 3 seconds after an "focus" event on "x" > Begin 3 seconds after a "focus" event on "x" > > 10.3.1 endsync > mpeg > MPEG > > theendsync="last" > the endsync="last" > > media.If > media. If > > See also the section The excl time container. > See also the section The excl element. (and the link can wrap the title) > > 10.3.1 restart > </span>restart="never" > restart="never" > > syncBehaviorattribute > syncBehavior attribute > > 10.3.1 syncBehaviorDefault > behavior ) > behavior) > > 10.3.1 timeAction > This may have presentation side-effect > This may have presentation side effects > > 10.3.2 pauseDisplay > <span class="einst-priorityClass einst">priorityClass, but </span> > <span class="einst-priorityClass einst">priorityClass</span>, but > > 10.3.2 Side effects of activation > <a href="#Timing-HyperlinkImplicationsOnSeqExcl">I</a>mplications > of beginElement() and hyperlinking for <a > href="smil-timing.html#edef-seq" class="noxref"><span > class="einst-seq einst">seq</span></a> and <a > href="smil-timing.html#edef-excl" class="noxref"><span > class="einst-excl einst">excl</span></a> time containers. > links only to the "I". Could read: > <a href="#Timing-HyperlinkImplicationsOnSeqExcl">Implications of > beginElement() and hyperlinking for seq and excl time > containers</a>. > > 10.3.3 > media-marker-valuesare > media-marker-values are > > 10.3.3 Principles for building and pruning intervals > 10.3.3 in general is lacking the element and attribute markup that is > present in the rest of the spec. You may want to add it. In this > subsection, words are emphasized with asterisks. They should be marked > up <em>. See "*intervals* and not *instance times*" and "*unresolved*". > > straight-forward > straightforward (It's a word.) > > I don't know what to make of "INDEFINITE" and "UNRESOLVED." Could they > be marked up as HTML <code>? > > Let a be a video > Let "A" be a video > (Also, these variables could be marked up to match "Implications....") > > isperformed > is performed > > 10.3.3 Time container duration > the respective sections: The par element, The seq element, and The > excl element. > the respective sections: the par element, the seq element, and the > excl element. > (or change the anchors to include three words each) > > 10.4.1 > "presenting a document"means > "presenting a document" means > > documentbegin > document begin > > documentend > document end > > 10.5.3 > abeginElement() > abeginElementAt() > andbeginElementAt() > > 11. TOC > Examples: > Examples > > 11.1.3 Examples > ( for example > (for example > > 11.1.3 The speed attribute > playback speed . > playback speed. > > end. (i.e. > end (i.e. > > 11.1.5 last list > Thus the next interval (if there is any) > Thus the next interval (if there is one) > > 12.1 > The purpose of this document > The purpose of this section (or, chapter) > (The reader may be looking at the entire spec.) > > 12.4 > "We" is used 9 times in just this small section. The first person > should be avoided because it is apparently hard to translate (see > http://lists.w3.org/Archives/Public/www-international/2000AprJun/0058.html). > A possible alternative: > > Now that a taxonomy of transition types and subtypes is defined, > we now discuss a "style-like" shorthand syntax for transitions. > This shorthand syntax requires specification of the following: > > 1. The class of transition to be applied. For instance, to use a > 1-second left-to-right wipe in a presentation, the wipe is defined as > a transition class defined with the transition element. > > 2. The media elements to which this transition class is applied. In > this shorthand syntax, the transition class is applied to the > media element with the transIn and transOut attributes. > > 12.4.3 list item 2 > the affect of the fill value on > the effect of the fill value on > > 12.4.3 list item 4 > Perhaps: > The active duration for the media element to be transitioned to > (the destination media) must either overlap the active duration > or the fill state for the media element to be transitioned from > (the background). > (This isn't perfect, but it does omit the "we"s.) > > In section 12, elements, attributes, and attribute values could be > marked up as they are in the rest of the spec. (Some do match.) > Thus, in 12.4.3 Use of fill="transition" > elements such as <par>, <seq>, and <excl>. If fill="transition" > becomes: > elements such as <a href="smil-timing.html#edef-par" > class="noxref"><span class="einst-par einst">par</span></a>, <a > href="smil-timing.html#edef-seq" class="noxref"><span > class="einst-seq einst">seq</span></a>, and <a > href="smil-timing.html#edef-excl" class="noxref"><span > class="einst-excl einst">excl</span></a>. If <a > href="smil-timing.html#adef-fill" class="noxref"><span > class="ainst-fill ainst">fill</span></a>="<span > class="avalue">transition</span>" > > In Slideshow example with transitions, the "we"s can be cut from the > unordered list with little or no lost meaning. For example, > At 0 seconds, we cut directly to butterfly.jpg. > becomes: > At 0 seconds, cut(s) directly to butterfly.jpg. > > The extra tr at the end of 12.8.5 Table 5 can be omitted; the extra > hr in it isn't needed. > > In 13 globally, Content Model -> content model > > In 13.1, can "This document specifies the second version of the > Synchronized Multimedia Integration Language (SMIL, pronounced > "smile")." be cut? This is the purpose of the entire Recommendation, > not only the profile. > > 13.2 list item 3 > recommendations > Recommendations > > Could four sections be moved up in numbering, to create a conformance > section under, say, 13.3? Like this: > 13.3 Conformance > 13.3.1 Document Conformance (move the section "Conforming SMIL > 2.0 Documents" to here) > 13.3.2 Conforming SMIL 2.0 User Agents > 13.4 Normative Definition of the SMIL 2.0 Language Profile > etc. > > 13.3.2 (twice) > conforming SMIL 2.0 Document > conforming SMIL 2.0 document > > In 13.3.2, support for XML Base is stated about three times in a row. > Maybe try cutting the second instance: > > SMIL 2.0 deprecates base as a property value for the content > attribute of the meta element of SMIL 1.0 in favor of the more > general XML Base URI mechanisms [XMLBase]. XML Base is supported > on all elements, and affects the interpretation of URIs as > specified in the individual modules defining the URI attributes. > Specifically.... (Continue as one paragraph.) > > 13.3.2 > URI's > URIs > > 13.3.3 second table > class(NMTOKEN) > class (NMTOKEN) > > 13.3.3 last line > elements are in parenthesis. > elements are in parentheses. > > In 13.3.4 through 13.3.12, the tables could have an additional th with > rowspan="3", containing the name of the modules. (As it stands now, they > all are labelled "Elements, Attributes, Content Model." > > 13.3.4 Integration definitions > black color, values greater > black color; values greater > > 13.3.6 > The Layout Modules defines > The Layout Modules define > > 13.3.6 table (twice) > backgroundColor(background-color) > backgroundColor (background-color) > > 13.3.7 > area(anchor) > area (anchor) > > URI's > URIs > > in the table: > > sourcePlaystate(play | pause | stop) 'pause' > sourcePlaystate (play | pause | stop) 'pause' > > (Schedule | MediaContent | ContentControl | Animation )* > (Schedule | MediaContent | ContentControl | Animation)* > > 13.3.7 > tabbing order, inactive elements > tabbing order; inactive elements > > 13.3.8 Media Object Integration Requirements > erase=never > erase="never" > > 13.3.9 > The Resource Description Framework is defined in the W3C Metadata > Recommendation [RDFsyntax]. > (There is no "W3C Metadata Recommendation" per se. You could say:) > The Resource Description Framework is defined in the W3C RDF > Recommendation [RDFsyntax]. > > 13.3.11 first table (twice, and the outer parentheses in the third occurrence > could be omitted, yes?) > (Schedule | MediaContent | ContentControl | a | Animation )* > (Schedule | MediaContent | ContentControl | a | Animation)* > > 13.4 > recommendations > Recommendations > > 13.5 (normative) > All SMIL 2.0 modules are integrated according to the guidelines > in the "Modularization of SMIL 2.0" specification [SMIL-MOD], > (There is no "Modularization of SMIL 2.0" specification at that address. > Rather, I found "Synchronized Multimedia Modules based upon SMIL 1.0" > with the disclaimer:) > This document is a NOTE made available by W3C for discussion > only. This indicates no endorsement of its content, nor that W3C > has, is, or will be allocating any resources to the issues > addressed by the NOTE. > > 14.2 par. 4 > extending the SMIL Basic > extending SMIL Basic (or maybe, extending the SMIL Basic profile) > > allowed by the SMIL Basic > allowed by SMIL Basic (or maybe, allowed by the SMIL Basic profile) > > The browsers conforming to the SMIL 2.0 language profile will be > automatically conforming to SMIL 2.0 Basic. > could be: > User agents conforming to the SMIL 2.0 language profile > automatically conform to SMIL 2.0 Basic. > > 14.3.1 par. 1 > SMIL 2.0 Basic profile > The SMIL 2.0 Basic profile > > 14.3.1 par. 2 > While not strictly required, we strongly encourage languages > based upon SMIL Basic to include the SyncbaseTiming module from > SMIL 2.0 Timing and Synchronization using the scalable profiles > mechanism, and for SMIL Basic User agents to support the module > when device constraints are not prohibitive. > (removing the we, introducing "should," and rearranging the last clause:) > While not strictly required, languages based upon SMIL Basic > should include the SyncbaseTiming module from SMIL 2.0 Timing and > Synchronization using the scalable profiles mechanism; SMIL Basic > user agents should support this module when device constraints are > not prohibitive. > > 14.3.1 last par. > XML Namespace declaration using the xmlns and XML > Internationalization xml:lang attributes are supported on all > elements. > could be: > XML namespace declaration using the xmlns attribute and the XML > internationalization xml:lang attribute are supported on all > elements. > > 14.3.2 > "conforming" SMIL Basic Document > "conforming" SMIL Basic document > > 14.3.3 list items 3 and 4 > conforming SMIL 2.0 Documents > conforming SMIL 2.0 documents > > 14.3.3 list item 5 > Host Language Conformance > host language conformance > > 14.3.3 list item 8 > URI's > URIs > > 14.3.3 list item 10 > the XML 1.0 specification (Extensible Markup Language (XML) 1.0) [XML10] > maybe: > the Extensible Markup Language (XML) 1.0 (Second Edition) [XML10] > > 14.4 > [XMLNAMES] could link to References. > > Future work by W3C will address ways to specify conformance for > documents involving multiple namespaces. > could be (erring in caution): > It is expected that future work by W3C may address.... > > 14.4.1 par. 3 > XML Namespace declaration ... and XML Internationalization > XML namespace declaration ... and XML internationalization > > 14.4.1 list item 1 > the SMIL Basic > SMIL Basic (or maybe, the SMIL Basic profile) > > 14.4.2 par. after examples > This provides for authors with a means > This provides authors with a means > > 14.4.4 > A conforming scalable user agent must conform to the requirements > for SMIL Basic User Agents above. > could be (and link to smil-basic.html#BaseGuideNS-BasicUserAgent) > A conforming scalable user agent must conform to the requirements > for (conforming?) SMIL Basic user agents above. > > In E., these references could have punctuation between the title and > author: [SMIL10], [SMIL-ANIMATION], [XML10], and [XPTR] > > E. [COMP-GRAPHICS] > "Computer Graphics : Principles and Practice, Second Edition", > (two changes:) > "Computer Graphics: Principles and Practice," Second Edition, > > In E., [CC/PP], [DOM1], [DOM2Events], [DOM2], [DOM2CSS], [SMIL-CSS2], > [SVG], [XHTML10], and [XSCHEMA] could have editors listed, using et al. > where applicable to save space. > > E. [DOM2] > Specification".W3C > Specification". W3C > > E. [HTML4] might be a normative reference. I'm not sure. > > E. [IEEE-Arithmetic] > "IEEE ... (R1990). ". > "IEEE ... (R1990)" > > E. [ISO10646] > ""Information Technology -- Universal Multiple-Octet Coded Character > Set (UCS) -- Part 1: Architecture and Basic Multilingual Plane", > ISO/IEC 10646-1:1993...planes 1-16. " > becomes: > "'Information Technology -- Universal Multiple-Octet Coded Character > Set (UCS) -- Part 1: Architecture and Basic Multilingual Plane', > ISO/IEC 10646-1:1993...planes 1-16." > > E. [MathML], [XHTML11], [XLINK], [XMLBase] > MathML is now 2.0 (as I imagine you know) at http://www.w3.org/TR/MathML2/ > and XHTML 1.1, XLink and XML Base are Recommendations. > > E. [RDFschema] > Available at http://www.w3.org/TR/PR-rdf-schema/ > Available at http://www.w3.org/TR/rdf-schema/ > > E. [SMIL10] > 1.0" P. Hoschka. > 1.0," P. Hoschka. > > In E., is there a reason to list [SMIL20]? > > E. [WAI-SMIL-ACCESS] > Jacobs .W3C > Jacobs. W3C > > E. [XML10] > This is now Second Edition dated 6 October 2000, and Eve Maler is an editor. > > Best wishes, > -- > Susan Lesch - mailto:lesch@w3.org tel:+1.858.483.4819 > World Wide Web Consortium (W3C) - http://www.w3.org/ >
Received on Friday, 6 July 2001 10:52:11 UTC