Re: [netmod] WG Last Call: draft-ietf-netmod-schema-mount-07

Ladislav Lhotka <lhotka@nic.cz> Fri, 10 November 2017 15:38 UTC

Return-Path: <lhotka@nic.cz>
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 0C5E9126CC4 for <netmod@ietfa.amsl.com>; Fri, 10 Nov 2017 07:38:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 dZ5EtoiBPYbf for <netmod@ietfa.amsl.com>; Fri, 10 Nov 2017 07:38:34 -0800 (PST)
Received: from trail.lhotka.name (trail.lhotka.name [77.48.224.143]) by ietfa.amsl.com (Postfix) with ESMTP id A3459126C3D for <netmod@ietf.org>; Fri, 10 Nov 2017 07:38:34 -0800 (PST)
Received: by trail.lhotka.name (Postfix, from userid 109) id 9BC3318215DE; Fri, 10 Nov 2017 16:37:43 +0100 (CET)
Received: from localhost (nat-2.nic.cz [217.31.205.2]) by trail.lhotka.name (Postfix) with ESMTPSA id D670E1820F78; Fri, 10 Nov 2017 16:37:40 +0100 (CET)
From: Ladislav Lhotka <lhotka@nic.cz>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Robert Wilton <rwilton@cisco.com>
Cc: "netmod@ietf.org" <netmod@ietf.org>
In-Reply-To: <20171109181638.zel2otpzrptggvwz@elstar.local>
References: <47B1141C-8979-4910-B7CA-2114B9C0D352@juniper.net> <68c6a4d5-fd3e-efdb-9c34-f69f241d6a31@cisco.com> <874lq4oq94.fsf@nic.cz> <7d8a8b01-6d3b-ac29-dd58-f2771ecdad56@cisco.com> <87d14rjwdq.fsf@nic.cz> <56ea1907-c2ed-1940-089c-527b33f0723e@cisco.com> <20171109181638.zel2otpzrptggvwz@elstar.local>
Mail-Followup-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Robert Wilton <rwilton@cisco.com>, "netmod\@ietf.org" <netmod@ietf.org>
Date: Fri, 10 Nov 2017 16:39:36 +0100
Message-ID: <87lgje9m87.fsf@nic.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/R7xT8rIL6sdxcldqF8h60Q-F6cU>
Subject: Re: [netmod] WG Last Call: draft-ietf-netmod-schema-mount-07
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: Fri, 10 Nov 2017 15:38:37 -0000

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> writes:

> On Thu, Nov 09, 2017 at 05:38:40PM +0000, Robert Wilton wrote:
>> 
>> > > > > 3. Sec 2.1 Glossary of New Terms:  "Schema" isn't actually defined
>> > > > > anywhere (RFC 7950 doesn't define this).  Should it be defined here?
>> > > > > The NMDA datastores draft had a similar issue and we choose to define
>> > > > > "datastore schema" instead.
>> > > > I think the right place for defining the term "schema" (and "data model"
>> > > > as well) is the specification of YANG because it is desirable that all
>> > > > documents related to YANG use the same meaning.
>> > > OK, 7950 doesn't define it today.  Is that a problem?
>> > "Schema tree" and "schema node" are defined and used a lot in 7950, so
>> > it might be good to define "schema" as well - meaning the schema tree
>> > with all associated semantics.
>> OK, but we can't add definitions to 7950 now.  Would it make sense to add
>> the definition to the NMDA draft and reference that?
>
> So what is the difference between "schema tree" and "schema"? Or to
> put it differently, what is "all associated semantics" that you are
> adding to a "schema tree" to obtain a "schema"? RFC 7950 says:
>
>    o  schema tree: The definition hierarchy specified within a module.

As Rob points out, this is probably incorrect, as schema tree should
involve multiple modules. It makes no sense to talk about a schema tree
of an augmenting module unless we also take into account the augmented
module.

Anyway, schema tree is really just the hierarchy, i.e. a tree of schema
nodes, whereas schema is the hierarchy with datatypes, semantic rules
and all that. We can validate instance data against the schema, not
against the schema tree. This is at least how I understand it.

Lada

>
> If I understand 'definition hierarchy' correctly, than it seems
> "schema" is just an abbreviation of "schema tree", i.e., there is no
> semantic difference between these two terms. If there is a difference,
> we need to be able to spell it out.
>
> /js
>
> -- 
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
>
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod

-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67