Suggestion: Diagrams and Documents should include an Acronym Table

[packet-rat]

Suggestion: Diagrams and Documents should include an Acronym Table.

Although we are expanding the range of thought, much of the jargon around these topics might seem like "newspeak" to those we we are trying to engage/expose. All Acronyms in a given diagram or document should have the related term called out. Any new terms should have a brief explanation.

[warrenrjwc]

Hi Patrick We do have a terminology file in our github--> https://github.com/opencybersecurityalliance/documentation/blob/master/Architecture%20Documents/terminology.md . We also defines our terms via the ontology workgroup. Russ From: "Patrick Maroney" ***@***.***> To: "opencybersecurityalliance/documentation" ***@***.***> Cc: "Subscribed" ***@***.***> Date: 01/21/2022 09:45 AM Subject: [EXTERNAL] [opencybersecurityalliance/documentation] Suggestion: Diagrams and Documents should include an Acronym Table (Issue #38) Suggestion: Diagrams and Documents should include an Acronym Table. Although we are expanding the range of thought, much of the jargon around these topics might seem like "newspeak" to those we we are trying to engage/expose. All Acronyms in ZjQcmQRYFpfptBannerStart This Message Is From an External Sender This message came from outside your organization. ZjQcmQRYFpfptBannerEnd Suggestion: Diagrams and Documents should include an Acronym Table. Although we are expanding the range of thought, much of the jargon around these topics might seem like "newspeak" to those we we are trying to engage/expose. All Acronyms in a given diagram or document should have the related term called out. Any new terms should have a brief explanation. — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>