They are attached. We plan to meet at the same time next week. Reminder to follow. --- Jim Minutes from Apr. '05 Telecon Attendees --------- Jim Pruyne Toshiyuki Nakata Heiko Ludwig Karl Czajkowski Agenda ------ - Heiko did updates to schema based on comments to 29. Multiplicity on the penalty and reward elements, and text to update. Introduced new 4.2.1 on term types to introduce extensibility for new term types. - Should we move obliged party up to the generic term definition? Does't seem to apply outside the SLA-like guarantee terms, so probably not. - Issue 34: Can we refine what a guarantee term points to? E.g. can we point to a particular method on a service rather than the service as a whole? Seems like a good idea. **Action: Add as suggested in the comment. Heiko to do this and add the text. - Issue 35: GuaranteeTerms may be specified relative to one another in terms of value/importance. This is pretty much already possible as specified, but there was consideration as to whether we could make it more specific about the expectation that some guarantees are more likely to fail. We're not sure right now how to specify that in a useful way, and the spec. already really covers the case, so we don't expect to make any changes on this right now. - Issue 36: THe concept is to be able to add a set of values for an objective based on various performance characteristics. The concept is a good one, but we can already capture this with various of guarantee terms. We'd rather wait until we have more experience rather than introduce this now since it is a conveince thing rather than a required thing. - Issue 27: Why is agreement name optional? Name's are not unique ids in any case, so we don't see how requiring the names helps. The agreement can be named by its EPR in any event if a unique id is needed. Some other contracts, e.g. mortgages, don't necessarily have a specific name on them. **Action: Add some text saying that the name is not a unique identifier, and that it is there for the purpose of "readability" of the agreement document. Heiko to add this comment. - How to review Karl's comments, and accept or reject so that are not change tracking marks all over. **Action: Jim to take editting pass to remove edit marks and commit them. Should clean up the doc. for editting purposes as we go forward. Will start with the next version from Heiko. - Jim should point out issues/topics in reminder rather than doing it on the fly. That lets people prepare better.