Re: [netmod] Module tags

Christian Hopps <chopps@chopps.org> Thu, 09 February 2017 12:19 UTC

Return-Path: <chopps@chopps.org>
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 741381299BB for <netmod@ietfa.amsl.com>; Thu, 9 Feb 2017 04:19:55 -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, RP_MATCHES_RCVD=-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 jUNrnkoo4aKa for <netmod@ietfa.amsl.com>; Thu, 9 Feb 2017 04:19:53 -0800 (PST)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id 37FD81299B0 for <netmod@ietf.org>; Thu, 9 Feb 2017 04:19:53 -0800 (PST)
Received: from tops.chopps.org (97-83-46-222.dhcp.trcy.mi.charter.com [97.83.46.222]) (using TLSv1.2 with cipher AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id 9545E623EC; Thu, 9 Feb 2017 12:19:51 +0000 (UTC)
References: <87r338gtzw.fsf@chopps.org> <20170209.085506.1418859449501855827.mbj@tail-f.com> <878tpfac43.fsf@chopps.org> <20170209.120823.198284779081114388.mbj@tail-f.com>
User-agent: mu4e 0.9.19; emacs 25.1.1
From: Christian Hopps <chopps@chopps.org>
To: Martin Bjorklund <mbj@tail-f.com>
In-reply-to: <20170209.120823.198284779081114388.mbj@tail-f.com>
Date: Thu, 09 Feb 2017 07:19:50 -0500
Message-ID: <874m03a74p.fsf@chopps.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/nDE--nK87WRIhJUek-df0Czldes>
Cc: netmod@ietf.org
Subject: Re: [netmod] Module tags
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 09 Feb 2017 12:19:55 -0000

Martin Bjorklund <mbj@tail-f.com> writes:

> Christian Hopps <chopps@chopps.org> wrote:
>>
>> Martin Bjorklund <mbj@tail-f.com> writes:
>> > Christian Hopps <chopps@chopps.org> wrote:
>> >> The reason I went with the grouping and in-module list was that I
>> >> thought one could then create selecting xpath expressions, e.g.,
>> >>
>> >>    get foobar-value[../tags="ietf:implements:foobar"]
>> >
>> > I'm not sure I understand what you're after, but I am pretty sure that
>> > if it can be done with a per-module structure that you propose, then
>> > it can also be done with a single structure.
>> >
>> > Is the idea that you want to read a certain leaf in a certain module,
>> > but only if that module has been dynamically tagged with a certain
>> > tag?
>>
>> Close, the idea was that I want to read all "foobar-value"s from all
>> modules that have that tag set.
>
> Ok. What is the use case?  It is probably not very common that
> multiple modules have the exact same data structure defined.

My example is fairly forward looking I guess. The key thing to note is:
"implements" in the tag name. The idea being that one has defined a
common structure (or interface) and then associated that interface with
a tag. Now a client can, with a single xpath expression, access a value
in all modules that implement that interface.

Thanks,
Chris.