First conversion of the STIX best practices to AsciiDoc #330
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…sciiDoc using existing CSS template Reference: oasis-tcs#323
TODO: Maybe found a better resolution or an SVG file to replace it
TODO: review the actual examples
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First step in converting the STIX best practices to AsciiDoc.
Some cleanup may still be required regarding quoting, references, and examples. One diagram will also need to be updated to have a better resolution than the original one from Google doc.
I propose merging this now so we can begin contributions and make the changes mentioned in #323 directly in the GitHub repository. This will help us avoid diverging too quickly from the original Google Docs. It will also allow contributors to see the history and changelog, and enable STIX 2 users to contribute as well.