Description: |
Do we want to keep the discussion about related agreements suspended? Or should we discuss and update the specification
accordingly?
If so:
1)
We need discussion about the kind of meta-information that each related agreement should be associated with.
In particular: do we need to define canonical types of relationships in the spec like we did before, such as dependency,
composition... I am referring to the different types of related agreements that started to be identified in OGSI-
Agreement (back in the day...).
2)
We may want to have a placeholder for domain-specific relationship type such as "advance reservation"... Which makes me
think that such as thing as "reservationID" could be a term more than a part of the context....
3)
Also, OGSI-Agreement says relationship can be modified at run-time: that is not in favor of specifying the related
agreements in the context. Or maybe those are only for relationships which cannot change during the lifecycle of the
agreement?
. |