Open APIs

Dear Colleagues, 
may be you can help me with the following question.

Our customer just asked me to process (GET/PUT/PATCH/DELETE) "Power of Attorney" (POA) documents.

This POA entity is associated with given agreement (one agreement may have many specific POAs - each POA for specific action (create a bill, ask a balance, add a new service, etc) and for specific person). POA entity authorizes the person (to make certain action) on behalf of the agreement signer.

POA has an issue date, validity period (from - to), "issued to"  person, "issued by" person.

Unfortunately, i haven't find a "Power of Attorney" entity in the SID model.

1) May be i missed it and this enity exists somewhere?:) 
2) My suggestion is to create this entity as a child from Agreement entity and store POAs linked with agreement in the associatedAgreement field of Agreement entity.
The external system can inspect the "type" field to differ between "simple" Agreement and POA.


Any suggestions? 

Big thanks in advance!



------------------------------
Vadim Nechaev
Senior systems architect
MTS Group HQ
------------------------------

Hi Vadim
You posted this in the Open API community forum, perhaps you should post in the Frameworx forum as well (https://engage.tmforum.org/communities/community-home/digestviewer?communitykey=019f32c2-82b7-427f-8156-f9262fe138fe&tab=digestviewer).
In any case I also do not recall a specific power-of-attorney entity in the SID, and certainly there is not one in the Open API model.
One could perhaps argue that a POA is a Document, for which there is a model in the Open API (but not in the SID, which currently has only Attachment).  The question arises as to whether there is sufficient semantic behavior for a POA that warrants it being modeled separately.
But the SID leaders @Michel Besson and @Cecile Ludwichowski might be able to give more clarity on the SID aspects.​​

------------------------------
Jonathan Goldberg
Amdocs Management Limited
------------------------------

Original Message:
Sent: Nov 29, 2018 04:23
From: Vadim Nechaev
Subject: Power of attorney

Dear Colleagues,
may be you can help me with the following question.

Our customer just asked me to process (GET/PUT/PATCH/DELETE) "Power of Attorney" (POA) documents.

This POA entity is associated with given agreement (one agreement may have many specific POAs - each POA for specific action (create a bill, ask a balance, add a new service, etc) and for specific person). POA entity authorizes the person (to make certain action) on behalf of the agreement signer.

POA has an issue date, validity period (from - to), "issued to"  person, "issued by" person.

Unfortunately, i haven't find a "Power of Attorney" entity in the SID model.

1) May be i missed it and this enity exists somewhere?:)
2) My suggestion is to create this entity as a child from Agreement entity and store POAs linked with agreement in the associatedAgreement field of Agreement entity.
The external system can inspect the "type" field to differ between "simple" Agreement and POA.


Any suggestions?

Big thanks in advance!



------------------------------
Vadim Nechaev
Senior systems architect
MTS Group HQ
------------------------------

Hi Jonathan

Thank you very much for your quick reply (absence of POA - it was specially important for us), clarifications and detailed instructions! I noted your hint about SID Model/Open API Model - i will try to dig more information about difference between these models. 


------------------------------
Vadim Nechaev
Senior systems architect
MTS Group HQ
------------------------------

Original Message:
Sent: Dec 02, 2018 01:52
From: Jonathan Goldberg
Subject: Power of attorney

Hi Vadim
You posted this in the Open API community forum, perhaps you should post in the Frameworx forum as well (https://engage.tmforum.org/communities/community-home/digestviewer?communitykey=019f32c2-82b7-427f-8156-f9262fe138fe&tab=digestviewer).
In any case I also do not recall a specific power-of-attorney entity in the SID, and certainly there is not one in the Open API model.
One could perhaps argue that a POA is a Document, for which there is a model in the Open API (but not in the SID, which currently has only Attachment).  The question arises as to whether there is sufficient semantic behavior for a POA that warrants it being modeled separately.
But the SID leaders @Michel Besson and @Cecile Ludwichowski might be able to give more clarity on the SID aspects.​​

------------------------------
Jonathan Goldberg
Amdocs Management Limited

Original Message:
Sent: Nov 29, 2018 04:23
From: Vadim Nechaev
Subject: Power of attorney

Dear Colleagues,
may be you can help me with the following question.

Our customer just asked me to process (GET/PUT/PATCH/DELETE) "Power of Attorney" (POA) documents.

This POA entity is associated with given agreement (one agreement may have many specific POAs - each POA for specific action (create a bill, ask a balance, add a new service, etc) and for specific person). POA entity authorizes the person (to make certain action) on behalf of the agreement signer.

POA has an issue date, validity period (from - to), "issued to"  person, "issued by" person.

Unfortunately, i haven't find a "Power of Attorney" entity in the SID model.

1) May be i missed it and this enity exists somewhere?:)
2) My suggestion is to create this entity as a child from Agreement entity and store POAs linked with agreement in the associatedAgreement field of Agreement entity.
The external system can inspect the "type" field to differ between "simple" Agreement and POA.


Any suggestions?

Big thanks in advance!



------------------------------
Vadim Nechaev
Senior systems architect
MTS Group HQ
------------------------------

Hi Vadim,

I agree with you and Jonathan: a POA is a special kind of Agreement, and as such it is certainly materialised in a Document.
The thing is that "Document" is not (yet) present in the SID. The SID has the concept of Attachment and we thought about adding "Document"... as soon as we have time!

Michel

------------------------------
Michel Besson , PhD
Lead Architect
TM Forum
------------------------------

Original Message:
Sent: Dec 03, 2018 06:26
From: Vadim Nechaev
Subject: Power of attorney

Hi Jonathan

Thank you very much for your quick reply (absence of POA - it was specially important for us), clarifications and detailed instructions! I noted your hint about SID Model/Open API Model - i will try to dig more information about difference between these models.


------------------------------
Vadim Nechaev
Senior systems architect
MTS Group HQ

Original Message:
Sent: Dec 02, 2018 01:52
From: Jonathan Goldberg
Subject: Power of attorney

Hi Vadim
You posted this in the Open API community forum, perhaps you should post in the Frameworx forum as well (https://engage.tmforum.org/communities/community-home/digestviewer?communitykey=019f32c2-82b7-427f-8156-f9262fe138fe&tab=digestviewer).
In any case I also do not recall a specific power-of-attorney entity in the SID, and certainly there is not one in the Open API model.
One could perhaps argue that a POA is a Document, for which there is a model in the Open API (but not in the SID, which currently has only Attachment).  The question arises as to whether there is sufficient semantic behavior for a POA that warrants it being modeled separately.
But the SID leaders @Michel Besson and @Cecile Ludwichowski might be able to give more clarity on the SID aspects.​​

------------------------------
Jonathan Goldberg
Amdocs Management Limited

Original Message:
Sent: Nov 29, 2018 04:23
From: Vadim Nechaev
Subject: Power of attorney

Dear Colleagues,
may be you can help me with the following question.

Our customer just asked me to process (GET/PUT/PATCH/DELETE) "Power of Attorney" (POA) documents.

This POA entity is associated with given agreement (one agreement may have many specific POAs - each POA for specific action (create a bill, ask a balance, add a new service, etc) and for specific person). POA entity authorizes the person (to make certain action) on behalf of the agreement signer.

POA has an issue date, validity period (from - to), "issued to"  person, "issued by" person.

Unfortunately, i haven't find a "Power of Attorney" entity in the SID model.

1) May be i missed it and this enity exists somewhere?:)
2) My suggestion is to create this entity as a child from Agreement entity and store POAs linked with agreement in the associatedAgreement field of Agreement entity.
The external system can inspect the "type" field to differ between "simple" Agreement and POA.


Any suggestions?

Big thanks in advance!



------------------------------
Vadim Nechaev
Senior systems architect
MTS Group HQ
------------------------------

Hi Michel, 
Thank you for your thoughts and clarifications: we will be waiting for added "Document" entity in SID:)  

 

------------------------------
Vadim Nechaev
Senior systems architect
MTS Group HQ
------------------------------

Original Message:
Sent: Dec 03, 2018 12:20
From: Michel Besson
Subject: Power of attorney

Hi Vadim,

I agree with you and Jonathan: a POA is a special kind of Agreement, and as such it is certainly materialised in a Document.
The thing is that "Document" is not (yet) present in the SID. The SID has the concept of Attachment and we thought about adding "Document"... as soon as we have time!

Michel

------------------------------
Michel Besson , PhD
Lead Architect
TM Forum

Original Message:
Sent: Dec 03, 2018 06:26
From: Vadim Nechaev
Subject: Power of attorney

Hi Jonathan

Thank you very much for your quick reply (absence of POA - it was specially important for us), clarifications and detailed instructions! I noted your hint about SID Model/Open API Model - i will try to dig more information about difference between these models.


------------------------------
Vadim Nechaev
Senior systems architect
MTS Group HQ

Original Message:
Sent: Dec 02, 2018 01:52
From: Jonathan Goldberg
Subject: Power of attorney

