profile ids should be idempotent
As of now, parameter values for (all) profiles are stored in the parameter object itself.
When loading a skill from memory or importing it through the frontend, the profiles need to exist in order to be able to convert the profile values. Profiles are identified by id here.
What should change:
- profile ids should be created deterministicly (how? what should be used to seed the UUID?)
- the name of a profile must be unique, atleast within a certain scope (same parent profile)
- profiles should be loaded from memory before loading the skills
- the user should be able to export / import profiles in the frontend (can this be combined with the export/import of a skill?)
Edited by Julian Tusch