Re: [cacao] Terminology Committee Note

[Bret Jordan <bret.jordan@broadcom.com>]

My thoughts, after talking with Allan is, I think this is a good idea. We can capture the data as a committee note and rev it as needed. Then when we get ready to release the spec, we can either fold in certain content or reference it as needed. But by doing this, we stop having the same content in multiple places.ÂÂ

John, I assume that you will help flesh out the terminology and add extra content as needed? I can split the documents today and get new working drafts uploaded to Kavi.Â

Thanks,

Bret

PGP Fingerprint:Â63B4 FC53 680A 6B7D 1447 ÂF2C0 74F8 ACAE 7415 0050

"Without cryptography vihv vivc ce xhrnrw, however, the only thing that can not be unscrambled is an egg."

On Thu, Feb 20, 2020 at 12:05 PM John Morris <johnmorr@us.ibm.com> wrote:

Hi Allan,

Â

My thought was a singular doc to be shared as an input to multiple specs. That said it would have to be the case that, although there may be opinions resulting in multiple approaches, that there would still need to be agreement by the TC upon a single playbook terminology. Otherwise I suppose I would not be in favor of a committee note and we would require allowing it to diverge into two terminologies organic to each document.

Â

Thanks,

John

Â

----- Original message -----
From: Allan Thomson <athomson@lookingglasscyber.com>
Sent by: <cacao@lists.oasis-open.org>
To: John Morris <johnmorr@us.ibm.com>, "cacao@lists.oasis-open.org" <cacao@lists.oasis-open.org>
Cc:
Subject: [EXTERNAL] Re: [cacao] Terminology Committee Note
Date: Thu, Feb 20, 2020 1:53 PM
Â

Hi John

Â

1. I think itâs important we have agreement across the TC on terminology/taxonomy so agree we need to have it written down/captured.
2. Similarly its important to be able to revise and update it as the standards process progresses as we discover gaps or changes that we all agree need to be made.
3. From a practical nature of readability and use of terms in the specs, having to refer to multiple documents to understand specifications or read them, makes it harder on people to read and/or consume the specs. We just need to balance having too many docs vs readability/understandability on the primary spec(s).
   1. With online documents, this is easily solved by embedded a link in the spec to a separate definition/doc that contains the taxonomy/terminology. However, when you start distributing word docs and/or PDFs for the spec then you have to distribute 2 or more docs.
   2. In STIX/TAXII work, that TC started out with many sub-documents (for various reasons) but in the end the group decided to consolidated the docs into fewer docs for readability/use of the spec.

Â

Whether this TC wants to have separate docs or 1 document is up to the group.

Â

Howeverâ..

Â

If the decision is 2 documents then this group has to be willing to do the actual work of helping create and maintain those separate documents. Its easy to suggest changes but you need to be willing to help do the work also.

Â

Allan Thomson

CTO (+1-408-331-6646)

LookingGlass Cyber Solutions

Â

From: <cacao@lists.oasis-open.org> on behalf of John Morris <johnmorr@us.ibm.com>
Date: Thursday, February 20, 2020 at 9:10 AM
To: "cacao@lists.oasis-open.org" <cacao@lists.oasis-open.org>
Subject: [cacao] Terminology Committee Note

Â

THIS EMAIL ORIGINATES FROM OUTSIDE OF LOOKINGGLASS

Recently a minor, avoidable concern caused by a need to reconcile versions of the "Terminology" section across multiple documents led to the question of whether that content should be represented singly in a committee note. I'd like to support and open to further discussion this option in an effort to streamline reconciliation.

Â

For those not familiar with the instrument, the detail surrounding the form of a committee note may be found at:
https://oasis-open.org/policies-guidelines/oasis-defined-terms-2018-05-22#dCommitteeNote

Â

My Thanks,

John Morris
IBM CCOE

--------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

Â

--------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php