Re: CFD: eXIf 2017-05-31
Glenn Randers-Pehrson <[email protected]> Sat, 3 Jun 2017 07:07:40 -0400
| Newsgroups | gmane.comp.graphics.png.general |
|---|---|
| Message-ID | <CA+PdXcuQRsSJVLo63TNJRFCcAKb8vx-6ia_MgAJ_ED+XHi+wHA@mail.gmail.com> |
On Sat, Jun 3, 2017 at 6:27 AM, Pavel Zlatovratskii <[email protected]> wrote: > > 02.06.2017 20:52, Glenn Randers-Pehrson пишет: >> >> First off, it begins with "It is recommended..." >> > Ok. I find out that part of problem is my English... for me "recommended" is > pretty weak condition like "here is recommendations, but you may do as you > wish". > As of RFC 2119 "recommended" is much more strict condition, same as "should" > and prevent treatment "oh, just recommendation, don't care". > > To avoid such misunderstanding in future I propose to add reference to > RFC2119 (as marked in RFC). > > The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL > NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and > "OPTIONAL" in this document are to be interpreted as described in > RFC 2119. > > We have the following already in the PNG specification version 1.2. I suppose we could copy it into the png extensions document, where the eXIf chunk specification will reside if we approve it: <p>The words "must", "required", "should", "recommended", "may", and "optional" in this document are to be interpreted as described in RFC-2119, which is consistent with their plain English meanings. The word "can" carries the same force as "may". > May be it also will be nice to change word to 'should' which is same for > RFC, but more looks like caution (at least for me). However it will be not > important with reference to RFC. Glenn ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ png-mng-misc mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/png-mng-misc