Re: [ubl-comment] Question about the BusinessCard object

["G. Ken Holman" <gkholman@CraneSoftwrights.com>]

Thank you, David, for this input to the UBL committee.

Your issue has been assigned to our colleague responsible for the 
business card to be addressed.  The issue is deferred to UBL 2.3 as 
we have closed new requirements for UBL 2.2 that is currently in progress.

The following ticket has been created to ensure your issue is 
properly addressed:

  https://issues.oasis-open.org/browse/UBL-141

Thank you, once again, for your assistance!  I wish you had found 
this comment list earlier in the process.

. . . . . . . Ken

At 2017-09-29 15:26 +0100, David Goodenough wrote:

> The business card (as in a piece of card printed with contact details)
>
> is generally a mass produced object, handed out to whoever wants one
>
> with no tailoring to the receiver. It is entirely one-sided, i.e. it
>
> only contains the details of one business/person/organization. Other
>
> sources of similar information would be the headed note paper and
>
> trade or postal directories.
>
>
>
> In order to start a UBL conversation it is necessary for the initiating
>
> party to obtain the Party details of the receiving party, but there seems
>
> to be no high level object that can be send just describing one Party.
>
> These might be printed as QR codes on real business cards or headed
>
> notepaper, or made available for download on a web site.
>
>
>
> Once you have the partner Party details then the DigitalCapabilities
>
> and DigitalAgreement conversation can happen, and these can also be
>
> used to update Party information should the need arise.
>
>
>
> 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?
>
>
>
> The UBL 2.2 Draft says:-
>
>
>
> >>>
>
> 2.3.8.2 Business Card
>
> The Business Card allows a standardized way of presenting digital trading
>
> capability information in a form that can be published or exchanged with
>
> trading partners.
>
>
>
> The data structures have been derived from the work of ebXML CPPP, OpenPEPPOL
>
> and other directory services initiatives.
>
> >>>
>
>
>
> It seems to me that is fails on two counts given this definition, firstly
>
> the lack of DigitalCollaboration object which would enable the presentation
>
> of digital trading capabilities, and secondly that it can not be published
>
> to the world, it can only be exchanged with a trading partner, which should
>
> not be necessary as if they are already UBL trading partners both sides must
>
> already have the Party details for the other and the BusinessCard object
>
> makes no provision for update, DigitalCapabilities/DigitalAgreement does.
>
>
>
> Or to put it another way, what is the high level object that is
>
> used by a Party to broadcast connection information so that others
>
> may request communications with it? I am rather hoping that this
>
> is not a piece of paper!
>
>
>
> David


--
Contact info, blog, articles, etc. http://www.CraneSoftwrights.com/o/ |
Check our site for free XML, XSLT, XSL-FO and UBL developer resources |
Streaming hands-on XSLT/XPath 2 training class @ US$45 (5 hours free) |