JISC Metadata Application Profiles, Data Models andInteroperability
Pete Johnston, Eduserv Foundation & Rosemary Russell, UKOLN
The JISC Repositories & Preservation Programme has funded a number of projects towork on metadata application profiles for the description of a range of resources. Themetadata application profiles developed so far - the Scholarly Works ApplicationProfile (SWAP)
, the Images Application Profile (IAP)
,the Geospatial ApplicationProfile (GAP)
- are all Dublin Core Application Profiles, i.e. they are based explicitlyon the Dublin Core Abstract Model. The project currently working on the profile for Time-Based Media (TBMAP) is also operating on this basis.The SWAP, the IAP and the TBMAP each have as their focus the description of a particular class or genre of resources. The GAP differs slightly in that it is intended to be used in conjunction with other profiles; and it focuses on a specific set of characteristics which may be applied to resources of many different types, thedistinguishing characteristic being that they have some relationship with “place”.This note provides some issues for discussion around the possible uses of the profiles.It should be emphasised that it is an attempt to raise some tentative questions, rather than to provide definitive solutions.
2Dublin Core Application Profiles, the DCMI Abstract Model and Domain Models
The DCMI Abstract Model (DCAM)
describes an information structure called a DC“description set” and specifies how those description sets are to be interpreted as providing information about resources and the relationships between resources. It is amodel for/of metadata.Although the current DCMI specification probably doesn’t make this as clear as itshould, the DCAM is based on RDF, so a DC description set is, or can be mapped to,an RDF graph, and the DCAM uses the RDF and RDFS semantics rules for themerging of data and for inferencing on that data.
Note that the DCAM doesn’t specify either a model of the “world” being described byany particular description set, nor does it specify any particular set of metadata termsto be referenced by a description set. A DC description set is not limited to using theset of terms defined/owned by DCMI, and indeed it may be the case that a DCdescription set references none of those terms, and refers only to terms defined/owned by agencies other than DCMI.A Dublin Core Application Profile (DCAP)
is a specification which describes theconstruction of some specific set of DC metadata records. It provides:
A specification of the
to be addressed, what functions/operationsthe metadata should support
” of the entities to be described and their attributes andrelationships (based on the requirements to be supported)1