improve addressing to include recipients

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major
    • Component/s: None
    • None
    • Hide

      We suggest to add the concept of recipients and devices to CAP.
      Specifically, the <addresses> element could be complemented with another element called <recipients>, as in the following example:

      <recipients>
      <recipient id=”string”>
      <displayName>string</displayName >
      <pin>string</pin>
      <locale>string</locale>
      <devices>
      <device id=”variant” type="string">
      <address>string</address>
      </device>
      …
      </devices>
      <overrideDeviceOrders>
      <deviceOrder deviceID=”string”>integer</deviceOrder>
      …
      </overrideDeviceOrders>
      </recipient>
      …
      </recipients>

      Show
      We suggest to add the concept of recipients and devices to CAP. Specifically, the <addresses> element could be complemented with another element called <recipients>, as in the following example: <recipients> <recipient id=”string”> <displayName>string</displayName > <pin>string</pin> <locale>string</locale> <devices> <device id=”variant” type="string"> <address>string</address> </device> … </devices> <overrideDeviceOrders> <deviceOrder deviceID=”string”>integer</deviceOrder> … </overrideDeviceOrders> </recipient> … </recipients>
    • Hide

      Use CIQ xPIL in EDXL wrapper

      Show
      Use CIQ xPIL in EDXL wrapper

      Sometimes, addressing may require more information that can be efficiently provided by just a single element (currently <addresses>).
      For example a message may target multiple recipients with multiple devices.
      This can become hard to manage if not organized in a clean data structure.

            Assignee:
            Unassigned
            Reporter:
            Tomer Petel (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: