Change cardinality of business parties in the UBL-BusinessCard and UBL-DigitalCapability

XMLWordPrintable

    • Hide

      Both the UBL-BusinessCard and UBL-DigitalCapability are required to change some party cardinality as follows:

      Now we have these main parties:
      SenderParty 1..1
      ReceiverParty 1..1
      BusinessParty 0..1
      The meaning was that the BusinessParty is only necessary if the SenderParty is a third-party (such as a service provider).

      I see now a different priority:
      SenderParty 0..1
      ReceiverParty 0..1
      BusinessParty 1..1
      Here the BusinessParty is always mandatory and both the sender or the recipient are information that can be optionally used or added in the future to send the document as a message.
      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.

      Show
      Both the UBL-BusinessCard and UBL-DigitalCapability are required to change some party cardinality as follows: Now we have these main parties: SenderParty 1..1 ReceiverParty 1..1 BusinessParty 0..1 The meaning was that the BusinessParty is only necessary if the SenderParty is a third-party (such as a service provider). I see now a different priority: SenderParty 0..1 ReceiverParty 0..1 BusinessParty 1..1 Here the BusinessParty is always mandatory and both the sender or the recipient are information that can be optionally used or added in the future to send the document as a message. 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.

      On the ubl-comment list an implementer has noted that the 1..1 cardinality of the SenderParty and ReceiverParty will not allow the use of the UBL-BusinessCard and UBL-DigitalCapability for simple storage of party's info and digital capabilities.
      Sender and Receiver parties need to be filled at a later stage for exchanging these particular documents.

            Assignee:
            Ken Holman
            Reporter:
            Roberto Cisternino (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: