feat(party-relationship): specify the PartyRelationship archetype pattern with OpenAPI 2.0 #15
Open
1 of 10 tasks
Projects
Milestone
馃挕 TIP: Select the "Preview" Tab to help read these instructions.
1. Issue type
2. User story summary
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
Party
can have zero or morePartyRoles
.PartyRoles
havePartyRoleIdentifiers
that represent their uniqueness.PartyRelationships
specify the semantics in which eachParty
plays aPartyRole
.PartyRoles
can be associated withPartyRoleTypes
, which store common information about a set ofPartyRole
instances.PartyRelationshipTypes
can be associated withPartyRelationships
, which store common information about a set ofPartyRelationship
instances.PartyRelationshipConstraints
specify the names of thePartyRoles
that may adoptclient
andsupplier
(orbuyer
andseller
) sides of aPartyRelationship
of a specificPartyRelationshipType
.Responsibilities
describe activities that aPartyRoleType
is expected to perform.AssignedResponsibilities
representResponsibilities
assigned to specificPartyRoles
;AssignedResponsibilities
may (or may not) havefrom
andto
dates.PartySummary
objects provide "snapshots" of summary contact information about aParty
, in relation to a particular context.The text was updated successfully, but these errors were encountered: