Markdown can be used efficiently in many places…
For example we can embed little wiki-like features in traditional RDBMS based application:
we can have an ordinary table in which we have text column we can have CommonMark
text which can be formatted. But it is only good for formatting
@Jonas: in an R&D project we implemented a framework solution in which in an ordinary column of an ordinary RDBMS text column (i.e.: nvarchar data type in SQL Server) we could have link
to other instance of an ordinary table (which must have a PrimaryKey, or even Unique Key).
Let’s suppose we have a Master Data table called “Product”, which contains instances of products identified by an Columns which contains UniqueItemId string (e.g.: 1P4L-0014).
We can have another ordinary table called “A”, which contains an ordinary text column called
e.g.: “X” from which we can refer to this instance with:
[[#Product:#1P4L-0014]]
Customizing the Markdown parser with this relation we have established a “soft” “foreign”
key between A.X -> Product.
This relationship is a many - to -many relationship, because in a markdown column we can have
more links to another instances to Products. (And from another instance of “A” table in the “X” column we can refer to the same “1P4L-0014” product.)
And because we had a meta-repository describing that e.g. from the “A” table “X” columns we
can have a relation to Product, we could have a specific meaning for that relation. Similarly
to the RDBMS standard Foreign Key has a specific “Type” for a relation.