Re: [netmod] [Netconf] Editorial comments on draft-kwatsen-netmod-artwork-folding-05

Qin Wu <> Wed, 27 June 2018 09:14 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B98B1130F36; Wed, 27 Jun 2018 02:14:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.19
X-Spam-Status: No, score=-4.19 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ZtxFfIjPPc9n; Wed, 27 Jun 2018 02:14:18 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 868451274D0; Wed, 27 Jun 2018 02:14:17 -0700 (PDT)
Received: from (unknown []) by Forcepoint Email with ESMTP id CDB0E9AEF4597; Wed, 27 Jun 2018 10:14:14 +0100 (IST)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.3.382.0; Wed, 27 Jun 2018 10:14:15 +0100
Received: from ([]) by ([]) with mapi id 14.03.0382.000; Wed, 27 Jun 2018 17:14:09 +0800
From: Qin Wu <>
To: Jonathan Hansford <>, "" <>, "" <>
Thread-Topic: Re[2]: [Netconf] Editorial comments on draft-kwatsen-netmod-artwork-folding-05
Thread-Index: AQHUDWTLzdC2PnbusEeeAmDnUALS0aRzuuFg//+NOICAAIsa4A==
Date: Wed, 27 Jun 2018 09:14:08 +0000
Message-ID: <>
References: <em6d922c27-30cd-41e3-806d-25669aa83a62@morpheus> <> <em8c3bc9ee-b8c9-4f97-aa0a-4f606d0b96e1@morpheus>
In-Reply-To: <em8c3bc9ee-b8c9-4f97-aa0a-4f606d0b96e1@morpheus>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA9AEB92BCnkgeml513mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [netmod] [Netconf] Editorial comments on draft-kwatsen-netmod-artwork-folding-05
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: NETMOD WG list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 27 Jun 2018 09:14:21 -0000

Good suggestion, thanks Jonathan.

发件人: Jonathan Hansford []
发送时间: 2018年6月27日 16:55
收件人: Qin Wu;;
主题: Re[2]: [Netconf] Editorial comments on draft-kwatsen-netmod-artwork-folding-05

Re Section 4.1, 2nd paragraph, can I suggest the first sentence be reworded along the lines of "Fundamentally, the issue is whether the artwork remains readable once folded." And I would add that sentence to the end of the previous paragraph and start paragraph 2 afterwards.

------ Original Message ------
From: "Qin Wu" <<>>
To: "Jonathan Hansford" <<>>; "<>" <<>>; "<>" <<>>
Sent: 27/06/2018 09:09:47
Subject: RE: [Netconf] Editorial comments on draft-kwatsen-netmod-artwork-folding-05

Thanks Jonathan for comments, please see my reply inline below.

发件人: Netconf [<>] 代表 Jonathan Hansford
发送时间: 2018年6月26日 23:46
主题: [Netconf] Editorial comments on draft-kwatsen-netmod-artwork-folding-05


Just a few editorial comments on draft-kwatsen-netmod-artwork-folding-05:

  *   General:

     *   Though there is a header to indicate where the artwork starts, there is no footer to indicate where it ends. How would a parser know when to stop?
[Qin]: Good point, if you follows netmod discussion, Martin has similar suggestion. We need to decide whether we should support fold framing or extract artwork based on header and footer in this draft.

     *   Should the header (and footer) be deleted for any artwork that does not require folding?
[Qin]If we allow the user to specify maximum length limit for each line, I think header and footer is not needed,
        If we use header and footer to indicate where the line start and where the line end, header and footer is only needed during artwork extraction phase.

  *   Section 4.1:

     *   1st paragraph: A very minor issue, but "e.g." and "etc." should not be used in the same list. "e.g." is used for a list of examples and by implication isn't complete, therefore "etc." is already inferred.
                          [Qin]: Okay.

     *   2nd paragraph:

        *   Not sure what the 1st sentence is saying.
                      [Qin] Suppose the artwork is a table, the table needs to be folded, folding result may look bad.

        *   2nd sentence: s/susceptible is/susceptible to
        *   3rd sentence: s/fair/fairs
                    [Qin]: Okay, thanks.

  *   Section 4.2, 3rd paragraph, 1st sentence: repetition of "out" - one of them needs removing
  *   Section 5.2:

     *   2nd paragraph, 1st sentence: s/than then/than the
     *   3rd paragraph, 1st sentence: s/be lead/lead
               [Qin]: Okay, thanks.

  *   Section 5.3:

     *   2nd paragraph: s/Caluculate/Calculate
     *   4th paragraph: Arguably this should be from bottom-to-top as, going from top-to-bottom, once you have concatenated two lines the '\' will not be on the folding-column
            [Qin]:In our code, we will delete unneeded ‘\’ line by line from top to bottom. I think whether from bottom to top or from top to bottom, it doesn’t matter since it is implementation specific.