Re: Grammatical corrections to the headers and boilerplate text

Stewart Bryant <stewart.bryant@xxxxxxxxx> · Tue, 13 Feb 2018 08:37:29 +0000



    This may be a US vs UK English thing, but I agree with LLoyd, the
      original seems quite correct to me.

    
    In the original the text we consider a (single) member of the
      set: [Documents approved by...] as a candidate for publication one
      by one, each on their own merits.

    
    - Stewart

    
    On 13/02/2018 08:08,
      lloyd.wood@xxxxxxxxxxx wrote:

    
      The thing that bugs me is that it's not, strictly
        speaking, a grammatical error.

        
        And that's because of the 'not', which excuses so much.

        
        Lions are not a wallaby.

        Cities are not countryside.

        
        Plurals are not singular.

        
        ...are all grammatically fine.

        
        I'd be more concerned about correct use of

        erratum/errata and datum/data... It's an "RFC Erratum report"!
      

        Lloyd Wood lloyd.wood@xxxxxxxxxxx
        http://about.me/lloydwood
        

        ________________________________
        

          From: Russ Housley <housley@xxxxxxxxxxxx>

          To: IETF <ietf@xxxxxxxx>
          

          Sent: Saturday, 10 February 2018, 5:24

          Subject: Re: Grammatical corrections to the headers and
          boilerplate text

          
          If I have read this properly, the revised paragraph does not
          appear in the Internet-Draft boilerplate.  Did I get that
          right?

          
          Russ

          
          > On Feb 9, 2018, at 12:46 PM, Robert Sparks <rjsparks@xxxxxxxxxxx>
          wrote:

          
          > 

          
          > The IAB recently accepted an erratum <https://www.rfc-editor.org/errata/eid5248>
          that pointed out a grammatical error in the boilerplate text
          templates in RFC 7841.  While reviewing the erratum, we
          noticed a similar error in the text for non-standards-track
          IETF-stream RFCs and verified that the IESG was ok correcting
          that error as well.

          
          > 

          
          > The header and boilerplate text is now maintained on a
          web page, <https://www.iab.org/documents/headers-boilerplate>,
          and we have updated that page and requested update of the
          relevant tools maintained by the IETF.  If you have your own
          tools for the generation of this text, please update them to
          reflect the update text.

          
          > 

          
          > Robert Sparks

          
          > for the IAB

          
          >