Next in thread → Next in month →

[OASIS Issue Tracker] (UBL-141) Reported: Business card receiver party and digital collaboration object

From
OASIS Issues Tracker <>
Date
2017-10-09T22:26:57+00:00
ID
Thread
[OASIS Issue Tracker] (UBL-141) Reported: Business card receiver party and digital collaboration object
[ https://issues.oasis-open.org/browse/UBL-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=67765#comment-67765 ] 

Roberto Cisternino commented on UBL-141:
----------------------------------------

The UBL BusinessCard is not directly related to digital collaborations.
The UBL DigitalCollaboration document covers this requirement and a full set of digital collaborations can be described inside the DigitalProcess information aggregate following the OASIS BPSS-like collaboration definition.

Process -> Collaborations -> Transactions

The UBL Business Card is not designed to fully instruct EDI / B2B systems.  It can be used to Exchange Party information along with identifiers, financial information and general business capabilities in textual form.

> Reported: Business card receiver party and digital collaboration object
> -----------------------------------------------------------------------
>
>                 Key: UBL-141
>                 URL: https://issues.oasis-open.org/browse/UBL-141
>             Project: OASIS Universal Business Language (UBL) TC
>          Issue Type: Bug
>          Components: Documents and business objects
>            Reporter: Ken Holman
>            Assignee: Roberto Cisternino
>            Priority: Minor
>
> Reported 2017-09-29:
> https://lists.oasis-open.org/archives/ubl-comment/201709/msg00018.html
> "So my question is why the BusinessCard has a mandatory ReceiverParty
> in it, and why it does not have a DigitalCollaboration object? I
> am here looking for a rational or definition objectives. It was
> presumably added for a good reason/purpose, is that documented anywhere?"
> (See original post for background detail to the question)



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
Next in thread → Next in month →