[OASIS Issue Tracker] (UBL-50) Can we use the DigitalCapability document as TPA ?

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/UBL-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63887#comment-63887 ] 

Roberto Cisternino commented on UBL-50:
---------------------------------------

The DigitalCapability describes both sending and receival capabilities, so if I describe only the subset of my capabilities that are matching my business partner I will be close to a TPA.
Anyway the ABIE is named DigitalCapabilities so to avoid semantic violations its structure should be reused into an additional ABIE named DigitalContract.
So probably a new document named DigitalContract or DigitalAgreement will be the best to describe the DigitalProcess/s the same way DigitalCollaboration does for a single party.

This could be the initial version for such a TPA...
...
MultiLateralAgreementIndicator (0..1)
SendingParty  (1..1)
ReceivingParty (1..n)   for multi-lateral agreeemnts if it is necessary to provide all participants in the contract.
AgreementTerms (0..n)
DigitalProcess (1..n)   This comes from the DigitalCollaboration.

I am reviewing EESPA MIA 3.0 (Model Interoperability Agreement for the Transmission and Processing of Electronic Invoices and other  Business Documents) so I will further comment this issue later.
 

> Can we use the DigitalCapability document as TPA ?
> --------------------------------------------------
>
>                 Key: UBL-50
>                 URL: https://issues.oasis-open.org/browse/UBL-50
>             Project: OASIS Universal Business Language (UBL) TC
>          Issue Type: Improvement
>          Components: Documents and business objects
>            Reporter: Roberto Cisternino
>            Assignee: Roberto Cisternino
>            Priority: Minor
>              Labels: DigitalCapability, TPA
>
> I found the DigitalCapability document is quite close to a TPA (Trading Partner Agreeement) or more precisely to an e-TPA.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)