Re: [Justfont] Working Group Last Call: draft-ietf-justfont-toplevel-02.txt
Chris Lilley <chris@w3.org> Mon, 09 May 2016 17:49 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 DD18512D5AC for <justfont@ietfa.amsl.com>; Mon, 9 May 2016 10:49:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level:
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.996, 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 UoCgmV4J9Fhi for <justfont@ietfa.amsl.com>; Mon, 9 May 2016 10:49:49 -0700 (PDT)
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 8FEF012D5A9 for <justfont@ietf.org>; Mon, 9 May 2016 10:49:49 -0700 (PDT)
Received: from [2620:0:1002:fd01:a5c3:2d5a:ac44:4b07] by raoul.w3.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <chris@w3.org>) id 1azpJT-000AJk-54 for justfont@ietf.org; Mon, 09 May 2016 17:49:48 +0000
To: justfont@ietf.org
References: <20160503182138.8226.20939.idtracker@ietfa.amsl.com> <57300FA8.2050505@w3.org> <5ec81e83-50dd-1b00-26bc-e79a1c773879@it.aoyama.ac.jp>
From: Chris Lilley <chris@w3.org>
Organization: W3C
Message-ID: <481dcbf5-af2e-0004-49ea-e33cf7e66104@w3.org>
Date: Mon, 09 May 2016 10:49:41 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <5ec81e83-50dd-1b00-26bc-e79a1c773879@it.aoyama.ac.jp>
Content-Type: multipart/alternative; boundary="------------93129D135AEDF4026D748558"
Archived-At: <http://mailarchive.ietf.org/arch/msg/justfont/bOnvLf6lPPwa9pUHI5_EATLdJ6g>
Subject: Re: [Justfont] Working Group Last Call: draft-ietf-justfont-toplevel-02.txt
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: Mon, 09 May 2016 17:49:52 -0000
On 16/05/09 03:45, Martin J. Dürst wrote: > >> Please review the draft carefully and raise any remaining issues here. > > > - The draft doesn't mention or reference RFC 6838 > (http://tools.ietf.org/html/rfc6838, Media Type Specifications and > Registration Procedures) at all, but it should definitely do so; in > particular, it should reference section 4.2.7., Additional Top-Level > Types. > (see https://github.com/svgeesus/ietf-justfont/pull/11) Agreed. I opened an issue for this https://github.com/svgeesus/ietf-justfont/issues/13 Your pull request neatly solves this, so i merged it and closed the issue again. > - The start of section 7 introduces @font-face format identifiers. It > uses the word "defined" for these, but only talks about the types > defined in the document itself. This raises the following questions: > - Are registrations of new subtypes supposed to give this > information, too? If yes, who is responsible to avoid conflicts? > (we could just ask IANA to check that the identifier doesn't clash > with that of another subtype) > - Will a future version of css-fonts-3 reference the IANA registry > for these values, or how will potential discrepancies be solved? > - If the information in css-fonts-3 is supposed to be normative, and > the information in the IANA registry just informative, then > clearly say so in the draft. This is a very good point. I have opened an issue https://github.com/svgeesus/ietf-justfont/issues/14 This requires discussion, as there are several options and it is not immediately clear which is best. > > The main editorial problems can be categorized as follows: > > - Repeated use of the word "believe", and other wordings that may be > appropriate at an early draft stage, but will look strange in a > published document, especially down the road. Noted. I added an editorial issue https://github.com/svgeesus/ietf-justfont/issues/15 and will review such wording. Suggestions for better wording 9or simply to cut particular parts of the text) very welcome. > - Many very long sentences that could easily be split up into shorter > ones. Yes. I added another editorial issue https://github.com/svgeesus/ietf-justfont/issues/16 Thanks for your careful review, Martin! -- Chris Lilley @svgeesus Technical Director, W3C Interaction Domain
- Re: [Justfont] Working Group Last Call: draft-iet… Wendy Seltzer
- [Justfont] I-D Action: draft-ietf-justfont-toplev… internet-drafts
- [Justfont] Working Group Last Call: draft-ietf-ju… Wendy Seltzer
- Re: [Justfont] Working Group Last Call: draft-iet… Martin J. Dürst
- Re: [Justfont] Working Group Last Call: draft-iet… Chris Lilley
- Re: [Justfont] Working Group Last Call: draft-iet… Chris Lilley
- Re: [Justfont] Working Group Last Call: draft-iet… Wendy Seltzer
- Re: [Justfont] Working Group Last Call: draft-iet… Martin J. Dürst
- [Justfont] Fwd: Re: Working Group Last Call: draf… Chris Lilley
- Re: [Justfont] Working Group Last Call: draft-iet… Alexey Melnikov