On Tue, Mar 21, 2017 at 04:55:18PM +0100, Ladislav Lhotka wrote: > > > > > Single character flags work for me as well. Since I have modules with > > pretty complex RPC inputs (more than a single page in RFC formatting), > > I think it is useful to be able to see that one is still starting at > > an RPC input tree and not a regular data tree or a notification tree. > > Even with long RPC parameter lists the indentation should make it obvious > what belongs where. Another option might be to label every input parameter > with "xi" or "i" and output with "xo"/"o", and remove the "input" and > "output" nodes. This would make the output shorter and narrower. >
I wrote multiple pages - indentation is difficult to follow over page boundaries. > > So I tend to like Rob's proposal a bit more. > > Note however that Rob's proposal doesn't distinguish input and output > parameters, all are labelled with "x". > I know. At least I know I am still in an rpc/action definition. But yes, some of this may be personal preference. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany Fax: +49 421 200 3103 <http://www.jacobs-university.de/> _______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
