Loading...

XML

Word

Printable

Proposal:

Hide

Change "agreementID' and "agreementName" and other instances of UML attributes with "agreement" in the name, respective to "contractID" and "contractName" and so forth.

Show
Change "agreementID' and "agreementName" and other instances of UML attributes with "agreement" in the name, respective to "contractID" and "contractName" and so forth.
Resolution:

Hide

Through the document change the terminology. The overarching agreement that provides context for interactions might be called a market context, market rules agreement, a program, etc.

Note in document that a context is always present; a "counterparty" may or may not be.

We use the term "transaction" for "contract" and "tender" for "offer" to be consistent with the EMIX Public Review of November 2010; comments welcome during the EI Public Review.

Show
Through the document change the terminology. The overarching agreement that provides context for interactions might be called a market context, market rules agreement, a program, etc. Note in document that a context is always present; a "counterparty" may or may not be. We use the term "transaction" for "contract" and "tender" for "offer" to be consistent with the EMIX Public Review of November 2010; comments welcome during the EI Public Review.

Where a "program" was used in OpenADR, Sections 5 and 7 use "agreement" e.g. agreementID and agreementName as a generalization.

Section 6 uses the term "contract", e.g. contractID.

Since all of these are either agreements or contracts, both should use the same term. I suggest "contract" be used for all definitions.