Describe processes as type transformations, with inference that supports subtypes and parametric polymorphism. Create and query corresponding transformation graphs.
Already hinted at in #89: I would like to rename the transformation-algebra library. Reasons:
It prevents confusion. We often talk about 'the transformation algebra' when we mean the CCT algebra or its implementation in the cct library. This transformation-algebra is really only a generic library underneath.
A different name emphasizes that it can be used in other contexts.
I'm currently writing a tutorial/workshop for the library, and "the transformation algebra library" has too many syllables for comfort. The name 'transformation algebra' algebra focuses only on the expressions, and not on the graphs, queries or type system.
Also, what does 'algebra' really mean?
It gets tedious to use from transformation_algebra import ... in Python or python -m transformation_algebra ... from the command line.
Better to change it now than to wait until it's more entrenched.
Already hinted at in #89: I would like to rename the
transformation-algebralibrary. Reasons:cctlibrary. Thistransformation-algebrais really only a generic library underneath.from transformation_algebra import ...in Python orpython -m transformation_algebra ...from the command line.Better to change it now than to wait until it's more entrenched.
metaflow, but that already exists: https://pypi.org/project/metaflow/.paraflowcould be an alternative?contrailis another contender (for 'concept transformation library', also evocative of a conceptual 'trail'), but that's a real word.transformatterwould work.