-
Notifications
You must be signed in to change notification settings - Fork 1
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
IM-001: Extensible Attribute Dictionary #24
Comments
Hi Jim, Please suggest a better wording....the intent is to ensure that the information model provides a required set (e.g. minimally) to ensure interoperability between data models. But also, I think there can be a very large set of attributes to achieve "posture", so the information model has to define the MUST (as 'the' minimum set) of attributes that a data model must support. Again, I am going by the basis that there is a single SACM information model that a data model must meet requirements.....a data model could be extended to have its own attributes but that could be for vendor differentiation or because there may be different types of applications (e.g. there may be apps that do more than posture so the data model would be richer in that sense). Does that help? |
Suggestion: |
That is a clear requirement. And it very clearly expresses what is a DM requirement that needs to be adhered to. Should there be a sentence along the lines of "The attribute dictionary should be defined with a clear mechanism for extensibility to enable future versions of the information model to be expanded with new attributes." |
I think the added sentence to Lisa's updates makes sense as well....will do in -05 |
Looks fine to me. |
Version -04
The text was updated successfully, but these errors were encountered: