I've opened a pull request for these, in case that helps. https://github.com/alexisannerossi/id-svgsinrfcs/pull/7
On Fri, May 2, 2025, at 07:51, Martin Thomson wrote: > On Fri, May 2, 2025, at 04:20, Russ Housley wrote: >> Normative descriptions of protocols, >> systems, etc. must be fully represented in the text of the RFC, >> and must not be contingent on comprehension of any SVG. >> >> This is a MUST statement, but the use of "etc." makes it very vague. > > The operative part of the phrase there is "normative descriptions", not > the list. > > How about: > >> Normative descriptions in documents (for example, definitions of protocols, >> formats, or system architectures) must be fully represented in in the text >> of the RFC, and must not be contingent on the comprehension of SVG diagrams. > >> Also in Section 2: >> >> * SVGs must remain static after publication of the RFC, so there may >> be interactive, multimedia, or other elements that cannot be used. >> >> I think we need clarity on "cannot be used". I think you mean that >> these features of SVG cannot be included in the SVG. > > s/be used/be included in the SVG/, yes > > -- > rswg mailing list -- rswg@rfc-editor.org > To unsubscribe send an email to rswg-le...@rfc-editor.org -- rswg mailing list -- rswg@rfc-editor.org To unsubscribe send an email to rswg-le...@rfc-editor.org
