[OASIS Issue Tracker] (EMERGENCY-39) improve addressing to include recipients

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/EMERGENCY-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomer Petel updated EMERGENCY-39:
---------------------------------

    Proposal: 
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>



  was:
We suggest to add the concept of recipients and devices, in the addressing element, 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>




> improve addressing to include recipients
> ----------------------------------------
>
>                 Key: EMERGENCY-39
>                 URL: https://issues.oasis-open.org/browse/EMERGENCY-39
>             Project: OASIS Emergency Management TC
>          Issue Type: Improvement
>            Reporter: Tomer Petel
>
> Addressing may require more information that can be efficiently provided by just a single element. 
> For example a message may target multiple recipients with multiple devices. 
> This can get very complex if not organized in a clean data structure.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)