C1 (2 points)
https://knobit.org/id/task/mm-metamodel/C1
Also as Turtle · JSON-LD · RDF/XML
| dcterms:license | https://creativecommons.org/licenses/by/4.0/ |
|---|---|
| owl:sameAs | https://bitbucket.org/reffa/ontology/id/task/mm-metamodel/C1 |
| rdfs:label | C1 (2 points) en |
| schema:hasPart | mm-metamodel C1a: business meaning moved off the column class to the term link |
| schema:hasPart | mm-metamodel C1b: column represents one term (N:1), per the 11179-3 data element |
| schema:identifier | C1 |
| schema:position | 1 |
| schema:text | Business meaning and the column, 1 each. (a) MC-005 Column carries `business_meaning`, a curated statement of what the column means to the business, although ML-001 already links each column to the business term that defines it: the attribute is dropped and the column's meaning is reached through ML-001 (MC-001), reported as business meaning stored on a technical class. MC-004 Table's `description` (what the table holds, its grain and how it is loaded, owned by the data owner) is technical documentation and stays: this part earns nothing while MC-005 keeps a business definition of its own (under any name), and dropping the table's description as well loses it. (b) ML-001 column represents term has cardinality N:M: it becomes N:1 - a column is a data element, which represents exactly one data element concept (its meaning) in one value domain (its representation), per ISO/IEC 11179-3; a column that seems to mean two things is raised for the glossary to resolve, not modelled as many-to-many. Changing the cardinality with no reason, or with a reason that does not say one column has one meaning, earns 0.5. en |