W3C

WOFF Disposition of Comments

2011-July-13


Abstract

This document outlines the way in which the WebFonts Working Group addressed the comments submitted during the Last Call period of WOFF 1.0.

Status of this document

During the Last Call period of the 16 November 2010 Working Draft of WOFF 1.0, a number of comments were received. This document summarizes those comments and describes the ways in which the comments were addressed by the WebFonts Working Group. Editorial changes have been made in the editors draft.

Table of Contents

Issue WG Action Commenter Response
1. No problems No change No reply
2. Mention benefits in supporting materials No change No reply
3. Put WOFF elements in a namespace Reject Accept
4. Allow multiple <text> elements as child of <description> Accept Accept
5. Support pronunciation and sorting metadata with structured text No change Accept
6. Extensibility by other namespaces Reject Accept
7. xsd:NCName is too constraining for lang attributes Accept Accept
8. Add @url and @id to <text> elements inside <license> Accept Accept
9. I18n-ISSUE-2: Why not using xml:lang? Accept Accept
10. I18n-ISSUE-4: Language tag references Accept Accept
11. I18n-ISSUE-5: Use of attributes for human readable text Reject Accept
12. I18N-ISSUE-6: Localization mechanism too restricted Reject Accept
13. I18N-ISSUE-7: Paragraphs and inline content Accept Accept
14. I18N-ISSUE-8: Direction attributes needed Accept Accept
15. Description of text elements Accept No reply
16. I18N-ISSUE-9: OpenType feature preservation [WOFF] Accept Accept
17. Conflicting statements on WOFF font table order No change Accept
18. license element text subelements Accept Accept
19. letting a URL carry information about the meaning of a resource is bad Reject No reply
20. clear and careful language No change No reply
21. Why padding after private data block Accept No reply
22. Change metadata section to use XMP Reject No reply
23. Wasteful to use four bytes to store an origLength Reject Accept
24. A context-free grammar for WOFF would be nice Reject No reply
25. Why align tables to 4-byte boundaries No change Accept
26 Does compression optionality break DSIG on WOFF? No Change Accept
27. Why "version 1.0" No change Accept
28. Summary appendix could conflict with normative sections Accept No reply
29. Mention of "extra data" superfluous Accept No reply
30. Move normative statements from introduction Accept Accept
31. Concern that metadata is not wellformed, due to @id Reject Accept
32. Content model unclear Accept No reply
33. Don't duplicate conformance requirements in an appendix Accept Accept
34. Some fields in OT header are not mentioned in WOFF spec Accept Accept

Comments and resolutions

Issue 1

Summary
WOFF does not pose any accessibility risks. No changes requested.
Raised by
Michael Cooper for WAI Protocols and Formats WG
Links
Michael Cooper | Chris Lilley
Proposed Resolution
Thanks. No change.
Reporter's response to resolution
Status
No changes requested or made.

Issue 2

Summary
Mention accessibility benefits in supporting materials.
Raised by
Michael Cooper for WAI Protocols and Formats WG
Links
Michael Cooper | Chris Lilley
Proposed Resolution
Supporting materials do mention benefits, will be further improved.
Reporter's response to resolution
Status
No changes to specification requested.

Issue 3

Summary
Put WOFF elements in a namespace
Raised by
Eric Muller, Adobe
Links
Christopher Slye for Eric Muller | Tal Leming | Chris Lilley | Eric Muller | Chris Lilley | Chris Lilley
Proposed Resolution
No change
Reporter's response to resolution
Accept
Status
Closed

Issue 4

Summary
Allow multiple <text> elements as child of <description>
Raised by
Eric Muller, Adobe
Links
Christopher Slye for Eric Muller | Tal Leming | Chris Lilley | Eric Muller | Chris Lilley
Proposed Resolution
Spec prose already allows this; change RNG to match
Reporter's response to resolution
Accept
Status
Chris edited RNG

Issue 5

Summary
Support pronunciation and sorting metadata with structured text
Raised by
Eric Muller, Adobe
Links
Christopher Slye for Eric Muller | Tal Leming | Chris Lilley
Proposed Resolution
No change
Reporter's response to resolution
Accept
Status
No Change

Issue 6

Summary
Extensibility by other namespaces
Raised by
Eric Muller, Adobe
Links
Christopher Slye for Eric Muller | Tal Leming | Chris Lilley
Proposed Resolution
No change
Reporter's response to resolution
Accept
Status
Closed

Issue 7

Summary
xsd:NCName is too constraining for lang attributes
Raised by
Eric Muller, Adobe
Links
Christopher Slye for Eric Muller | Tal Leming | Chris Lilley
Proposed Resolution
Agree, fix RNG
Reporter's response to resolution
Accept
Status
RNG has been updated

