Edit comment LC-2969 for Timed Text Working Group

Quick access to LC-2967 LC-2968 LC-2969 LC-2970 LC-2971 LC-2973 LC-2974 LC-2975 LC-2976 LC-2977 LC-2978 LC-2979 LC-2980 LC-2981 LC-2982 LC-2983

Comment LC-2969

Comment Shortname:

Commenter: chaals <chaals@yandex-team.ru>

Message-id:

Section of the document concerned:

[Free text description]Document as a wholeTTML Text and Image Profiles for Internet Media Subtitles... TTML Text and Image Profiles for Internet Media Subtitles... TTML Text and Image Profiles for Internet Media Subtitles and Captions 1.0 W3C Working Draft 30 September 2014 Abstract This document specifies two profiles of [TTML1]: a... Abstract Status of This Document This section describes the status o... Status of This Document 5 February 2004 W3C Patent Policy 1 August 2014 W3C Process Document Table of Contents 1. Scope 2. Terms and Definitions 3. Con... Table of Contents 1. Scope 2. Terms and Definitions 3. Conformance 4. Profile... 1. Scope This document specifies two profiles of [TTML1]: a... 1. Scope 2. Terms and Definitions Presentation processor. See Sectio... 2. Terms and Definitions Presentation processor Transformation processor Intermediate synchronic document Related Media Object 3. Conformance As well as sections marked as non-normative,... 3. Conformance Note 4. Profiles 4.1 General A subtitle document SHALL NOT conf... 4. Profiles 4.1 General A subtitle document SHALL NOT conform to the Te... 4.1 General Note 4.2 Text Profile The Text Profile consists of Sections 5. C... 4.2 Text Profile Text Profile 4.3 Image Profile The Image Profile consists of Sections 5.... 4.3 Image Profile Image Profile 5. Common Constraints 5.1 Document Encoding A subtitle doc... 5. Common Constraints 5.1 Document Encoding A subtitle document SHALL use UTF-8 c... 5.1 Document Encoding 5.2 Foreign Element and Attributes A subtitle document MAY... 5.2 Foreign Element and Attributes 5.3 Namespaces The following namespaces (see [xml-names]) a... 5.3 Namespaces 5.4 Overflow Subtitle documents should be authored assuming... 5.4 Overflow Note 5.5 Related Video Object A subtitle document MAY be associa... 5.5 Related Video Object 5.6 Synchronization Each intermediate synchronic document o... 5.6 Synchronization Note Note 5.7 Extensions 5.7.1 ittp:aspectRatio The ittp:aspectRatio... 5.7 Extensions 5.7.1 ittp:aspectRatio The ittp:aspectRatio attributes allo... 5.7.1 ittp:aspectRatio Note 5.7.2 ittp:progressivelyDecodable A progressively decodable... 5.7.2 ittp:progressivelyDecodable progressively decodable subtitle document Note 5.7.3 itts:forcedDisplay itts:forcedDisplay allows the proc... 5.7.3 itts:forcedDisplay Note Note Note 5.7.4 ittm:altText ittm:altText allows an author to provide... 5.7.4 ittm:altText Note 5.8 Region 5.8.1 Presented Region A presented region is a... 5.8 Region 5.8.1 Presented Region A presented region is a temporally a... 5.8.1 Presented Region presented region 5.8.2 Dimensions and Position All regions SHALL NOT extend... 5.8.2 Dimensions and Position 5.8.3 Maximum number The number of presented regions in a g... 5.8.3 Maximum number 5.9 Hypothetical Render Model Any sequence of consecutive i... 5.9 Hypothetical Render Model 5.10 Features Unless specified otherwise,a subtitle documen... 5.10 Features Note 6. Text Profile Constraints 6.1 Profile Designator This pr... 6. Text Profile Constraints 6.1 Profile Designator This profile is associated with the... 6.1 Profile Designator Note 6.2 Recommended Character Sets Authors should select from t... 6.2 Recommended Character Sets 6.3 Features The subtitle document SHALL conform to the fol... 6.3 Features 7. Image Profile Constraints 7.1 Profile Designator This p... 7. Image Profile Constraints 7.1 Profile Designator This profile is associated with the... 7.1 Profile Designator Note 7.2 Presented Image 7.2.1 Definition A presented image is... 7.2 Presented Image 7.2.1 Definition A presented image is a div element with a... 7.2.1 Definition presented image 7.2.2 Number per Region In a given synchronic document, th... 7.2.2 Number per Region 7.3 div element If a smpte:backgroundImage attribute is app... 7.3 div element 7.4 Features The features included in a subtitle document S... 7.4 Features 8. Hypothetical Render Model 8.1 Performance Model 8.1.1... 8. Hypothetical Render Model 8.1 Performance Model 8.1.1 Overview This Section specifie... 8.1 Performance Model 8.1.1 Overview This Section specifies the Hypothetical Rend... 8.1.1 Overview Fig. 1 Hypothetical Render Model 8.1.2 General The Presentation Compositor SHALL render in P... 8.1.2 General Note Note Note 8.1.3 Paint Regions The total normalized drawing area S(En)... 8.1.3 Paint Regions Note 8.1.4 Paint Images The Presentation Compositor SHALL paint... 8.1.4 Paint Images 8.1.5 Paint Text For each glyph displayed in intermediate s... 8.1.5 Paint Text Fig. 2 Example of Presentation Compositor Behavior for Text... Note 8.2 Reference Fonts The height and width of the area occupi... 8.2 Reference Fonts Note Note A. Recommended Character Sets When authoring textual conten... A. Recommended Character Sets B. Forced content (non-normative) Fig. 3 Illustration of th... B. Forced content (non-normative) Fig. 3 Illustration of the use of itts:forcedDisplay C. WCAG Considerations In order to meet the guidelines in [... C. WCAG Considerations D. Extensions D.1 General The following sections define ex... D. Extensions D.1 General The following sections define extension designa... D.1 General D.2 #progressivelyDecodable A transformation processor supp... D.2 #progressivelyDecodable D.3 #aspectRatio A transformation processor supports the #a... D.3 #aspectRatio D.4 #forcedDisplay A transformation processor supports the... D.4 #forcedDisplay D.5 #altText A transformation processor supports the #altTe... D.5 #altText D.6 #linePadding A transformation processor supports the #l... D.6 #linePadding D.7 #multiRowAlign A transformation processor supports the... D.7 #multiRowAlign E. References E.1 Normative references [CLDR] Unicode Con... E. References E.1 Normative references [CLDR] Unicode Consortium. The Co... E.1 Normative references [CLDR] [EBU-TT-D] [MHP] [RFC2119] [ST2052-1] [TTML1] [UNICODE] [WCAG20] [xml-names] E.2 Informative references [CEA-608] Line-21 Data Services... E.2 Informative references [CEA-608] [CEA-708] [HTML5] [SDPUS] [SUBM]
or

Refinement of the section concerned:

Status:

open proposal pending resolved_yes resolved_no resolved_partial other assigned to Nobody Adams, Glenn Birch, John Concolato, Cyril de Jong, Frans Desai, Hemant Dixit, Shwetank Dolan, Mike EVAIN, Jean-Pierre Flick, Chris Godbole, Sayali Goldstein, Glenn Guarino Reid, Loretta Harrenstien, Ken Kim, Dae Le Hégaret, Philippe Lemieux, Pierre-Anthony Levantovsky, Vladimir Masood, Kasar Megitt, Nigel Michel, Thierry mine, shingo Olivier, Frank Pfeiffer, Silvia Pieters, Simon Puri, Rohit Ronca, David Singer, David Smith, Jerry Sutherland, Harold Tai, Andreas

Type: substantive editorial typo question general comment undefined

Resolution status:

Response drafted Resolution implemented Reply sent to commenter

Response status:

No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):

