[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ubl-comment] Question about the BusinessCard object
Hello David,
I cutted out some parts for a more readable mail. Il 11/10/2017 20:46, David Goodenough ha scritto: Well, the DigitalCapability already includes the Sender Party information, same as in the BusinessCard. What I want to say is that the BusinessCard is not binded to the DigitalAgreement process, it is mainly used to share or update Party information and any change in the time, that's why we designed a message. At this point I think both the UBL-BusinessCard and UBL-DigitalCapability are required to changesome cardinality as follows: Now we have these main parties:
The actual form was forcing implementers to fill the recipient and sender in any case (e.g. with a place holder) if the document was not immediately intended to be exchanged using B2B. I see now a different priority:
This is facilitating the possibiity to publish (broadcast) a BusinessCard or a DigitalCapability on a web site or a public/private social or business directory. I am sorry I didn't get you perfectly when you said to add DigitalService... where ? Now DigitalService (a.k.a Business Transaction) is nested inside the Business process and its collaborations. This structured way of describing digital services that we want expose and/or consume is based on an OASIS specification for business processes (BPSS) and projects like PEPPOL will find this structure quite familiar. PEPPOL business profiles can be fully described using the UBL-DigitalCapability and trading party agreements can be built using the UBL-DigitalAgreement. The BusinessCard can be used as a generic way of introducing your company to others and is not specific for achieving a Digital Agreement with our partners. - I present my company with its trading capabilities for doing business (e.g. at a marketing level) - I update my partners with my new business address or contact info - so on... there are many uses for the Business Card. The main requirement was to have a way to transfer Party information separately from other specific business documents. The DigitalCapability is *specific* for publishing only "digital" trading capabilities and building digital agreements. It contains Party information too, but NOT full trading capabilities. A company could be able to receive electronic invoices and that's it... but their commercial capabilities could be many and detailed descriptions.... for that they will use a BusinessCard instead. PEPPOL uses the name BusinessCard for digital purposes, but this is a simplification they probably preferred to use. UBL TC seriously avoided to put all of these info inside the Party ABIE and we preferred to separate these documents for different purposes.
Versioning is accomplished using the upper information in the document root. No, the BusinessCard cannot contain DigitalService this is already partof the DigitalCapability document and also you need to tell if you are able to expose or consume a DigitalService that's why we use the DigitalCollaboration (here you can describe bot sending and/or receival capabilities). Yes the Digital Agreement can be used for peer-to-peer too. Please see the DigitalCapability and the DigitalAgreement more machine-2-machine documents for driving cyber-business not only e-business. The BusinessCard is mainly an e-Business document and used mostly for human-machine relationships. Do not see this as extreme, we have simply separated their roles. I will immediately suggest the revision of the cardinality for the above mentioned documents, I will also request a fix for the specification where we miss the description for the DigitalCapability document (even if it is mentioned in the digital agreeement graph). Further I will propose to include a graph for the BusinessCard too if possible. Cheers, Roberto Cisternino UBL ITLSC, chair |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]