Issue 8

Summary
Add @url and @id to <text> elements inside <license>
Raised by
Eric Muller, Adobe
Links
Christopher Slye for Eric Muller | Tal Leming | Chris Lilley | Eric Muller | Chris Lilley
Proposed Resolution
Agree
Reporter's response to resolution
Accept
Status
Edited RNG and spec

Issue 9

Summary
I18n-ISSUE-2: Why not using xml:lang?
Raised by
Richard Ishida for I18N-Core WG
Links
Richard Ishida | Richard Ishida | Richard Ishida | Martin J. Dürst | Chris Lilley | Chris Lilley | Richard Ishida | Richard Ishida
Proposed Resolution
Accept; we will change to xml:lang
Reporter's response to resolution
Accept
Status
RNG updated to use xml:lang. Examples (apart from historical, real-world ones) updated to xml:lang. Spec edited.

Issue 10

Summary
I18n-ISSUE-4: Language tag references
Raised by
Richard Ishida for I18N-Core WG
Links
Internationalization Core Working Group Issue Tracker | Chris Lilley | Chris Lilley | Richard Ishida
Proposed Resolution
Accept; reference BCP47 rather than requiring a single tag from the IANA Subtag Registry
Reporter's response to resolution
Accept
Status
Spec has been edited

Issue 11

Summary
I18n-ISSUE-5: Use of attributes for human readable text
Raised by
Richard Ishida for I18N-Core WG
Links
Internationalization Core Working Group Issue Tracker | Chris Lilley
Proposed Resolution
Reject due to complexity/benefit tradeoff for these particular attributes
Reporter's response to resolution
Accept
Status
No change

Issue 12

Summary
I18N-ISSUE-6: Localization mechanism too restricted
Raised by
Richard Ishida for I18N-Core WG
Links
Richard Ishida | Tab Atkins | Richard Ishida | Chris Lilley | Richard Ishida
Proposed Resolution
No change in this version
Reporter's response to resolution
Accept
Status
No change, in this version.

Issue 13

Summary
I18N-ISSUE-7: Paragraphs and inline content
Raised by
Richard Ishida for I18N-Core WG
Links
Internationalization Core Working Group Issue Tracker | Chris Lilley | Chris Lilley | Sylvain Galineau | Chris Lilley Chris Lilley | Chris Lilley | Richard Ishida
Proposed Resolution
Agree; we will add div and span elements for this
Reporter's response to resolution
Accept
Status
Chris sent examples to list; Chris asked i18n for more examples; Jonathan has edited spec to add description and examples; Chris has edited RNG to add these and edited/revalidated examples.

Issue 14

Summary
I18N-ISSUE-8: Direction attributes needed
Raised by
Richard Ishida for I18N-Core WG
Links
15 Dec 2010 19:14:23 +0000 | 12 Jan 2011 15:49:52 +0100 | Kang-Hao (Kenny) Lu | Chris Lilley | Richard Ishida | Chris Lilley | Richard Ishida
Proposed Resolution
Accept; we will add @dir to metadata elements
Reporter's response to resolution
Accept
Status
Spec edit made. Richard offered to provide examples.

Issue 15

Summary
Description of text elements
Raised by
Richard Ishida
Links
Richard Ishida | Chris Lilley | Chris Lilley Richard Ishida | Chris Lilley
Proposed Resolution
We have clearly indicated the content model of these elements in the human-readable prose of the spec
Reporter's response to resolution
Status
Spec edited, but text element not described like the others.

Issue 16

Summary
I18N-ISSUE-9: OpenType feature preservation [WOFF]
Raised by
Richard Ishida for I18N-Core WG
Links
Richard Ishida | John Daggett | Christopher Slye | Vladimir Levantovsky | John Hudson | Christopher Slye | Addison Phillips
Proposed Resolution
Mostly out of scope for WOFF spec, but we will add an informative note.
Reporter's response to resolution
Accept
Status
Needs informative note added

Issue 17

Summary
Conflicting statements on WOFF font table order
Raised by
Julio Gonzalez
Links
Julio Gonzalez | Jonathan Kew | Julio Gonzalez | Jonathan Kew | Julio Gonzalez
Proposed Resolution
No change required for spec; commentor was confused by wording
Reporter's response to resolution
Accept
Status
Closed

Issue 18

Summary
license element text subelements
Raised by
Tal Leming
Links
Tal Leming | Sylvain Galineau
Proposed Resolution
Agree
Reporter's response to resolution
Agree
Status
Spec up to date, example added.

Issue 19

Summary
letting a URL carry information about the meaning of a resource is bad
Raised by
Bert Bos
Links
Bert Bos | Vladimir Levantovsky | Chris Lilley | Bert Bos | Liam R E Quin | Sylvain Galineau
Proposed Resolution
Reject, the claims of architectural violation and of the superiority of EOT asre not convincing
Reporter's response to resolution
Status
Clarification requested from commentor, no response, no change.

Issue 20

Summary
clear and careful language
Raised by
Bert Bos
Links
Bert Bos | Chris Lilley
Proposed Resolution
Thanks; no change
Reporter's response to resolution
Status
Closed

Issue 21

Summary
Why padding after private data block
Raised by
Bert Bos
Links
Bert Bos | Chris Lilley
Proposed Resolution
Agree; padding after private removed
Reporter's response to resolution
Status
Closed

Issue 22

Summary
Change metadata section to use XMP
Raised by
Bert Bos
Links
Bert Bos | Chris Lilley | Bert Bos | Chris Lilley
Proposed Resolution
Reject; large unmotivated change with no backwards compatibility
Reporter's response to resolution
Status
No response, no change

Issue 23

Summary
wasteful to use four bytes to store an origLength
Raised by
Bert Bos
Links
Bert Bos | Jonathan Kew | Bert Bos
Proposed Resolution
Reject: origLength avoids multiple passes on decompress
Reporter's response to resolution
Agree
Status
Closed

Issue 24

Summary
A context-free grammar for WOFF would be nice
Raised by
Bert Bos
Links
Bert Bos | Chris Lilley | Bert Bos | Chris Lilley
Proposed Resolution
Reject
Reporter's response to resolution
Status
No change

Issue 25

Summary
Why align tables to 4-byte boundaries
Raised by
Bert Bos
Links
Bert Bos | Chris Lilley
Proposed Resolution
No change
Reporter's response to resolution
Accept
Status
No change

Issue 26

Summary
Does compression optionality break DSIG on WOFF?
Raised by
Bert Bos
Links
Bert Bos | Chris Lilley
Proposed Resolution
No change, DSIG is not broken by WOFF
Reporter's response to resolution
Accept
Status
No change.

Issue 27

Summary
Why "version 1.0"
Raised by
Bert Bos
Links
Bert Bos | Chris Lilley | Bert Bos
Proposed Resolution
No change
Reporter's response to resolution
Accept
Status
Closed

Issue 28

Summary
Summary appendix could conflict with normative sections
Raised by
Bert Bos
Links
Bert Bos | Chris Lilley | Chris Lilley
Proposed Resolution
Agreed, remove section
Reporter's response to resolution
Status
Spec edited

Issue 29

Summary
Mention of "extra data" superfluous
Raised by
Bert Bos
Links
Bert Bos | Chris Lilley
Proposed Resolution
Remove entire section as condusing duplication
Reporter's response to resolution
Status
Spec edited

Issue 30

Summary
Move normative statements from introduction
Raised by
Steve Zilles
Links
Steve Zilles | Chris Lilley | Steve Zilles
Proposed Resolution
Agree; moved to new section
Reporter's response to resolution
Agree
Status
Spec edited.

Issue 31

Summary
Concern that metadata is not wellformed, due to @id
Raised by
Steve Zilles
Links
Steve Zilles | Chris Lilley | Steve Zilles
Proposed Resolution
Reject; commentor misunderstood spec, which has however been clarified
Reporter's response to resolution
Accept
Status
Closed

Issue 32

Summary
Content model unclear
Raised by
Steve Zilles
Links
Steve Zilles | Chris Lilley
Proposed Resolution
Agree; spec will clarify
Reporter's response to resolution
Status
Spec edited.

Issue 33

Summary
Don't duplicate conformance requirements in an appendix
Raised by
Steve Zilles
Links
Steve Zilles | Chris Lilley | Steve Zilles
Proposed Resolution
Agree
Reporter's response to resolution
Accept
Status
Section removed.

Issue 34

Summary
Some fields in OT header are not mentioned in WOFF spec
Raised by
Sergey Malkin
Links
Sergey Malkin | WebFonts WG
Proposed Resolution
Accept. WOFF spec should mentioned them in two places. First, it has to reference OpenType spec for calculation algorithm. And second, conformance requirements have to mention that these fields should be correct in original font to ensure complete roundtrip.
Reporter's response to resolution
Status
Spec edited.

Chris Lilley
$Id: issues-lc-2010.html,v 1.26 2011-07-13 16:32:02 clilley Exp $