Hi Vadim
You posted this in the Open API community forum, perhaps you should post in the Frameworx forum as well (https://engage.tmforum.org/communities/community-home/digestviewer?communitykey=019f32c2-82b7-427f-8156-f9262fe138fe&tab=digestviewer).
In any case I also do not recall a specific power-of-attorney entity in the SID, and certainly there is not one in the Open API model.
One could perhaps argue that a POA is a Document, for which there is a model in the Open API (but not in the SID, which currently has only Attachment).  The question arises as to whether there is sufficient semantic behavior for a POA that warrants it being modeled separately.
But the SID leaders @Michel Besson and @Cecile Ludwichowski might be able to give more clarity on the SID aspects.​​

------------------------------
Jonathan Goldberg
Amdocs Management Limited

Original Message:
Sent: Nov 29, 2018 04:23
From: Vadim Nechaev
Subject: Power of attorney

Dear Colleagues,
may be you can help me with the following question.

Our customer just asked me to process (GET/PUT/PATCH/DELETE) "Power of Attorney" (POA) documents.

This POA entity is associated with given agreement (one agreement may have many specific POAs - each POA for specific action (create a bill, ask a balance, add a new service, etc) and for specific person). POA entity authorizes the person (to make certain action) on behalf of the agreement signer.

POA has an issue date, validity period (from - to), "issued to"  person, "issued by" person.

Unfortunately, i haven't find a "Power of Attorney" entity in the SID model.

1) May be i missed it and this enity exists somewhere?:)
2) My suggestion is to create this entity as a child from Agreement entity and store POAs linked with agreement in the associatedAgreement field of Agreement entity.
The external system can inspect the "type" field to differ between "simple" Agreement and POA.


Any suggestions?

Big thanks in advance!



------------------------------
Vadim Nechaev
Senior systems architect
MTS Group HQ
------------------------------

Howdy,  Vadim and all. As Michel and you mentioned a POA is a special type of agreement. There is an Agreement ABE currently in the SID Engaged Party domain. You may want to take a look at that. There is also a BusinessInteractionType entity related to BusinessInteraction, from which Agreement inherits that could be used to indicate that the agreement is a POA.

------------------------------
John Reilly
John P. Reilly Sole Trader
------------------------------

Original Message:
Sent: Dec 04, 2018 04:15
From: Vadim Nechaev
Subject: Power of attorney

Hi Michel,
Thank you for your thoughts and clarifications: we will be waiting for added "Document" entity in SID:)  

 

------------------------------
Vadim Nechaev
Senior systems architect
MTS Group HQ

Original Message:
Sent: Dec 03, 2018 12:20
From: Michel Besson
Subject: Power of attorney

Hi Vadim,

I agree with you and Jonathan: a POA is a special kind of Agreement, and as such it is certainly materialised in a Document.
The thing is that "Document" is not (yet) present in the SID. The SID has the concept of Attachment and we thought about adding "Document"... as soon as we have time!

Michel

------------------------------
Michel Besson , PhD
Lead Architect
TM Forum

Original Message:
Sent: Dec 03, 2018 06:26
From: Vadim Nechaev
Subject: Power of attorney

Hi Jonathan

Thank you very much for your quick reply (absence of POA - it was specially important for us), clarifications and detailed instructions! I noted your hint about SID Model/Open API Model - i will try to dig more information about difference between these models.


------------------------------
Vadim Nechaev
Senior systems architect
MTS Group HQ

Original Message:
Sent: Dec 02, 2018 01:52
From: Jonathan Goldberg
Subject: Power of attorney

Hi Vadim
You posted this in the Open API community forum, perhaps you should post in the Frameworx forum as well (https://engage.tmforum.org/communities/community-home/digestviewer?communitykey=019f32c2-82b7-427f-8156-f9262fe138fe&tab=digestviewer).
In any case I also do not recall a specific power-of-attorney entity in the SID, and certainly there is not one in the Open API model.
One could perhaps argue that a POA is a Document, for which there is a model in the Open API (but not in the SID, which currently has only Attachment).  The question arises as to whether there is sufficient semantic behavior for a POA that warrants it being modeled separately.
But the SID leaders @Michel Besson and @Cecile Ludwichowski might be able to give more clarity on the SID aspects.​​

------------------------------
Jonathan Goldberg
Amdocs Management Limited

Original Message:
Sent: Nov 29, 2018 04:23
From: Vadim Nechaev
Subject: Power of attorney

Dear Colleagues,
may be you can help me with the following question.

Our customer just asked me to process (GET/PUT/PATCH/DELETE) "Power of Attorney" (POA) documents.

This POA entity is associated with given agreement (one agreement may have many specific POAs - each POA for specific action (create a bill, ask a balance, add a new service, etc) and for specific person). POA entity authorizes the person (to make certain action) on behalf of the agreement signer.

POA has an issue date, validity period (from - to), "issued to"  person, "issued by" person.

Unfortunately, i haven't find a "Power of Attorney" entity in the SID model.

1) May be i missed it and this enity exists somewhere?:)
2) My suggestion is to create this entity as a child from Agreement entity and store POAs linked with agreement in the associatedAgreement field of Agreement entity.
The external system can inspect the "type" field to differ between "simple" Agreement and POA.


Any suggestions?

Big thanks in advance!



------------------------------
Vadim Nechaev
Senior systems architect
MTS Group HQ
------------------------------