
From nobody Fri Jul 15 12:49:34 2016
Return-Path: <wseltzer@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 A2F1512DD51 for <justfont@ietfa.amsl.com>; Fri, 15 Jul 2016 12:49:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.418
X-Spam-Level: 
X-Spam-Status: No, score=-2.418 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_SORBS_WEB=0.77, RP_MATCHES_RCVD=-1.287, 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 BS85D-26Q7kI for <justfont@ietfa.amsl.com>; Fri, 15 Jul 2016 12:49:31 -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 64AB612DD66 for <justfont@ietf.org>; Fri, 15 Jul 2016 12:49:30 -0700 (PDT)
Received: from [69.38.252.84] (helo=[192.168.97.130]) by raoul.w3.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <wseltzer@w3.org>) id 1bO973-0009ao-JJ; Fri, 15 Jul 2016 19:49:29 +0000
To: Chris Lilley <chris@w3.org>, justfont@ietf.org
References: <20160503182138.8226.20939.idtracker@ietfa.amsl.com> <57300FA8.2050505@w3.org> <5ec81e83-50dd-1b00-26bc-e79a1c773879@it.aoyama.ac.jp> <481dcbf5-af2e-0004-49ea-e33cf7e66104@w3.org>
From: Wendy Seltzer <wseltzer@w3.org>
Organization: W3C
Message-ID: <57893E49.30206@w3.org>
Date: Fri, 15 Jul 2016 15:49:29 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0
MIME-Version: 1.0
In-Reply-To: <481dcbf5-af2e-0004-49ea-e33cf7e66104@w3.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/justfont/BO2Xowh5Nv7WZaHZepKibZHmRmI>
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: Fri, 15 Jul 2016 19:49:33 -0000

We seem to have stalled here, though we're very close. Can anyone poke
at the three open issues to suggest resolutions?
https://github.com/svgeesus/ietf-justfont/issues

Chris, can you please review the open pull requests?
https://github.com/svgeesus/ietf-justfont/pulls

Thanks,
--Wendy

On 05/09/2016 01:49 PM, Chris Lilley wrote:
> 
> 
> 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!
> 
> 
> 
> _______________________________________________
> Justfont mailing list
> Justfont@ietf.org
> https://www.ietf.org/mailman/listinfo/justfont
> 


-- 
Wendy Seltzer -- wseltzer@w3.org +1.617.715.4883 (office)
Policy Counsel and Domain Lead, World Wide Web Consortium (W3C)
http://wendy.seltzer.org/        +1.617.863.0613 (mobile)



From nobody Tue Jul 26 08:17:50 2016
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 0BE0112DF8B for <justfont@ietfa.amsl.com>; Tue, 26 Jul 2016 08:17:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.187
X-Spam-Level: 
X-Spam-Status: No, score=-3.187 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-1.287, 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 GStVnQWxxl_k for <justfont@ietfa.amsl.com>; Tue, 26 Jul 2016 08:17:44 -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 3227412E017 for <justfont@ietf.org>; Tue, 26 Jul 2016 07:43:03 -0700 (PDT)
Received: from [2601:182:c500:59ca:25db:10ac:f9b4:75fc] by raoul.w3.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <chris@w3.org>) id 1bS3ZV-000AVX-OW; Tue, 26 Jul 2016 14:43:01 +0000
To: Wendy Seltzer <wseltzer@w3.org>, justfont@ietf.org
References: <20160503182138.8226.20939.idtracker@ietfa.amsl.com> <57300FA8.2050505@w3.org> <5ec81e83-50dd-1b00-26bc-e79a1c773879@it.aoyama.ac.jp> <481dcbf5-af2e-0004-49ea-e33cf7e66104@w3.org> <57893E49.30206@w3.org>
From: Chris Lilley <chris@w3.org>
Organization: W3C
Message-ID: <d5562c71-26e0-8816-5b37-99d8c6a1f453@w3.org>
Date: Tue, 26 Jul 2016 10:42:54 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <57893E49.30206@w3.org>
Content-Type: multipart/alternative; boundary="------------176D631F98530E9EB2A6A288"
Archived-At: <https://mailarchive.ietf.org/arch/msg/justfont/zatAQ0Yba_EpKnwBtPMYhrTy_oc>
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: Tue, 26 Jul 2016 15:17:49 -0000

This is a multi-part message in MIME format.
--------------176D631F98530E9EB2A6A288
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi Wendy

On 2016-07-15 15:49, Wendy Seltzer wrote:
> We seem to have stalled here, though we're very close. Can anyone poke
> at the three open issues to suggest resolutions?
> https://github.com/svgeesus/ietf-justfont/issues
*Wording too tentative*
https://github.com/svgeesus/ietf-justfont/issues/15

These were all in the "Background and Justification" section. The 
wording has been tightened up by
ea46d07. 
<https://github.com/svgeesus/ietf-justfont/commit/ea46d0788e6d1f7bf1143ce90fd985f5bc23994a> 
As this was editorial and trivial, I closed the issue

*Long sentences*
https://github.com/svgeesus/ietf-justfont/issues/16

I marked this as editorial and am going through looking for overly long 
sentences.

*Where are @font-face format identifiers defined?*
https://github.com/svgeesus/ietf-justfont/issues/14

This is substantive. To-date, the authoritative definition has been the 
CSS 3 Fonts specification (and before that, the CSS 2.0 specification). 
Thus my initial thought was that this should continue. Martin asked 
whether new registrations should give that info too, and I agree that 
they should. I

In that case, IANA would check for uniqueness (as they already do for 
subtype names) and the authoritative definition would be the 
registration itself (including the registrations included in the present 
document) and CSS 3 Fonts would update to state that the registrations 
are the official source, once the RFC was published.

