Content access with multiple scopes
Current implementation supports a single Scope only. Support of multiple scopes should be implemented.
Namespace: Login
Scopes: administration, read, visitor
Result: {“name”:”userX”,”iss”:did:sov:33333}, {“membership”:”company”,”iss”:did:sov:1111}
To optimize the access, it MAY be optimized by flatten the access pattern like: Key: DID:sov:2358585 Namespace: Login:administration
Independent from the format, the result for the accessor MUST be a flatten JSON structure. In the flattening step, it SHOULD namespace duplicated claims if they are semantically different (e.g., using JSON-LD context). If two JSON structures bring a duplicated claim which is semantically the same claim (say two JSON structures bring Name and Surname, but the values are different) then a policy shall decide whether to: take one of them or discard all of them.
Constraints
- Supported data format of the cache technology
- Policy Decision Engine
Acceptance Criteria
- Result of a flat JSON file to an DID, namespace and scopes
- Duplicate Handling during the flattening of multiple documents