The Java metadata binding is described in the project overview as a thin general purpose Java binding. It is the bridge between the Java tools in m3dditieZ and the metadata that the tagger produced.
What thin means here
A binding is thin when it maps an existing interface into Java without adding a second model on top of it. The value of that approach is that a Java tool can use the same metadata that the other tools read, and that a change in the source data does not require a matching change in a large generated layer.
Role in the tool chain
- It feeds the Java side of the library tools.
- It keeps the metadata model shared with the other components.
- It is a library rather than an application, so it does not have a user interface.
Recorded scope
The project overview links this page, but its body was not preserved. The description above keeps the recorded phrase, a thin general purpose Java binding, and does not name a service or protocol that the archive did not record.
To see how the metadata is consumed, read library fundamentals and the project overview.