Re: [netmod] Schema Mount Terminology Clarification

Rohit R Ranade <rohitrranade@huawei.com> Wed, 12 December 2018 11:08 UTC

Return-Path: <rohitrranade@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 85640130DBE for <netmod@ietfa.amsl.com>; Wed, 12 Dec 2018 03:08:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=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 fHHBBY3IZy56 for <netmod@ietfa.amsl.com>; Wed, 12 Dec 2018 03:08:32 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 BE88B12D4E8 for <netmod@ietf.org>; Wed, 12 Dec 2018 03:08:32 -0800 (PST)
Received: from LHREML711-CAH.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 1B8BEAEEA96C0; Wed, 12 Dec 2018 11:08:27 +0000 (GMT)
Received: from DGGEML424-HUB.china.huawei.com (10.1.199.41) by LHREML711-CAH.china.huawei.com (10.201.108.34) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 12 Dec 2018 11:08:27 +0000
Received: from DGGEML510-MBX.china.huawei.com ([169.254.2.202]) by dggeml424-hub.china.huawei.com ([10.1.199.41]) with mapi id 14.03.0415.000; Wed, 12 Dec 2018 19:08:16 +0800
From: Rohit R Ranade <rohitrranade@huawei.com>
To: Ladislav Lhotka <lhotka@nic.cz>, "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] Schema Mount Terminology Clarification
Thread-Index: AdSSAHJMd79djmViQCOmlgelvyOoWP//iC8A//9140A=
Date: Wed, 12 Dec 2018 11:08:16 +0000
Message-ID: <991B70D8B4112A4699D5C00DDBBF878A6BCA7E45@dggeml510-mbx.china.huawei.com>
References: <991B70D8B4112A4699D5C00DDBBF878A6BCA7DE4@dggeml510-mbx.china.huawei.com> <4ddfe88336e6528d079eb583dec7faa95ccf9a2d.camel@nic.cz>
In-Reply-To: <4ddfe88336e6528d079eb583dec7faa95ccf9a2d.camel@nic.cz>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.18.150.121]
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/NZa427rByvLBhSSAq80fQoMct1Y>
Subject: Re: [netmod] Schema Mount Terminology Clarification
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
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, 12 Dec 2018 11:08:39 -0000

Hi Lada,

Thank you for your response.
Please find some responses inline.

With Regards,
Rohit

-----Original Message-----
From: netmod [mailto:netmod-bounces@ietf.org] On Behalf Of Ladislav Lhotka
Sent: 12 December 2018 16:14
To: netmod@ietf.org
Subject: Re: [netmod] Schema Mount Terminology Clarification

Hi Rehat,

On Wed, 2018-12-12 at 10:12 +0000, Rohit R Ranade wrote:
> Hi,
>  
>  
> 1..       The term “data model” is used many times in this document, but it is
> not defined in this document but defined in RFC 7950. I think it 
> should be added under the “following terms are defined in [RFC7950]” part.

The definition of "data model" in RFC 7950 is too informal. What is meant by it in the schema mount document is basically "datastore schema" as defined in RFC 8342. Perhaps a better term would just be "schema".

>  
> 2..       The term “This document allows mounting of complete data models
> only” is used in Section 1. I think here “complete data model” should 
> be replaced by “schema tree” as it is more precise?

No, "schema tree" is only for a single module, accrding to the definition in 7950. What is meant here is a schema of multiple modules, as defined by YANG library.
[Rohit R Ranade] I agree. Maybe "complete schema trees" is better as mounting sub-hierarchies is not in scope for this document. I see that it has been used in Section 1 in the below statement . 
" With the "uses" approach, the complete schema tree of "ietf-interfaces" would have to be wrapped in a grouping ...... "

>  
> a)         RFC 7950 , schema tree: The definition hierarchy specified within a
> module
> b)   RFC7950, data model: A data model describes how data is represented and
> accessed
>  
> 3..       The “data model” term is used many times Eg: “LNE's data model”,
> “share the same data model”, “NI data model”, “mounting one data model
> consisting of any number of YANG modules”   etc, sometimes using the term
> “data model” as a collection of YANG modules and sometimes for a 
> single Yang module. I feel, where-ever we refer to single Module, we 
> need to use the term “schema tree” and when we refer to collection of 
> YANG modules, we can refer to as Data Model.. Please provide your opinions.

This was my original idea, but maybe it is better to use "schema" or "datastore schema" for the latter.
[Rohit R Ranade] I agree that term "schema" is indeed better. 

Lada

>  
> With Regards,
> Rohit
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
--
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67

_______________________________________________
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod