The standard in the previous form also contained base requirements. For v2+ a possible solution could be to seperate that, so that only technical requirements are still part of the base framework. Every other requirement is then extracted into a 'global core profile set'.
We do have a data type library that profiles the datatypes according to their most important usages. (Unfortunately, this currently only contains the US perspective. It would be good to add other, eg. the Asian use case for names.) Links will follow here:
In order to keep the details for a global core profile these are generated separately. (In the segment page you can also find an integrated view - just as you like to see it.) Links will follow here: