@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix edu: <https://knobit.org/def/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix schema: <https://schema.org/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

<https://knobit.org/id/task/dsec-access-design/I1> a edu:Question ;
    rdfs:label "I1 (1.5 points)"@en ;
    dcterms:license <https://creativecommons.org/licenses/by/4.0/> ;
    owl:sameAs <https://bitbucket.org/reffa/ontology/id/task/dsec-access-design/I1> ;
    schema:hasPart <https://knobit.org/id/register/data-security#SE-354>,
        <https://knobit.org/id/register/data-security#SE-355> ;
    schema:identifier "I1" ;
    schema:position 3 ;
    schema:text "(a) 1 point: hardship_note.note_text is restricted but has no column_access entry, which CS-02 requires: the answer reports it and adds an entry - clear only for the hardship specialists' role RL-013, no analyst or agency role clear or masked, the note kept out of arrears_mart, TR-001 and the agency portal. (b) 0.5: the notes record illness, disability and bereavement - health data, a GDPR Art. 9 special category - but CS-02's regulatory categories have none for it: the answer reports the gap in the standard (a category with its own handling rule) and sends it to the DPO or the CISO."@en .

edu:Question rdfs:label "Question"@en,
        "Küsimus"@et .

<https://knobit.org/id/register/data-security#SE-354> rdfs:label "dsec-access-design I1: hardship notes restricted with no access design"@en .

<https://knobit.org/id/register/data-security#SE-355> rdfs:label "dsec-access-design I1: the confidentiality standard has no special-category class"@en .