W3C home > Mailing lists > Public > public-tt@w3.org > September 2012

Editorial Issues List for SDP-US FPWD

From: Monica Martin (MS OPEN TECH) <momartin@microsoft.com>
Date: Wed, 12 Sep 2012 23:02:36 +0000
To: "'public-tt@w3.org'" <public-tt@w3.org>
Message-ID: <c79b31f984c04d8f9332e0e023cc873b@BLUPR03MB603.namprd03.prod.outlook.com>
We see several minor changes need for the SDP-US.

1.       SDP-US reference: Section 6.4
Issue: Both Section 6.3 and 6.4 speak to display-region.  Section 6.3 identifies requirements for use of display-region.
Correct Section 6.4 - change to #extent-region. Correct title and table reference.

2.       SDP-US reference: Section 6.6.2
Issue: What happens if the fontSize is unsupported? Add a note to what may happen.
Add a note: "Note: If a specific fontSize is unsupported, a player can snap to the next larger fontSize."

3.       SDP-US reference: Section 7.1.1
Issue: Doesn't R0040 actually speak to number of lines in all active regions?
Change from: No more than four lines of text must be selected into a region at any given time.
Change to:  No more than four lines of text must be selected into all active region at any given time.

4.       SDP-US reference: Section 8.1.2
Issue: Clarify the R0045 applies to roll-up content only. The requirement doesn't explicitly say that.
Change from: Durations (dur) shall only be used on the span element.
Change to:  Durations (dur) shall only be used on the span element for rollup style content.

5.       SDP-US reference: Section 8.2.1 (and 10)
Issue: Conflict - The time-offset-with-frames feature requires #subFrameRate feature. We only use #frameRate and #frameRateMultiplier features. The time-offset-with-frames was mistakenly included to pertain to the hh:mm:ss:ff notation. This is not the case.  The time-offset-with-frames pertains to the 100f notation.
Remove time-offset-with-frames feature from Section 8.2.1 table and Section 10.

6.       SDP-US reference: Section 8.3
Issue: Separate content and player for use of #frameRateMultiplier.
Add a note that states: Use of the #frameRateMultiplier is optional in the document (see Section 10).

7.       SDP-US reference: Abstract
Issue: Profile uses TTML 1.0. Ensure we acknowledge that boundary.

Change from: This interoperability profile is a proper subset of TTML 1.0 plus features required to support US Government closed captioning requirements for online presentation.

Change to: This interoperability profile is a proper subset of TTML 1.0 to support features required for US Government closed captioning requirements for online presentation.

8.       SDP-US reference: Appendix A.1
Issue: Updates to fontFamily weren't reflected in A.1.
Change from: The casual, cursive and smallcap styles could be considered for addition to <genericFamilyName> expression in a future version of TTML.
Change to: The casual, cursive and smallCaps styles could be considered for TTML 1.1.

9.       SDP-US reference: Conformance
Issue: Add a reference to Error Handling, Section 11.
Add this Note in Conformance to Section 11. "Error handling behavior is found in Error Handling<http://dvcs.w3.org/hg/ttml/raw-file/tip/ttml10-sdp/Overview.html#error_handling>" (Section 11).

10.   SDP-US reference: Global
Issue: Use smallCaps on all references.
c/smallcap or smallcaps/smallCaps

11.   SDP-US reference: Examples
Issue: Example numbering is mixed up. Correct Examples 1-4. Example 1 has no E000X identifier.

Correct example numbering: Example 1 has no E000X.  Example 2-4 have incorrect example numbers (i.e. Example 2 is E0001, Example 3 is E0002, etc.).

12.   SDP-US reference: Example correction

Issue: Background color and color have "named colors" but should be expressed in #rrggbbaa format only.
Implement change found here: http://lists.w3.org/Archives/Public/public-tt/2012Aug/0043.html. Proposed by Andrew Tai.

Other - Separately, Glenn be listed as editor?

Monica J Martin
Senior Program Manager
Microsoft Open Technologies, Inc.
A subsidiary of Microsoft Corporation
Received on Wednesday, 12 September 2012 23:03:41 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 5 October 2017 18:24:07 UTC