Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Auth48: Should any drawings be sourcecode? #4948

Closed
MikeBishop opened this issue Feb 14, 2022 · 1 comment
Closed

Auth48: Should any drawings be sourcecode? #4948

MikeBishop opened this issue Feb 14, 2022 · 1 comment
Labels
-http editorial An issue that does not affect the design of the protocol; does not require consensus.

Comments

@MikeBishop
Copy link
Contributor

The RFC editor asks:

Note that we updated instances of 'artwork type="drawing"' to type="ascii-art". However, we wonder if any of these should be tagged as sourcecode instead. Please review.

Original (in the XML):
<artwork type="drawing" name="" align="left" alt="">

See https://authors.ietf.org/rfcxml-vocabulary#sourcecode for more information about sourcecode.

@MikeBishop MikeBishop added editorial An issue that does not affect the design of the protocol; does not require consensus. -http labels Feb 14, 2022
@MikeBishop
Copy link
Contributor Author

MikeBishop commented Feb 17, 2022

My XML-fixup PR will include the change from drawing to ascii-art. Having reviewed the artwork instances, they are all stream headers and frame layouts. The guidance for sourcecode says:

For artwork such as character-based art, diagrams of message layouts, and so on, use the <artwork> element instead.

Therefore, I'm going to close this issue and say no further change is needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-http editorial An issue that does not affect the design of the protocol; does not require consensus.
Projects
None yet
Development

No branches or pull requests

1 participant