feat(party-relationship): specify the PartyRelationship archetype pattern with OpenAPI 2.0

[gregswindle]

💡 TIP: Select the "Preview" Tab to help read these instructions.

1. Issue type

Type the letter "x" in the "checkbox" the best describe this issue.

• Feature: I'm requesting an enhancement.

2. User story summary

Describe what you want to accomplish and in what role/capacity, and why it's important to you.
EXAMPLE:
As a Job Applicant,
I want to submit my resume
In order to be considered for a job opening.

As an API consumer,
I need to define and understand the roles and relationships between Parties
In order to communicate with, market and sell to or by good and services from.

3. Acceptance criteria

Replace the examples below with your own imperative, "true/false" statements for the behavior you expect to see, or the behavior that would be true if there were no errors (for defects).

• 1. A Party can have zero or more PartyRoles.
• 2. PartyRoles have PartyRoleIdentifiers that represent their uniqueness.
• 3. PartyRelationships specify the semantics in which each Party plays a PartyRole.
• 4. PartyRoles can be associated with PartyRoleTypes, which store common information about a set of PartyRole instances.
• 5. PartyRelationshipTypes can be associated with PartyRelationships, which store common information about a set of PartyRelationship instances.
• 6. PartyRelationshipConstraints specify the names of the PartyRoles that may adopt client and supplier (or buyer and seller) sides of a PartyRelationship of a specific PartyRelationshipType.
• 7. Responsibilities describe activities that a PartyRoleType is expected to perform.
• 8. AssignedResponsibilities represent Responsibilities assigned to specific PartyRoles; AssignedResponsibilities may (or may not) have from and to dates.
• 9. PartySummary objects provide "snapshots" of summary contact information about a Party, in relation to a particular context.