In discussion recently it was pointed out that there is still some hard coding in the endeme world or level 3. When you interpret(use) an endeme set you have hard coding. I don’t have a problem with some hard coding at the low end of level 3. As you move up through the levels the amount of hard coding should reduce. That is the hope and the theory. The theory is based on the idea that:
- graceful degradation for hard coded interpreters as an endeme set changes.
- meta information
- soft coded fields
- progressive softening of coding while moving upwards within sub-levels of This Stack.
But then how to add functionality in a way that is soft coded?
That is the rub.
Hard Coding Level 3 may be the first step in development
Hard coding endeme interpreters may be part of the process of development in level 3. Endemes can operate very well off of a framework which is above the level of object orientation but is written using object orientation. 95% of your code will be hard coded OO and 5% will be level 3 soft coded code. To increase the percentage of soft coded code at this level you will need to write lots of hard coded OO level interpreters and then start refactoring and generalizing to make your framework. So hard coding endeme interpreters is the first step in development.
Maybe there is a stack inside level 3:
knowledge representation graphs (ontololgies) | - node and edge definitions of functionality | node definitions for use by knowledge representation graphs | - node functionality definitions? | data semantics | - more endeme meta-information | - meta-information about meta-information? | endeme activated fields | - endeme meta-information | endeme activated lists | - soft coded endeme to endeme translators? | endemes - hard coded endeme interpreters