Reusable BKM

BKMs are defined as reusable assets of the DMN, since any decision needing that bit of decision logic can invoke it by mapping its inputs to the BKM parameters. The creator of the BKM does not need to know the names of the variables in the models that invoke it.
A library of BKMs should be available for the DMN modeler user.
I want to suggest the creation of a set of tools like the ones that we have for custom work item handlers in BPMN:
1. bkm file types can be created in decision central, the BKM will define its logic and be persited in the repositories like the attached example. More complex examples can be given as BKMs can have knowledge requirements, to other BKMs; but note that no information requirements can be attached to BKMs, so the BKM editor does not need inputs, decisions or knowledge services; only other BKMs and access to the BKM library.
2. BKMs in the dependencies and in the current kjar should be displayed in the BKM library (an organized toolbox like the one presented for custom work item handlers in BPMN).

ORGANIZATION
because BKMs list can grow with the project, may be the library can be part of the Included Models type instead and import them to the main DRD using some action button in the Included Model lists; and then, switch to the DRD and setup the BKM relationships and mappings.