Design Requirement
A solution must comply with CMR regulations.
01
Producer metadata and the represented concept document.
Concept identity
design-knowledge/decentralized-procurement-logistics-dr4design-knowledge/decentralized-procurement-logistics-dr4.mdA solution must comply with CMR regulations.
This design requirement is proposed by Decentralized Procurement Mechanisms for Efficient Logistics Services Mapping - a Design Science Research Approach (Tiphaine Henry, Roman Beck, Nassim Laga, Walid Gaaloul, Shenle Pan, 2022).
02
Concepts connected by incoming or outgoing native Markdown links.
03
Directed links from Markdown. Heading context is displayed as derived metadata, not as a formal OKF predicate.
Derived heading context: Source paper
Derived heading context: Addresses
Derived heading context: Design knowledge
Derived heading context: Addressed by
04
One-hop by default, with an optional bounded two-hop view. Nodes are concept files and arrows are Markdown links.
3 of 3 concepts · 6 directed relationships
05
The complete producer frontmatter, serialized without server paths or runtime data.
{
"type": "design-requirement",
"title": "R4 - CMR regulations compliance",
"description": "A solution must comply with CMR regulations.",
"resource": "https://hdl.handle.net/10125/79952",
"source_paper": "Decentralized Procurement Mechanisms for Efficient Logistics Services Mapping - a Design Science Research Approach",
"label": "R4",
"tags": [
"decentralized-procurement-logistics",
"design-requirement",
"logistics",
"procurement",
"smart-contracts",
"supply-chain"
]
}