Comment:

Editorial:

3. Conformance

The document defines clearly that it uses the terms MUST, SHOULD, MAY and so on in line with RFC2119. This is good practice, and helps many spec users recognise what is meant. But it uses (beginning about the next line) SHALL throughout, which is undefined, and an uncommon word in modern english. I suggest replacing every instance of shall with must.

Related issues: (space separated ids)

WG Notes: ISO (as well as other SDOs) recommends [1] against using 'must' to 'avoid any confusion between the requirements of a document and external statutory obligations.' [1] http://isotc.iso.org/livelink/livelink?func=ll&objId=4230456&objAction=browse&sort=subtype W3C does not forbid the use of the term 'shall'. IMSC 1 uses 'shall' consistently throughout. SMPTE-TT and CFF-TT and EBU-TT-D use 'shall'. Respec.js was updated to (a) recognize 'shall' and (b) include it in the RFC 2119 boilerplate prose.

Resolution: RFC 2119 specifies that 'shall' and 'must' have identical meanings. We have added the term 'shall' to the list of RFC 2119 terms in the Section 4 Conformance at https://dvcs.w3.org/hg/ttml/raw-file/tip/ttml-ww-profiles/ttml-ww-profiles.html We note also that Respec.js was recently updated to (a) recognize 'shall' and (b) include it in the RFC 2119 boilerplate prose.

(Please make sure the resolution is adapted for public consumption)