As we begin to discuss consensus semantics / start our semantic engineering journey as an ecosystem, we will most assuredly ‘get things wrong’.
As such, we should accept that we will ‘get things wrong’ now, and devise some plan for the ‘mass migration’ of Atoms / Triples’, for which we currently have no efficient solution.
For example → right now, the Portal uses a specific [has tag] Atom as the predicate for all of its tag/list functionality.
What if that [has tag] Atom is no longer viable, and but we want to preserve the relationships?
What is our approach?
Something on-chain? Something off-chain?
Some backwards-compatible versioning system?
Very curious to hear what folks think might be interesting solutions here, so that we can start to converge around something that generally feels good in most scenarios; if we can do this, then ‘getting things right’ from the beginning becomes far less important (though still important), and semantic engineering generally can become a much more fluid process.