I2 (1.5 points)
https://knobit.org/id/task/dii-source-profiling-semantics/I2
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/dii-source-profiling-semantics/I2 |
| rdfs:label | I2 (1.5 points) en |
| schema:hasPart | dii-source-profiling-semantics I2: a canonical message limits the transformations |
| schema:hasPart | dii-source-profiling-semantics I2: production flows are monitored, retries do not replace it |
| schema:hasPart | dii-source-profiling-semantics I2: DII metrics beyond interface counts; lineage to metadata management |
| schema:identifier | I2 |
| schema:position | 4 |
| schema:text | Design note, design and operation statements, 0.5 each: marked incorrect with a correction that states the concept. (a) D4: a canonical card message limits the transformations - each producer and consumer maps once to the common format instead of one transformation per consumer pair. (b) D9: flows in production are monitored (failures, latency, volume or backlog, with alerts); automatic retries do not replace monitoring. (c) D11: metrics cover availability, volume, latency or business value, not only the count of interfaces moved; lineage is handed to metadata management, not left in job logs (either half of the correction earns the part, both are expected). en |