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
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.
The text was updated successfully, but these errors were encountered:
Fixed in -08 - clarified that the data model must include elements for each element in the information model, and may also include additional elements.
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.
The text was updated successfully, but these errors were encountered: