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

DM-001 - association of data objects #49

Closed
llorenzin opened this issue Jun 29, 2015 · 2 comments
Closed

DM-001 - association of data objects #49

llorenzin opened this issue Jun 29, 2015 · 2 comments

Comments

@llorenzin
Copy link

The draft currently states that that a data object should be associated with exactly one information model element - endpoint, IP address, asset, etc. Why? An IP address is not the same class of element as an endpoint; an IP address is one identifying aspect of an endpoint. So an attribute could be applicable to both an IP address and to the endpoint on which that IP address is configured. If the attribute collector is aware of the relationship between the IP address and the endpoint, are we saying that it must only publish the attribute on one or the other, but not both? This seems problematic.

@jimsch
Copy link
Contributor

jimsch commented Jul 3, 2015

This is the same as issue #38

@llorenzin
Copy link
Author

Fixed in -08 - clarified that the data model must include elements for each element in the information model, and may also include additional elements.

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

No branches or pull requests

2 participants