As was discussed on the call, things that are going to be “left out” going forward, need to be called out – it could be in the spec, but probably we could use
some release notes.
Starting them now (as a google doc), as we make these decisions, would probably be the best way to capture all of our reasoning/discussions.
BTW - If we don’t have any specific best practices to suggest, that’s ok. In other words, having a defanging normative standard would not be necessary. Simply
say: “Any defanging is left as an implementation detail.”
From: [mailto:]
On Behalf Of Wunder, John A.
Sent: Tuesday, February 23, 2016 11:10 AM
To:
Subject: Re: [cti] CybOX Datatype Refactoring/Deprecation
If that’s what you’re saying, I agree. If users and vendors think it’s useful, I could see a group like us defining best practices for
defanging data in the UI.
