Discussion: allowed "markup" in description about automation-working-group HOT 5 CLOSED

Markdown might be a good middle ground. It's still basic ASCII but allows for fairly rich formatting when rendered, and decent formatting when not rendered.

from automation-working-group.

Currently MITRE does not support formatting characters in descriptions for public ids and removes any present during ingest. If there is consensus for adding them, it would be good to first create some test ids and give the community time to evaluate whether products that use the descriptions can handle them.

from automation-working-group.

I'm a big fan of markdown. We'd definitely need to experiment with markdown for a while since consumers need to ensure they can consume it, as was mentioned, but they also need to ensure they will not render it since markdown like github flavored markdown allows embedded html which could lead to html injection

from automation-working-group.

@kurtseifried could we label this with a target json schema version? I would guess the very next version early next year might not be the best idea, but possibly the target version after that

from automation-working-group.

This issue is being closed as obsolete. If you feel it is still relevant to any currently running AWG initiatives, feel free to re-open it or open a new issue. Thank you!

from automation-working-group.