"Baselining". The Baseline Protocoll as a design pattern - within the Unibright Framework.

In this video, Unibright's CTO and Baseline TSC member Stefan Schmidt explains:

- Why it is meaningful to define business processes on an abstract level, like with our Unibright Workflow Designer, and to be not only "blockchain agnostic" but also "design pattern agnostic".
- That enterprises may be cautious to use a public blockchain, because they do not want to give others any insights (even if they are pseudonymized) into their processes.
That a "private" chain does not solve all the concerns enterprises may have towards privacy, as a private chain still can give others insights that should not be made public.
- How integration changes (or doesn't change) in regards to Baseline as long as you have a low-coding integration component like the Unibright Connector which can connect to blockchains, off-chain-systems and APIs (like that one of Baseline).
- How important code generation (like with our Unibright Lifecycle Manager) becomes in the world of Baseline, because generated code becomes the "shared" and trusted codebook of all participants of a business process.
- How tokenization processes (like with out Freequity components) come into play, when blockchain is not "only" used as a middleware, but also as a token environment for tokens representing digital identities or even securities.

Check out the corresponding blog: https://medium.com/@UnibrightIO/baseline-repo-public-unibright-on-the-tsc-baselining-explained-84a3bc4c2e58

The Baseline Repo on GitHub:
https://github.com/ethereum-oasis/baseline

Documentation on Baseline Governance and the TSC:
https://docs.baseline-protocol.org/community/community-members

Check out a great baseline explainer FAQ by EY's Paul Brody: https://www.reddit.com/r/ethfinance/comments/fds4sy/a_sort_of_baseline_explainer_faq/