Lada writes:
> Andy writes:
>>IMO, the yang-data defined in RFC 8040 has a clear purpose, and it
>>is sufficient for that purpose, which is a YANG representation of
>>an instance document (such as a protocol message or file).
>
> The same is basically true even without the extension. For example,
On Mon, Apr 30, 2018 at 7:09 AM, Ladislav Lhotka wrote:
> Andy Bierman writes:
>
> > On Fri, Apr 27, 2018 at 8:13 AM, Ladislav Lhotka wrote:
> >
> >> On Fri, 2018-04-27 at 16:47 +0200, Juergen Schoenwaelder wrote:
> >> > On Fri, Apr 27, 2018 at 04:34:38PM +0200, Ladislav Lhotka wrote:
> >> >
>
>Martin wrote before:
> No I was thinking along the lines of:
>
> ydx:yang-data my-first-rpc-error-info {
>...
> }
>
> rpc my-first-rpc {
>...
>opx:error-info-structure my-first-rpc-error-info;
> }
>
> I.e., use yang-data to define a structure, and use another statement
> to tie t
Andy Bierman writes:
> On Fri, Apr 27, 2018 at 8:13 AM, Ladislav Lhotka wrote:
>
>> On Fri, 2018-04-27 at 16:47 +0200, Juergen Schoenwaelder wrote:
>> > On Fri, Apr 27, 2018 at 04:34:38PM +0200, Ladislav Lhotka wrote:
>> >
>> > > [...] define a special datastore for it, such as "error-messages".