Skip to content
Snippets Groups Projects

IDM.TSA.00059 Content Access

    • Closed Issue created by Kalin Canov @kalin.canov

    The cached content MUST be accessible over a key (e.g., a DID), a namespace and an array of scopes, which results in an array of JSON documents. For instance, the access to the cache can be the following:

    Key: DID:sov:2358585

    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

    1. Result of a flat JSON file to an DID, namespace and scopes
    2. Duplicate Handling during the flattening of multiple documents
    Edited

    Designs

      Child items ...

      Activity

      Please register or sign in to reply