Meta Requirement
BEMIs should support users' learning by providing concise and audience-specific explanations of complex concepts.
01
Producer metadata and the represented concept document.
Concept identity
design-knowledge/bemi-marketplace-interfaces-mr2design-knowledge/bemi-marketplace-interfaces-mr2.mdBEMIs should support users' learning by providing concise and audience-specific explanations of complex concepts.
This meta-requirement is proposed by Developing Blockchain-enabled Marketplace Interfaces: A Design Science Research Study (Tobias Koelbel, Ahmed Zekri, Christof Weinhardt, 2023).
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: Design knowledge
Derived heading context: Addresses
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 · 5 directed relationships
05
The complete producer frontmatter, serialized without server paths or runtime data.
{
"type": "meta-requirement",
"title": "MR2 - Provide audience-specific documentation",
"description": "BEMIs should support users' learning by providing concise and audience-specific explanations of complex concepts.",
"resource": "https://aisel.aisnet.org/icis2023/blockchain/blockchain/1",
"source_paper": "Developing Blockchain-enabled Marketplace Interfaces: A Design Science Research Study",
"label": "MR2",
"tags": [
"bemi-marketplace-interfaces",
"meta-requirement",
"marketplace",
"user-interface",
"additive-manufacturing",
"hci"
]
}