-
Notifications
You must be signed in to change notification settings - Fork 6
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
SACM Operations #19
Comments
Hi, I agree that there should be an Operations section in the SACM Info Model. Cheers,
Ira McDonald (Musician / Software Architect) On Fri, Jul 17, 2015 at 6:28 PM, llorenzin notifications@github.com wrote:
|
I disagree. it makes much more sense for this type of information to be in the architecture document not this one. these are all independent of the IM. The only question would be the attributes needed to discover support, and it is not clear if that is protocol or IM based. |
I think I would like to see the operations enumerated in the architecture along with descriptions of the different SACM components and their capabilities. From there, we could capture any information needs (e.g. enumerations of capabilities, parameters necessary to support operations, etc.) in the IM. Does that seem reasonable? |
+1. In the alternate architecture, Jim and I have started doing some of this. More work is needed to complete this aspect. Dave From: Danny Haynes [mailto:notifications@github.com] I think I would like to see the operations enumerated in the architecture along with descriptions of the different SACM components and their capabilities. From there, we could capture any information needs (e.g. enumerations of capabilities, parameters necessary to support operations, etc.) in the IM. Does that seem reasonable? — |
Are there any objections to having the operations in the architecture? Please let me know by 11/8. If there are no objections, I will move this issue to the architecture issue tracker. |
I haven't any objections at this point. |
In the requirements document, we have requirements on the SACM operations (such as publishing, querying, etc.) My impression is that those high-level SACM operations need to be defined in the information model. Do we need to add an Operations section? If not, how will they be defined?
The text was updated successfully, but these errors were encountered: