-
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
Section 2 - "assets and endpoints" #3
Comments
Hi Jim, Pragmatically, I would think there would be a (guidance) template that would already have defined the relevant assets for an endpoint class. So perhaps I can break it as you suggest to "Map the assets associated with an endpoint class".... I'm not sure I understand the last part of #3....the attributes are defined in the terminology and should be also in the information model. This "task" could exchange or publish information as part of the "creation" of such a template, though I think in cases I know today, they are constructed manually. Nancy. |
Removal of data elements makes the term attributes self evident. |
Agreed....the text has been updated to remove "data elements" |
This item is still missing the step of collecting the assets as a separate item. It should probably be there. Did you really mean to remove the "Define the assets" step from this? |
Fixed in -08 |
wfm |
Version -04
The text was updated successfully, but these errors were encountered: