Multi-Tree support?

_This is a topic originating from the HIM presentation by Ulf at the Porto AMM_

Ulf has proposed the HIM model to include multiple trees and services. How shall it continue.

Two parts:

**Tree (in general)**

- Ulf possibly put rules/tools in separate project
- Erik: In HIM file - do we want static data (what is catalog XXX) or also deployment information (which server provides data for model XXX)
- Erik: I can see 3 usecases
- Static model info, for example to generate dataclasses in some programming language. More as a recepie
- Client Deployment info - how can client access data
- Server deployment data - how shall server manage data
- Erik: The first use-case can likely be generic, the other might possibly be more use-case-specific
- Ulf: WAII import binary format,

Way forward:

- Ulf to take lead. Possibly create a PR to DEG repo in a markdown file so that it can be reviewed/discussed in group
- Ted: Wants to see some use cases
- Sebastian: Maybe first split tools from catalog

**Services**

Handled by #15