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 requirements draft highlights (in ARCH-005, with a lower-case “must”) the need for every SACM Component to enable “announcement and negotiation of functional capabilities” and corresponding “inquiries about the capabilities of other components in the SACM ecosystem”.
If SACM Components are composed out of Building Blocks, Announcement and Negotiation, and Query (querying & getting queried) could be considered mandatory Building Blocks that MUST be part of every SACM Component. These would be Management Plane Building Blocks and corresponding definitions could be added to or extended in the terminology draft.
There might be more Building Blocks that could be Mandatory Building Blocks.
The text was updated successfully, but these errors were encountered:
Do we need to define "mandatory building blocks" or is it enough for such requirements to be implied in respective drafts with appropriate language (i.e. MUST)? If so, this seems like it might become an issue for the architecture draft.
The requirements draft highlights (in ARCH-005, with a lower-case “must”) the need for every SACM Component to enable “announcement and negotiation of functional capabilities” and corresponding “inquiries about the capabilities of other components in the SACM ecosystem”.
If SACM Components are composed out of Building Blocks, Announcement and Negotiation, and Query (querying & getting queried) could be considered mandatory Building Blocks that MUST be part of every SACM Component. These would be Management Plane Building Blocks and corresponding definitions could be added to or extended in the terminology draft.
There might be more Building Blocks that could be Mandatory Building Blocks.
The text was updated successfully, but these errors were encountered: