Re: [YANG] keyref

Phil Shafer wrote:
> Andy Bierman writes:
>> Phil Shafer wrote:
>>> Andy Bierman writes:
>>>> IMO, leafref as a documentation clause does the same thing
>>>> but way simpler.  The DM reader should not have to be an expert
>>>> in Xpath, and need to hunt down the relevant documentation,
>>>> just to find out a leaf's data type.
>>> Are you saying you prefer this relationship to be defined in English
>>> words instead of a formal language?  The "description" statement
>>> for the leaf can provide the words, but we hope to provide something
>>> that a generic manager implementation can use to process module
>>> contents.
>> I already made a proposal -- instead of a builtin type called keyref
>> there would be an optional clause for a leaf of leaf-list called
>> leafref that has the path-stmt from the keyref as its argument.
> 
> Your proposal called this a "documentation clause", which implies
> something targeted to humans and not usable by software.  This
> would be bad, but I would live with a distinct statement for the
> ref target that is a formal target.

Yes -- only used like like an optional documentation clause,
but the argument would be the same path-stmt from keyref-stmt.

> 
> Thanks,
>  Phil
> 
> 

Andy

_______________________________________________
YANG mailing list
YANG@ietf.org
https://www1.ietf.org/mailman/listinfo/yang