Writing Mapping Specifications and Configurations for Dynamic Evidence

Dynamic evidence by it's nature is not modeled. There is single entity (or a set of entities) that contain data for all dynamic evidence types. A Dynamic Evidence Type will have one or more Evidence Type Versions over its lifetime. At any point in time, only one Evidence Type Version will be effective. All metadata elements (Attributes, Relationships, etc.) will be defined at the Evidence type Version level. So, the developer is responsible for providing the right mapping specification and configurations for the currently effective evidence type version.