Requiring a related party for every resource seems to be an overreach. MSISDN (for example) is a logical resource, would you really have a mandatory relationship to a support person for every MSISDN in the TELUS mobile inventory (millions)?
An alternative approach might be to identify the types of logical resource that really do need a support contact, and for those resource types only to have a mandatory characteristic that could point to the support contact, or directly to the contact medium.
Does this make sense?
------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------
Original Message:
Sent: May 16, 2022 10:52
From: Karen Aiken
Subject: RelatedParty: how to make one role required?
Thanks Jonathan -
This gets us most of the way - what I'm missing is how to then define the support role as being a required role, since RelatedParty is an optional attribute. The only way I can think to make support contact information required would be to extend RelatedParty as RelatedParty_Support, and making that a required property.
I'm not sure if we're over-engineering this.
Take care,
Karen
------------------------------
Karen Aiken
Strategy Manager, Integration Architecture
TELUS
Original Message:
Sent: May 16, 2022 06:11
From: Jonathan Goldberg
Subject: RelatedParty: how to make one role required?
RelatedParty is probably the best alternative. You could use a role of support, the RelatedParty pointer, and on the underlying related Party or PartyRole you have contact means.
Hope it helps
------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
Original Message:
Sent: May 12, 2022 13:22
From: Karen Aiken
Subject: RelatedParty: how to make one role required?
We're managing a logical resource inventory, where each resource has associated contact (support) information - I was looking at RelatedParty to support this, but since contact information is required for these resources, I'm not sure how best to handle, with RelatedParty being an array. Am I on the right track or is there a better method?
Appreciate any insights -
------------------------------
Karen Aiken
Strategy Manager, Integration Architecture
TELUS
------------------------------