Closed kchason closed 1 year ago
Thank you, @kchason !
I looked at how we handled the vote scheduling for MIME type expansion (Change Proposal 104, linked off of the UCO 0.9.0 release notes). We did not fast-track that vote.
This hits some of the same potential complexities for interpretation, so we will hold a Requirements Review vote on this one.
Background
Currently, the property
observable:IMEI
in theobservable:MobileDeviceFacet
has a max cardinality of 1. This causes issues with devices that contain multiple SIM ports, as each SIM port has its own IMEI.In a direct and practical example, a commercial forensics tool (appropriately) identified two IMEIs off the sample mobile device and there's not currently a way to represent this without duplicating a
observable:MobileDeviceFacet
and associating it with the sameobservable:Device
.Requirements
Requirement 1
Remove the
sh:maxCount
from theobservable:IMEI
property of theobservable:MobileDeviceFacet
.Risk / Benefit analysis
Benefits
It allows devices that contain multiple SIM cards to be properly represented.
Risks
There are no known risks to existing adopters since it's loosening restrictions.
Competencies demonstrated
Competency 1
Competency Question 1.1
Allow representation of a device with multiple IMEIs.
Result 1.1
Solution suggestion
Coordination
develop
for the next releasedevelop
state with backwards-compatible implementation merged intodevelop-2.0.0
develop-2.0.0
(N/A)