I1 (2 points)
https://knobit.org/id/task/dg-standards-procedures/I1
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/dg-standards-procedures/I1 |
| rdfs:label | I1 (2 points) en |
| schema:hasPart | dg-standards-procedures I1: ST-024 may is a permission, not a requirement |
| schema:hasPart | dg-standards-procedures I1: ST-025 can is a possibility, not a requirement |
| schema:hasPart | dg-standards-procedures I1: ST-021 permission beside a shall left alone |
| schema:hasPart | dg-standards-procedures I1: ST-026 verification a second person could carry out |
| schema:identifier | I1 |
| schema:position | 4 |
| schema:text | Requirement wording and verification, 0.5 each. (a) ST-024 says country codes 'may' be taken from ISO 3166-1: a permission, not a requirement; rewritten with shall (proposed, for RO-010 to confirm) or reported as not a requirement. (b) ST-025 says collateral 'can' be revalued every 12 months: a possibility, not a requirement; rewritten with shall (proposed, for RO-003 to confirm) or reported. (c) ST-021 is left alone: its 'may' (consent may be given in any channel) is a permission beside a shall requirement, which is correct; flagging or rewriting it loses this half point. (d) ST-026's verification 'Ongoing monitoring as appropriate' names no method, performer or frequency: it is replaced with one a second person could carry out (who, how and how often - for example monthly by the credit risk analyst from a default flag completeness query on the risk data mart). en |