Re: [netmod] Status update on <draft-wu-netmod-yang-xml-doc-conventions-01>

Qin Wu <bill.wu@huawei.com> Wed, 30 May 2018 05:41 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B79512ECBE for <netmod@ietfa.amsl.com>; Tue, 29 May 2018 22:41:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_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 1us7UbLuOsC4 for <netmod@ietfa.amsl.com>; Tue, 29 May 2018 22:41:38 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0531D12F27D for <netmod@ietf.org>; Tue, 29 May 2018 22:41:38 -0700 (PDT)
Received: from lhreml707-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 25D1A20764F11; Wed, 30 May 2018 06:41:35 +0100 (IST)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml707-cah.china.huawei.com (10.201.108.48) with Microsoft SMTP Server (TLS) id 14.3.382.0; Wed, 30 May 2018 06:41:35 +0100
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.193]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0382.000; Wed, 30 May 2018 13:41:31 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
CC: "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] Status update on <draft-wu-netmod-yang-xml-doc-conventions-01>
Thread-Index: AQHT97P2/JSg9j4OKEuGkK1Py+kz/KRHeJEA///Bl4CAAIeWAA==
Date: Wed, 30 May 2018 05:41:31 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA9AE915D0@nkgeml513-mbx.china.huawei.com>
References: <B8F9A780D330094D99AF023C5877DABA9AE913E4@nkgeml513-mbx.china.huawei.com> <20180530053411.7scy2khghg75wlbz@anna.jacobs.jacobs-university.de>
In-Reply-To: <20180530053411.7scy2khghg75wlbz@anna.jacobs.jacobs-university.de>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.33.244]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/6rlgDrRrG6gmNtmTybYo-OlsLuw>
Subject: Re: [netmod] Status update on <draft-wu-netmod-yang-xml-doc-conventions-01>
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 May 2018 05:41:41 -0000

Good point, we will fix terminologies issues in the next update. 
Thanks, Juergen.

-Qin
-----邮件原件-----
发件人: Juergen Schoenwaelder [mailto:j.schoenwaelder@jacobs-university.de] 
发送时间: 2018年5月30日 13:34
收件人: Qin Wu
抄送: netmod@ietf.org
主题: Re: [netmod] Status update on <draft-wu-netmod-yang-xml-doc-conventions-01>

I think the title of the document is misleading. The convention for expressing YANG in XML is called YIN, defined in RFC 7950. There are other phrases that I find misleading, for example, Automatic Generation of Valid XML From Examples. For me, the example is the XML (or JSON) and what you call an example is the encoding of an XML in the RFC format and what you define is an RFC format qencoding and a decoding function. Perhaps it helps to properly define the terminology you use and then to go through the document to make sure terms are used consistently.

/js

On Wed, May 30, 2018 at 01:39:42AM +0000, Qin Wu wrote:
> Hi, WG:
> We have made an update Documentation Conventions for Expressing YANG in XML I-D based on last meeting discussion.
> The changes include:
> 1. Add JSON support.
> 2. Add objectives section
> 3. Consolidate Mandatory Boilerplate for both leaf node and metadata annotation.
> 4. Move complex case to Appendix.
> 5. Better Align abstract and introduction section with objectives sections.
> The diff is:
> https://www.ietf.org/rfcdiff?url2=draft-wu-netmod-yang-xml-doc-convent
> ions-01 We believe the v-(01) address all the comments in last meeting 
> and can serve a good basis to move to the next step.
> Thanks. Further Comments and suggestions are welcome.
> 
> -Qin
> -----邮件原件-----
> 发件人: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> 发送时间: 2018年5月30日 9:17
> 收件人: Benoit Claise; Qin Wu; Adrian Farrel; Benoît Claise
> 主题: New Version Notification for 
> draft-wu-netmod-yang-xml-doc-conventions-01.txt
> 
> 
> A new version of I-D, draft-wu-netmod-yang-xml-doc-conventions-01.txt
> has been successfully submitted by Qin Wu and posted to the IETF repository.
> 
> Name:		draft-wu-netmod-yang-xml-doc-conventions
> Revision:	01
> Title:		Documentation Conventions for Expressing YANG in XML
> Document date:	2018-05-29
> Group:		Individual Submission
> Pages:		10
> URL:            https://www.ietf.org/internet-drafts/draft-wu-netmod-yang-xml-doc-conventions-01.txt
> Status:         https://datatracker.ietf.org/doc/draft-wu-netmod-yang-xml-doc-conventions/
> Htmlized:       https://tools.ietf.org/html/draft-wu-netmod-yang-xml-doc-conventions-01
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-wu-netmod-yang-xml-doc-conventions
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-wu-netmod-yang-xml-doc-conventions-01
> 
> Abstract:
>    Many documents that define YANG modules also include artwork examples
>    presented in XML/JSON.
> 
>    IETF documentation has specific limits on line length and some
>    artwork examples such as XML examples have to include line wraps that
>    would not normally be allowed according to the XML representation
>    rules of RFC7950 and RFC7952.The same applies to JSON.
> 
>    This document lays out documentation conventions that allow YANG
>    examples to be presented in IETF documentation when XML/JSON encoded
>    YANG data instance would otherwise exceed the maximum line length and
>    provide consistent XML/JSON encoded YANG data node instance example
>    within an Internet-Draft or RFC.  There are no implications in this
>    document for YANG parsers: this document does not change the rules
>    for presenting YANG models or for encoding YANG in data files or in
>    the wire.
> 
>                                                                                   
> 
> 
> Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
> 
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103         <https://www.jacobs-university.de/>