MediaBeacon uses the Adobe XMP standard to store metadata.
How XMP Metadata Works
XMP metadata is written into the data of a file, making the metadata strongly-attached. This allows the metadata to travel with the file, instead of residing in an external source. This approach to metadata also allows XMP-aware applications to read and write metadata to that specific file, so that that all future users of the file can use this information.
From the user's perspective, metadata values are displayed in fields, which are collected together in schemas. In MediaBeacon, the interface that displays these data structures are called metaforms.
When XMP metadata is written to a file, each value is stored with the field and schema, so the information will always have context. An asset containing a metadata value is sometimes referred to as being tagged with that value.
Over the life of the XMP standard, various industry standard schemas have been developed, such as Dublin Core Properties or Adobe Photoshop Properties. Although there are standards that exist, one aspect of XMP is that the display of metadata is variable. A common practice is to label fields differently than their canonical field names. A good example is data structure behind the Dublin Core Properties "Keyword" field:
The above is an example of a XMP/XML expanded name consisting of a namespace URI (aka namespace name), and a local name.
- Namespace URI: "http://purl.org/dc/elements/1.1/" This value is used in MediaBeacon to define a schema, a collection of related fields. The schema name "Dublin Core Properties" is a label applied to make this information more human-readable.
- Local Name: "subject" This designates the field itself, "Keywords" is the display label.
MediaBeacon's metaforms can change the label (display names)l of schema or fields, but the data entered will remain unchanged.
The articles below will discuss different ways to view and edit metadata in MediaBeacon.
- [3D Viewer]
- [Clarifai AI]