You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes the meaning of CTIM vocabulary values isn't self evident. For example, there are many types of Observable Object, and at least some of them are potentially esoteric or ambiguous. A recent example is processor ID, which I think is an x86-specific hex number that identifies an x86 processor model.
STIX documentation includes descriptions for all vocabulary values. It would be ideal if CTIM had a way to attach (optional) documentation to each value too.
Explore options and propose a solution for feedback from stakeholders
Implement solution. No need to add many descriptions now. The idea is enable the ability to add descriptions so it's possible to enrich docs going forward.
The text was updated successfully, but these errors were encountered:
Sometimes the meaning of CTIM vocabulary values isn't self evident. For example, there are many types of Observable Object, and at least some of them are potentially esoteric or ambiguous. A recent example is processor ID, which I think is an x86-specific hex number that identifies an x86 processor model.
STIX documentation includes descriptions for all vocabulary values. It would be ideal if CTIM had a way to attach (optional) documentation to each value too.
The text was updated successfully, but these errors were encountered: