[mgmtprotocol] Requirements

[Andreas Maier <MAIERA@de.ibm.com>]

Some more:

- The specification needs to be completely agnostic to any specific CIM
schema / model. That means any future schema / model would need to be
supported automatically.

- We should do the specification in such a way that any code that
implements the specification can be as schema/model agnostic as possible. I
have serious doubts whether we achieve this. If it turns out I am right
here,  we will need to talk about tooling at some point that generates
model dependent code. We probably would not want to dig too deeply into
this, but what I want to make sure is that we are aware of such issues and
"ground" our decisions by taking them into account to the extent needed.

- We will need to support future versions of the CIM operations. Example
(not entirely out of the air because I have a CR pending on that): The
Associators operation gets an additional argument specifying a query string
to be applied to the target side objects. I suspect there are changes to
CIM operations that require new versions of our specification. This again
brings up the question how versions of our spec are synchronized with
versions of CIM operations specs. Probably some procedural mechanism needs
to be established.

Andy

Andreas R. Maier
IBM Senior Technical Staff Member, eServer Software Design
IBM Lab Boeblingen, maiera@de.ibm.com, Phone +49-7031-16-3654