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
sbarnum
changed the title
Discuss use cases behind allowing both embedded and referenced relationships
Discuss use cases behind use of either embedded and referenced relationships
Aug 7, 2014
@tezzatheman , yes, this is likely related to the discussion of #70.
johnwunder
changed the title
Discuss use cases behind use of either embedded and referenced relationships
Remove either embedded or referenced relationships
Nov 3, 2014
having a 'top_level' relationship object makes STIX more flexible (all the effective/real relationships would not have to be defined in advance in this case: could seem easier)
However, just using this new top-object, and removing the relationships already defined would lead to potential inconsistency and less strict control of consistency.
Need more investigation
Suggest lesson learnt from OVAL
More specifically, are both necessary or can we normalize to a single approach for simplicity?
The text was updated successfully, but these errors were encountered: