We are trying to think about what to call 'branches' in TerminusDB and would appreciate your input. The survey is a short context-building intro and a single question.
In the git way of thinking, branching is where a particular versioned data product is taken as the starting point for a new development. For example, one may create a branch based off the default ‘main’ branch called ‘experimental’, to try out some experimental extensions to a data product without polluting the main data.
However, branches, as implemented in TerminusDB, are far more general than that. There is no need at all for branches in a data product to have some common starting point. Effectively, each branch is its own independent versioned graph.
The question is what to call these versioned graphs? What will have sufficient descriptive power and capture the imagination? The advantage to the git terminology is that it's all a bit complicated so at least if folks already share those concepts it's easier, but then again too much existing context can be difficult to overcome. Cache invalidation can't hold a candle to naming things
https://sb4cbw5ek2c.typeform.com/NameTerminusDB
