Re: [netmod] Comments on instance data draft rev -02 - Change target-module to what name?

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Mon, 25 March 2019 23:17 UTC

Return-Path: <j.schoenwaelder@jacobs-university.de>
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 5AD0B12014D for <netmod@ietfa.amsl.com>; Mon, 25 Mar 2019 16:17:51 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001] 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 h9KosKwf30BN for <netmod@ietfa.amsl.com>; Mon, 25 Mar 2019 16:17:49 -0700 (PDT)
Received: from atlas5.jacobs-university.de (atlas5.jacobs-university.de [212.201.44.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EEC512014C for <netmod@ietf.org>; Mon, 25 Mar 2019 16:17:47 -0700 (PDT)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas5.jacobs-university.de (Postfix) with ESMTP id 7E1D337; Tue, 26 Mar 2019 00:17:46 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas5.jacobs-university.de ([10.70.0.217]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10032) with ESMTP id jIkeG7-naQkI; Tue, 26 Mar 2019 00:17:46 +0100 (CET)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "Jacobs University CA - G01" (verified OK)) by atlas5.jacobs-university.de (Postfix) with ESMTPS; Tue, 26 Mar 2019 00:17:46 +0100 (CET)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by hermes.jacobs-university.de (Postfix) with ESMTP id 3D81C200A8; Tue, 26 Mar 2019 00:17:46 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10028) with ESMTP id nQog1fiuoeMX; Tue, 26 Mar 2019 00:17:45 +0100 (CET)
Received: from exchange.jacobs-university.de (SXCHMB01.jacobs.jacobs-university.de [10.70.0.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "exchange.jacobs-university.de", Issuer "DFN-Verein Global Issuing CA" (verified OK)) by hermes.jacobs-university.de (Postfix) with ESMTPS id C17A8200A7; Tue, 26 Mar 2019 00:17:45 +0100 (CET)
Received: from anna.localdomain (10.50.218.117) by sxchmb03.jacobs.jacobs-university.de (10.70.0.155) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.1591.10; Tue, 26 Mar 2019 00:17:45 +0100
Received: by anna.localdomain (Postfix, from userid 501) id C7ECC30078EA05; Tue, 26 Mar 2019 00:17:44 +0100 (CET)
Date: Tue, 26 Mar 2019 00:17:44 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: =?utf-8?Q?Bal=C3=A1zs?= Lengyel <balazs.lengyel@ericsson.com>
CC: Joe Clarke <jclarke@cisco.com>, "netmod@ietf.org" <netmod@ietf.org>
Message-ID: <20190325231744.hj534aep3jbxardv@anna.jacobs.jacobs-university.de>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: =?utf-8?Q?Bal=C3=A1zs?= Lengyel <balazs.lengyel@ericsson.com>, Joe Clarke <jclarke@cisco.com>, "netmod@ietf.org" <netmod@ietf.org>
References: <5f17a293-346e-b469-e78f-8933a7650db4@cisco.com> <9b9aebc0-3f72-9724-4a0b-c3587d16b65d@ericsson.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
In-Reply-To: <9b9aebc0-3f72-9724-4a0b-c3587d16b65d@ericsson.com>
User-Agent: NeoMutt/20180716
X-ClientProxiedBy: SXCHMB04.jacobs.jacobs-university.de (10.70.0.156) To sxchmb03.jacobs.jacobs-university.de (10.70.0.155)
X-Clacks-Overhead: GNU Terry Pratchett
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/iwRVBS96rxeKPe2iWuk0ueZsV-0>
Subject: Re: [netmod] Comments on instance data draft rev -02 - Change target-module to what name?
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: Mon, 25 Mar 2019 23:17:51 -0000

For me, it seems obvious that we talk about the schema of the instance
data (content). (The other schema defining the format of the instance
data file is fixed and it would be pointless to include it.) Anyway,
we should look at the existing definitions. RFC 8342 defines:

   o  datastore schema: The combined set of schema nodes for all modules
      supported by a particular datastore, taking into consideration any
      deviations and enabled features for that datastore.

So perhaps you want to define the term 'instance data schema' or
something like that. Within the model, however, I would prefer to use
simple and short names, that is s/target/schema/.

/js

On Mon, Mar 25, 2019 at 10:36:42PM +0000, Balázs Lengyel wrote:
>    While I agree that target might not be the best name, I want a name that
>    describes that
>    "these are the modules I am providing instance data for".
> 
>    I propose to use the terms:
>    "content-schema" and "content defining Yang module(s)" (Sometimes I need
>    to refer them individually.)
> 
> 
>    Just schema is a too generic word. It does not tell you which schema are
>    we speaking about? The schema for ietf-yang-instance-data,or the schema
>    just for the content part? Are we speaking about individual modules or the
>    collection of all target modules?
> 
>    regards Balazs
> 
>    On 2019. 03. 25. 14:29, Joe Clarke wrote:
> 
>  First, I agree with Jürgen that the "target" terminology confused me,
>  especially so given you have target-module and inline-target-spec.  Like
>  Jürgen and Rob said, "schema" seems to work better.  And maybe
>  "inline-schema-module-spec" would be clearer that the spec modifies the
>  modules from which the schema is generated.
> 
>  --
>  Balazs Lengyel                       Ericsson Hungary Ltd.
>  Senior Specialist
>  Mobile: +36-70-330-7909              email: [1]Balazs.Lengyel@ericsson.com
> 
> References
> 
>    Visible links
>    1. mailto:Balazs.Lengyel@ericsson.com



> _______________________________________________
> 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/>