@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/dm-logical-integrity/C3> a edu:Question ;
    rdfs:label "C3 (2 points)"@en ;
    dcterms:license <https://creativecommons.org/licenses/by/4.0/> ;
    owl:sameAs <https://bitbucket.org/reffa/ontology/id/task/dm-logical-integrity/C3> ;
    schema:hasPart <https://knobit.org/id/register/data-modelling#I-519> ;
    schema:identifier "C3" ;
    schema:position 3 ;
    schema:text "The v0.4 split of Card Issue into Card Account Role (card account, role) and Party Card Role (person, role), joined back on Card Role Code, is lossy: Card Role Code is a key of neither part, so two card accounts each with an additional card holder join back into four holdings. 1 for reporting it as a lossy decomposition with the shared non-key attribute named (an example spurious row, or the four-from-two arithmetic, is enough); 1 for the fix: the issue fact is kept whole, on Card (card number -> holder, role) or on a single Card Issue entity, and the two fragments are removed."@en .

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

<https://knobit.org/id/register/data-modelling#I-519> rdfs:label "dm-logical-integrity C3: lossy split of card issue on the role code"@en .

