Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove either embedded or referenced relationships #201

Open
johnwunder opened this issue Aug 6, 2014 · 3 comments
Open

Remove either embedded or referenced relationships #201

johnwunder opened this issue Aug 6, 2014 · 3 comments

Comments

@johnwunder
Copy link
Member

More specifically, are both necessary or can we normalize to a single approach for simplicity?

@sbarnum 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
@terrymacdonald
Copy link

Is it worth also talking about whether we need a separate 'top_level' relationship object as part of this discussion?

@gtback
Copy link
Contributor

gtback commented Aug 8, 2014

@tezzatheman , yes, this is likely related to the discussion of #70.

@johnwunder johnwunder changed the title Discuss use cases behind use of either embedded and referenced relationships Remove either embedded or referenced relationships Nov 3, 2014
@athiasjerome
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment