Re: [netmod] summary line in descriptions

On Wed, 2017-12-06 at 15:00 +0100, Martin Bjorklund wrote: > Ladislav Lhotka wrote: > > On Wed, 2017-12-06 at 14:51 +0100, Martin Bjorklund wrote: > > > Juergen Schoenwaelder wrote: > > > > I am not sure design decisions of some web clients

Re: [netmod] summary line in descriptions

Ladislav Lhotka wrote: > On Wed, 2017-12-06 at 14:51 +0100, Martin Bjorklund wrote: > > Juergen Schoenwaelder wrote: > > > I am not sure design decisions of some web clients that provide clumsy > > > user experience should impact how we write

Re: [netmod] summary line in descriptions

On Wed, 2017-12-06 at 14:51 +0100, Martin Bjorklund wrote: > Juergen Schoenwaelder wrote: > > I am not sure design decisions of some web clients that provide clumsy > > user experience should impact how we write data models. If we need > > summary lines, we

Re: [netmod] summary line in descriptions

Juergen Schoenwaelder wrote: > I am not sure design decisions of some web clients that provide clumsy > user experience should impact how we write data models. If we need > summary lines, we should properly separate them via > > ext:summary "this does

Re: [netmod] summary line in descriptions

I am not sure design decisions of some web clients that provide clumsy user experience should impact how we write data models. If we need summary lines, we should properly separate them via ext:summary "this does magic, see the description" instead of relying on conventions. /js On Wed, Dec

[netmod] summary line in descriptions

Hi, although detailed descriptions is a good thing, my recent experiences with web clients for RESTCONF indicate that they can become clumsy and unwieldy in such user interfaces. I think it would be useful to adopt a convention similar to Git commit messages: one relatively short summary line