On 22-10-14 13:10, Ian McNicoll wrote: > In practice this means that if I create a .opt , I can upload this to > one of these systems and it will be ready to use, with no need to > upload or manage the individual archetypes.
This is in fact an interesting thought. It could mean the end of archetypes. They only need to exist virtual, as inner-parts of templates. The system does not need to know them, as long as the template designer says they exist, somewhere, and on other existence, they are the same. It will be the templates which take over control, the decide what is right, they decide the ADL-paths, they decide the structure, and there is no way to validate if they are right. And the naming of archetypes in file-names. As archetypes do not need to be managed anymore, then they don't need to be in files. We had that discussion just a few weeks ago. Virtual Archetypes! Suppose you are wrong, archetypes are still needed on a system, suppose you fantasized this purpose, then the existence of the OPT-templates would be useless. Why need OPT-templates if all the information already is on a system. I therefor think you are right, I think this is really the purpose of the OPT-templates. I cannot think of another purpose. Quite some conclusion is that.