It still seems useful to have a list of @font-face formats, so they 
would stay in CSS 3 Fonts as an informative list. The W3C errata 
mechanism could be used in the event of new registrations after CSS 3 
Fonts becomes a W3C Recommendation.

I recalled seeing a registration template in earlier MIME specifications 
and went looking for it. I had planned to copy it into the present 
document, adding the @font-face format field. However, reading through 
RFC 6838 it seems that this has been replaced by an online form:
http://www.iana.org/form/media-types

I have added this as an informative reference in the IANA considerations 
section. I have started to add a section on 'New Registrations' which 
points to this form, and also references the ABNF of section /4.2. 
Naming Requirements/ of RFC 6838 
<https://tools.ietf.org/html/rfc6838#section-4.2>. Should this document 
then state that it updates RFC 6838? How should we go about getting the 
online form updated to include the @font-face format to the "additional 
information" section of that form?

Also, is that form the sole way to do new registrations or is there 
still a textual template somewhere which people can edit as a plain text 
email for ietf-types as was done previously?

(Off topic, but it would also be good to know who to contact about 
updates to the form because it has a link to RFC 3013, which was 
obsoleted by RFC 7303; this should be corrected).


> Chris, can you please review the open pull requests?
> https://github.com/svgeesus/ietf-justfont/pulls
Both reviewed and merged

-- 
Chris Lilley
@svgeesus
Technical Director, W3C Interaction Domain


--------------176D631F98530E9EB2A6A288
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hi Wendy<br>
    <br>
    <div class="moz-cite-prefix">On 2016-07-15 15:49, Wendy Seltzer
      wrote:<br>
    </div>
    <blockquote cite="mid:57893E49.30206@w3.org" type="cite">
      <pre wrap="">We seem to have stalled here, though we're very close. Can anyone poke
at the three open issues to suggest resolutions?
<a class="moz-txt-link-freetext" href="https://github.com/svgeesus/ietf-justfont/issues">https://github.com/svgeesus/ietf-justfont/issues</a></pre>
    </blockquote>
    <b>Wording too tentative</b><br>
    <a href="https://github.com/svgeesus/ietf-justfont/issues/15">https://github.com/svgeesus/ietf-justfont/issues/15</a><br>
    <br>
    These were all in the "Background and Justification" section. The
    wording has been tightened up by<br>
    <a
href="https://github.com/svgeesus/ietf-justfont/commit/ea46d0788e6d1f7bf1143ce90fd985f5bc23994a"
      class="commit-link"><tt>ea46d07.</tt></a> As this was editorial
    and trivial, I closed the issue<br>
    <br>
    <b>Long sentences</b><br>
    <a href="https://github.com/svgeesus/ietf-justfont/issues/16">https://github.com/svgeesus/ietf-justfont/issues/16</a><br>
    <br>
    I marked this as editorial and am going through looking for overly
    long sentences.<br>
    <br>
    <b>Where are @font-face format identifiers defined?</b><br>
    <a href="https://github.com/svgeesus/ietf-justfont/issues/14">https://github.com/svgeesus/ietf-justfont/issues/14</a><br>
    <br>
    This is substantive. To-date, the authoritative definition has been
    the CSS 3 Fonts specification (and before that, the CSS 2.0
    specification). Thus my initial thought was that this should
    continue. Martin asked whether new registrations should give that
    info too, and I agree that they should. I<br>
    <br>
    In that case, IANA would check for uniqueness (as they already do
    for subtype names) and the authoritative definition would be the
    registration itself (including the registrations included in the
    present document) and CSS 3 Fonts would update to state that the
    registrations are the official source, once the RFC was published. <br>
    <br>
    It still seems useful to have a list of @font-face formats, so they
    would stay in CSS 3 Fonts as an informative list. The W3C errata
    mechanism could be used in the event of new registrations after CSS
    3 Fonts becomes a W3C Recommendation.<br>
    <br>
    I recalled seeing a registration template in earlier MIME
    specifications and went looking for it. I had planned to copy it
    into the present document, adding the @font-face format field.
    However, reading through RFC 6838 it seems that this has been
    replaced by an online form:<br>
    <a href="http://www.iana.org/form/media-types">http://www.iana.org/form/media-types</a><br>
    <br>
    I have added this as an informative reference in the IANA
    considerations section. I have started to add a section on 'New
    Registrations' which points to this form, and also references the
    ABNF of section <em>4.2. Naming Requirements</em> of <a
      href="https://tools.ietf.org/html/rfc6838#section-4.2">RFC 6838</a>.
    Should this document then state that it updates RFC 6838? How should
    we go about getting the online form updated to include the
    @font-face format to the "additional information" section of that
    form?<br>
    <br>
    Also, is that form the sole way to do new registrations or is there
    still a textual template somewhere which people can edit as a plain
    text email for ietf-types as was done previously?<br>
    <br>
    (Off topic, but it would also be good to know who to contact about
    updates to the form because it has a link to RFC 3013, which was
    obsoleted by RFC 7303; this should be corrected).<br>
    <br>
     <br>
    <blockquote cite="mid:57893E49.30206@w3.org" type="cite">
      <pre wrap="">Chris, can you please review the open pull requests?
<a class="moz-txt-link-freetext" href="https://github.com/svgeesus/ietf-justfont/pulls">https://github.com/svgeesus/ietf-justfont/pulls</a></pre>
    </blockquote>
    Both reviewed and merged<br>
    <br>
    <pre class="moz-signature" cols="72">-- 
Chris Lilley
@svgeesus
Technical Director, W3C Interaction Domain
</pre>
  </body>
</html>

--------------176D631F98530E9EB2A6A288--

