Yes/support. But with the condition that I would still like the draft
to define a basic common subset of markdown fields/annotations that
implementations would be expected to support. For clarity, I'm not
suggesting that the draft should define a new markdown language, I think
that it would be better to use an existing markdown language, but
perhaps simplified.
I want to avoid the scenario where each group of YANG modelers could
decide to use a different incompatible variant of text/markdown, and
hence generic tools would not be able to reliably render the markup for
a generic YANG module.
Care would need to be taken with which variant of the Markdown language
is chosen as a base (RFC 7764 may be of use) . E.g. the github markup
language has been previously suggested, but the specification document
for that variant is long (approx 120 pages).
Thanks,
Rob
On 10/04/2017 12:45, Ladislav Lhotka wrote:
As the author: yes/support.
Two changes seemed to have support in IETF 98 audience:
1. Apart from text/plain, the media type SHOULD be text/markdown
(variants permitted).
2. The "text-media-type" extension can appear anywhere in a (sub)module,
and will be scoped to the parent statement and its substaments (unless
overriden).
Lada
Kent Watsen <[email protected]> writes:
All,
This is start of a two-week poll on making the following draft a
NETMOD working group document:
draft-lhotka-netmod-yang-markup-00
Please send email to the list indicating "yes/support" or "no/do not
support". If indicating no, please state your reservations with the
document. If yes, please also feel free to provide comments you'd
like to see addressed once the document is a WG document.
Thank you,
NETMOD WG Chairs
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
