[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
Platform: 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":{
"pv":{"acr":[{"acor" : ["admin"],"acop":63,"acco":[{"aclr":{"accr":["1.0"],"accc":["US","NL"]}}]}]},"pvs":{"acr":[{"acor" : ["admin"],"acop":63,"acco":[{"aclr":{"accc":["IN","NL"]}}]}]}
}
}

Expected behavior - As per spec TS-004

Type Definition of m2m:locationRegion
================================================================
Element Path Element Data Type Multiplicity
circRegion List of 3 xs:float 0..1
================================================================

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.


Generated at Wed Feb 07 20:05:06 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.