Agent CN Iteration3

refine the foundations (contracts, community spec, commitments) for community to community interactions
Use case:
1. user registers (enrolls) to community A
2. user requests to see the resources available in community A
3. Com A makes a contract for resources with com B on behalf of its members
4. user requests to see the resources available in community A (should be able to get access also to the resources provided by community B according to the contract between A and B)
  - case a) comm A does not project who owns the resources
  - case b) the user can see that the resources are owned by other communities. Community A just projects the resources.

High - Refine the model/relationship between contract and community specification to support community to community use case
High - Define interaction patterns for community to community use case
High - implement the community-to-community use case in Jade. No integration with Magnet so far.
Medium - Model refinement and tie the domain models together - community spec, contract, interaction pattern, commitment, rules, facts...
Medium - Design the Messaging Service use case - Identify the entities in the Messaging Service, domain models, and the scenarios between them. Relate the entities to the Org Specification. Example of contracts for the Messaging Service use case.
Medium - express the policies in the specification language, and not directly in Jess
Deferred - prototype algorithm to generate Jess rules from the a specification
Deferred - represent the contract explicitly (repository of contract templates, registry of instantiated contracts, etc)
Deferred - Define interaction patterns for Identity provider use cases
check compliance with the contract by logging and audit (or at runtime). Compliance is between two parties. The unit of measure for compliance is the commitment