[IOTDM-71] Compliance - IoTDM is not doing expected check while configuring "circRegion:accr" for ACP Created: 07/Mar/17 Updated: 19/Oct/17 |
|
| Status: | Open |
| Project: | iotdm |
| Component/s: | General |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Anil Pandey | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 7911 |
| Description |
|
Current Behavior - IoTDM is allowing me to set the ACP having (circRegion:accr) with only one element present. See following o/p - {"m2m:acp":{ Expected behavior - As per spec TS-004 Type Definition of m2m:locationRegion Note : The values represent latitude (/-90 degrees), longitude (/-180 degrees), and radius (metres) As circRegion is defined list of 3 elements, We should change current IoTDM behavior and impose restriction to set 3 elements in the list. |