Re: [Justfont] Review of draft-ietf-justfont-toplevel-05

"Chris Lilley" <chris@w3.org> Tue, 13 December 2016 19:44 UTC

Return-Path: <chris@w3.org>
X-Original-To: justfont@ietfa.amsl.com
Delivered-To: justfont@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6103F1294B9; Tue, 13 Dec 2016 11:44:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.796
X-Spam-Level:
X-Spam-Status: No, score=-4.796 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-2.896, SPF_HELO_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ia972Nv4mnzl; Tue, 13 Dec 2016 11:44:29 -0800 (PST)
Received: from raoul.w3.org (raoul.w3.org [IPv6:2001:470:8b2d:804:52:12:128:0]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B7D912946B; Tue, 13 Dec 2016 11:44:29 -0800 (PST)
Received: from 30-9-49.wireless.csail.mit.edu ([128.30.9.49]) by raoul.w3.org with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <chris@w3.org>) id 1cGt00-0004c4-Hu; Tue, 13 Dec 2016 19:44:28 +0000
Content-Type: multipart/alternative; boundary="----=_NextPart_51983308.532917481874"
MIME-Version: 1.0
Date: Tue, 13 Dec 2016 14:44:26 -0500
Message-ID: <d192e6b7-2efb-4846-8621-bd0227815cbe@getmailbird.com>
From: "Chris Lilley" <chris@w3.org>
To: "Dale R. Worley" <worley@ariadne.com>, "" <gen-art@ietf.org>
In-Reply-To: <148133938469.4670.11616216625013224080.idtracker@ietfa.amsl.com>
References: <148133938469.4670.11616216625013224080.idtracker@ietfa.amsl.com>
User-Agent: Mailbird/2.3.36.0
X-Mailbird-ID: d192e6b7-2efb-4846-8621-bd0227815cbe@getmailbird.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/justfont/5PMXAavWXxNd9YMJkSDtmwSkbeo>
Cc: justfont@ietf.org, ietf@ietf.org, draft-ietf-justfont-toplevel.all@ietf.org
Subject: Re: [Justfont] Review of draft-ietf-justfont-toplevel-05
X-BeenThere: justfont@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Font Top Level Media Type \(just font\) WG" <justfont.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/justfont>, <mailto:justfont-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/justfont/>
List-Post: <mailto:justfont@ietf.org>
List-Help: <mailto:justfont-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/justfont>, <mailto:justfont-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Dec 2016 19:44:31 -0000

On 2016-12-09 22:10:14, Dale Worley <worley@ariadne.com>; wrote:
Major issue:

Section 5.3.4, Collection Font Type (font/collection)

Fragment Identifiers A string, no longer than 63 characters and
restricted to the printable ASCII subset, codes 33 - 126,
except for the 10 characters '[', ']', '(', ')', '{', '}',
'<',>
'>', '/', '%'. If this string matches one of the PostScript
names (name ID=6) [ISO.14496-22.2015] in the name table, that
font is selected. For example, "#Foo-Bold" refers to the
font
with PostScript name Foo-Bold. If the name does not match,
or
if a fragment is not specified, the first font in the
collection is matched. Note that the order of fonts in
collections may change as the font is revised, so relying on
a
particular font in a collection always being first is unwise.

However, the characters '"', '#', '\', '^', '`', '|' are not
admissible in fragment identifiers, per RFC 3986.

It appears from ISO 14496-22 that those characters are allowed in font
PostScript names, so you probably want to enable the use of %-escapes
in fragment identifiers to represent those six characters.
Chris Lilley: 
Thank you for spotting this. I examined the grammar in RFC 3986 and agree that these six characters, which are allowed in PostScript names, would need to be percent escaped.

Because this subsection was getting a bit long (and appeared in two places) I created a new section on fragments for font collections. I added a list of characters to escape and added a second example with an escaped character. i clarified that the fragment is un-escaped prior to comparing with name table entries.

I also added a normative reference to RFC 3986.

I have submitted a new draft -06 with this change.

Minor issue:

>From my correspondence with the author, I think his intention is that
the parameter values should be case-insensitive. It seems to me that
RFC 6838 section 4.3 makes the values case-sensitive by default, so if
they are intended to be case insensitive, that needs to be specified.
Chris Lilley: 

I left these as case-sensitive per RFC 6838.

--
Chris Lilley
@svgeesus
Technical Director @ W3C
W3C Strategy Team, Core Web Design
W3C Architecture & Technology Team, Core Web & Media