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: Re: [ubl] [OASIS Issue Tracker] (UBL-145) Add a new DigitalAgreementID BIE to the root of any business document to directly reference an overall Digital Agreement

The reason for this request is in connection with the new UBL-DigitalAgreement document that is used to create TPAs (trading partner agreements) in a digital way and thus to facilitate the automatic configuration of edi / b2b systems.

At this stage OpenPEPPOL uses primarly the envelope to specify which ProfileID and CustomizationID are in use within a given transaction, but UBL could be used in peer-to-peer too and it is in fact independent from a specific envelope.

It should be noted that the ProfileID and CustomizationID are possibly just a piece of an overall agreement in place. Just like in OpenPEPPOL these are not sufficient to identify the real TPA agreement.

This DigitalAgreementID is a sort of shortcut to say which TPA is currently driving the exchange of a document instance.

For OpenPEPPOL it could be something like...  I am using the Spring Release 2017 openPEPPOL-VA-V3.4.0 (the currently mandatory release is such an agreement)

By referencing a specific instance of an UBL-DigitalAgreement two companies or an user group wil precisely identify the exchange context.

Hope this clarifies better the requirement and what is going to solve.


Il 25/10/2017 16:18, OASIS Issues Tracker ha scritto:
     [ https://issues.oasis-open.org/browse/UBL-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=67927#comment-67927 ]

Erlend Klakegg Bergheim commented on UBL-145:

The OpenPEPPOL TIA is an agreement on transport level. Referencing the OpenPEPPOL TIA in a business level document would give no value.

I think we need a more generic description of this request to be able to add such an identifier in any document types.

Add a new DigitalAgreementID BIE to the root of any business document to directly reference an overall Digital Agreement

                 Key: UBL-145
                 URL: https://issues.oasis-open.org/browse/UBL-145
             Project: OASIS Universal Business Language (UBL) TC
          Issue Type: Improvement
          Components: Documents and business objects
            Reporter: Roberto Cisternino
            Assignee: Ken Holman
            Priority: Minor

Any UBL document has a ProfileID and CustomizationID in order to associate a precise profile and customization.
Different profiles and document customizations could be part of an overall Digital Agreement (e.g. an OpenPEPPOL agreement).
Now that UBL has a DigitalAgreement document it could be nice to have the possibility to directly reference a digital e-business agreement from each UBL document instance.

This message was sent by Atlassian JIRA

To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:

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