ebcore — archive

[Pim van der Eijk]

Submitter's message Another update of the CPPA3 schema adds an option to white list or black list partners in CPPs, using new optional allowed and denied attributes. The attributes can be specified at one of four levels, so on one extreme they can apply to all communication and on another to an individual action in a service. The target of the attributes are party identifier lists that can be included in the CPP, or external to it. Lists can also reference other lists, allowing re-use. By default all parties are allowed and none denied. If an allowed list is specified, in CPA formation it is checked that the counterparty is on the list. If a denied list is specified, in CPA formation it is checked that the counterparty is not on the list. This functionality was requested for a community management system and allows parties to define the counter parties they are willing to engage with for all or some exchanges. You can think of the community management system as a social network, involving possibly very large numbers of parties. In theory anyone is free to want to exchange data with anyone else, but in practice parties tend to form sub-communities. The attributes can be thought of as an individual address book that parties can use to control who can connect to them. All comments welcome! The CPPA3 specification draft will be updated accordingly. -- Mr. Pim van der Eijk Document Name : cppa3.xsd Description Draft CPPA 3 specification and schema. Including embedded documentation but excluding generated HTML documentation. Download Latest Revision Public Download Link Submitter : Mr. Pim van der Eijk Group : OASIS ebXML Core (ebCore) TC Folder : Contributions Date submitted : 2016-12-14 14:15:08 Revision : 9