Chapter 3 of Library Technology Reports (vol. 57, no. 6), “Components,” explains that metadata application profiles (MAPs) have four components: the application, entities, properties, values. When an ...application requires a MAP, entities are the things described. Arguably the main purpose of a MAP is to identify properties describing entities. Properties have values also described by a MAP. MAP components are familiar to metadata professionals, but MAP contents have changed, largely due to the increasing adoption of linked-data practices.
Chapter 4 of Library Technology Reports (vol. 57, no. 6), “Sources,” explains that metadata application profile (MAP) creators gather MAP components from already existing sources. These sources ...include ontologies, schemas, vocabulary encoding schemes, and syntax encoding schemes, representing a shift in sources following the increasing adoption of linked-data practices.
In chapter 6 of Library Technology Reports (vol. 57, no. 6), “Examples,” five examples of metadata application profile (MAP) features demonstrate the following: a machine-readable MAP, two ...human-readable MAPs, a MAP embedded in a platform, and a domain model for an application. Descriptions that accord with an application profile created for describing application profile fragments accompany the examples.
