A metadata aggregator will take metadata from various sources and also disseminate metadata to others. The aggregator uses an application profile to specify the metadata that it will ingest, which is a subset of a widely used specification. The aggregator requires a certain minimum of metadata in order to perform its functions, i.e. some of the metadata in the profile is mandatory; in addition to this there is metadata that is not mandatory but can be useful if present; beyond this there is metadata that is allowed by the base specification that is not part of the application profile but may be useful (or even necessary) to services to which the aggregator disseminates metadata. The aggregator requires that the language of the metadata is appropriate for its users.
Stakeholders
providers of metadata to the aggregator
the maintainers of the aggregator
downstream users of metadata disseminated by the aggregator
Requirements
The application profile must be able to distinguish between mandatory/required elements, preferred/desired elements and optional elements.
The application profile may include information about what happens to metadata that conforms to the base specification that is not in the application profile. Alternatively this may be a policy outside the scope of the application profile.
The application profile should be able to specify which languages are allowed or required for textual metadata (literals and labels)
Comments
An extension of the use case may involve an application profile that forbids some parts of the base spec, e.g. if the data involved did not conform to local laws / policy. This may be a factor with sensitive personal data.
Creator: Phil Barker
Problem statement
A metadata aggregator will take metadata from various sources and also disseminate metadata to others. The aggregator uses an application profile to specify the metadata that it will ingest, which is a subset of a widely used specification. The aggregator requires a certain minimum of metadata in order to perform its functions, i.e. some of the metadata in the profile is mandatory; in addition to this there is metadata that is not mandatory but can be useful if present; beyond this there is metadata that is allowed by the base specification that is not part of the application profile but may be useful (or even necessary) to services to which the aggregator disseminates metadata. The aggregator requires that the language of the metadata is appropriate for its users.
Stakeholders
providers of metadata to the aggregator the maintainers of the aggregator downstream users of metadata disseminated by the aggregator
Requirements
Comments
An extension of the use case may involve an application profile that forbids some parts of the base spec, e.g. if the data involved did not conform to local laws / policy. This may be a factor with sensitive personal data.