Interesting observation about point cut, Robert.

For the case of the "inactive" attribute that has been discussed in the past, 
as well as the "last-modified" attribute discussed in the draft, the intent 
would be to allow it everywhere, so the need for point cut isn't there.

Can you think of some metadata examples that would apply to only a subset of 
the nodes?

I recall a related conversation from before where we concluded that we want 
attributes to only ever be used as metadata (never data), which is why they are 
defined in a global way.  I fear that the point cut approach might bring some 
of that concern back...

Thanks,
Kent

From: Robert Varga <n...@hq.sk<mailto:n...@hq.sk>>
Date: Tuesday, October 13, 2015 at 11:26 AM
To: Kent Watsen <kwat...@juniper.net<mailto:kwat...@juniper.net>>, 
"netmod@ietf.org<mailto:netmod@ietf.org>" 
<netmod@ietf.org<mailto:netmod@ietf.org>>
Subject: Re: [netmod] WG Last Call for draft-ietf-netmod-yang-metadata-02 
(until 2015-10-22)

On 10/07/2015 07:37 PM, Kent Watsen wrote:

This is a notice to start a NETMOD WG last call for the document:

Defining and Using Metadata with YANG
http://tools.ietf.org/html/draft-ietf-netmod-yang-metadata-02


I have read the document, and coming in without the previous discussions, 
md:annotation instances feel like aspects (from aspect-oriented programming) 
being attached to pre-defined models to address a cross-cutting concern. 
Unfortunately it seems it lacks an equivalent of pointcut specification, e.g. a 
machine-readable definition where/when a particular annotation is valid.

This makes annotations disconnected from the YANG metamodel, which is not 
desirable for systems strictly based on the metamodel, as each instance of an 
annotation will require hand-written code.

My question is whether it would make sense to define some sort of (optional) 
pointcut specification to be carried within the md:annotation statement (such 
as an explicit list of data nodes, or a 'when' statement or similar)?

That would allow us to bind some/most md:annotation instances automagically to 
the metamodel, reducing the need to hand-code their semantics.

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

Reply via email to