The LV2 API, on its own, cannot be used to write plugin libraries where data is dynamically generated at runtime (e.g. API wrappers), since LV2 requires needed information to be provided in one or more static data (RDF) files. This API addresses this limitation by extending the LV2 API. To detect that a plugin library implements a dynamic manifest generator, the host checks its static manifest for a description like: <http://example.org/my-dynamic-manifest> a dman:DynManifest ; lv2:binary <mydynmanifest.so> . To load the data, the host loads the library (e.g. mydynmanifest.so) as usual and fetches the dynamic Turtle data from it using this API. The host is allowed to request regeneration of the dynamic manifest multiple times, and the plugin library is expected to provide updated data if/when possible. All data and references provided via this API before the last regeneration of the dynamic manifest is to be considered invalid by the host, including plugin descriptors whose URIs were discovered using this API. Accessing Data Whenever a host wants to access data using this API, it could: Call lv2_dyn_manifest_open(). Create a FILE for functions to write data to (e.g. using tmpfile()). Get a list of exposed subject URIs using lv2_dyn_manifest_get_subjects(). Call lv2_dyn_manifest_get_data() for each URI of interest to get the data related to that URI (which can be written to any FILE). Call lv2_dyn_manifest_close(). Parse the content of the FILE(s). Free/delete/unlink the FILE(s). Each call to the above mentioned dynamic manifest functions MUST write a complete, valid Turtle document (including all needed prefix definitions) to the output FILE. Each call to lv2_dyn_manifest_open() causes the (re)generation of the dynamic manifest data, and invalidates all data fetched before the call. In case the plugin library uses this same API to access other dynamic manifests, it MUST implement some mechanism to avoid potentially endless loops (such as A loads B, B loads A, etc.) and, in case such a loop is detected, the operation MUST fail. For this purpose, use of a static boolean flag is suggested. Threading Rules All of the functions defined by this specification belong to the Discovery class.
A DynManifest MUST have at least 1 lv2:binary, which MUST implement all the functions defined in dynmanifest.h.
The class which represents a dynamic manifest generator. There MUST NOT be any instances of dman:DynManifest in the generated manifest. All relative URIs in the generated data MUST be relative to the base path that would be used to parse a normal LV2 manifest (the bundle path).