[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=63885#comment-63885 ] 

Tim McGrath commented on UBL-50:
--------------------------------

I originally thought the DigitalCapability was a statement on one organisation's ability to process digital documents.  That is the same sort of thing as an ebXML CPPP (collaboration profile). It says "I am capable of digitally trading in these ways".
So the Sending and Receiving Party is "who I am as a Sender and who I am as a Receiver".
But I can see how this may be seen as a TPA (the same sort of thing as an ebXML CPPA (collaboration agreement).  In these cases the two DigitalCapabilities are matched up to create an agreement, "My sending ability matches your receiving ability".
So as it stands I am not sure the DigitalCapability is a TPA - it is only one side of it.  Certainly a DigitalCapability (from both parties) could be referenced in a TPA but that probably will have a more complex structure.
This does raise a good point about TPAs. I suspect the most important TPAs in future will be multi-lateral (such as used by PEPPOL and EESPA).
It may be worth reviewing their agreements to see how DigitalCapability could be used to specify their technical requirements.

> 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: Tim McGrath
>            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)