> >1. I think node_id rather than "meaning" for the name of this data would > > be clearer. > > I suspect we will make this change - most people prefer it
I propose to delete all "name", "meaning", "id" or similar fields from all archetypes. The only way an archetype should be identifiable is through its file name, which should be unique and in English. This also permits to use a URL for archetype identification. Philosophical Background: - a knowledge model (concept) knows about its parts - the parts are identified by the whole over a unique name - a part model itself does not know what name it carries in a possible surrounding "whole" concept that it is part of Example: - the concept of a person can be used as part by different whole concepts like an address-, EHR- or other administrative applications - these whole concepts can give a person very different names/ IDs - it is impossible to guess all possible uses of the person concept - therefore it does not make sense to store all possible names within a concept (knowledge template/ archetype) In short, the file name suffices to identify archetypes. Whole (compound) concepts use additional names to identify their parts. Christian - If you have any questions about using this list, please send a message to d.lloyd at openehr.org
