As a matter of modeling principle, should this spec provide guidance or even rules for how to deal with class hierarchies, e.g. do we want to keep the full tree and all of the ancestor classes in a profile, or materialize it (at least in part) to keep only leaf classes that are relevant to the use case?
Might be a modeling question entirely out of scope, but guidance may be useful and this could be a suiting place to provide it.
As a matter of modeling principle, should this spec provide guidance or even rules for how to deal with class hierarchies, e.g. do we want to keep the full tree and all of the ancestor classes in a profile, or materialize it (at least in part) to keep only leaf classes that are relevant to the use case?
Might be a modeling question entirely out of scope, but guidance may be useful and this could be a suiting place to provide it.