OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ubl message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


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


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

Ken Holman edited comment on UBL-50 at 10/28/16 9:11 PM:
---------------------------------------------------------

Roberto, I'm looking into the details of the new DigitalAgreement document and I wonder if it makes sense to consider changing:

  SenderParty   1
  ReceiverParty   1..n

... to be:

  ParticipantParty   1..n

I think it is important for this document that it be bi-lateral/multi-lateral where all participants have the same weight in the agreement.  Personally, I don't think there should be a sender and receiver ... all parties are both sender and receiver to/from all other parties.

As discussed offline, participants can use the UBL Signature Extension in order to co-sign the document, or less formally the Signature ABIE.

I tweaked the description and so the schema documentation instance is updated with:

  <schema>
    <name>Digital Agreement</name>
    <description>A document used to support business parties agreeing on a set of digital processes, terms and conditions to ensure interoperability.</description>
    <processes>
      <process>Business Directory</process>
    </processes>
    <submitterRole>Agreement Participant</submitterRole>
    <receiverRole>Agreement Participant</receiverRole>
    <examples/>
  </schema>




was (Author: gkholman):
Roberto, I'm looking into the details of the new DigitalAgreement document and I wonder if it makes sense to consider changing:

  SenderParty   1
  ReceiverParty   1..n

... to be:

  ParticipantParty   1..n

I think it is important for this document that it be bi-lateral/multi-lateral where all participants have the same weight in the agreement.  Personally, I don't think there should be a sender and receiver ... all parties are both sender and receiver to/from all other parties.

As discussed offline, participants can use the UBL Signature Extension in order to co-sign the document, or less formally the Signature ABIE.



> 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: Ken Holman
>            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)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]