Application profile

In the information sciences, an application profile consists of a set of metadata elements, policies, and guidelines defined for a particular application.[1]

The elements may come from one or more element sets, thus allowing a given application to meet its functional requirements by using metadata from several element sets - including locally defined sets. For example, a given application might choose a subset of the Dublin Core that meets its needs, or may include elements from the Dublin Core, another element set, and several locally defined elements, all combined in a single schema. An application profile is not complete without documentation that defines the policies and best practices appropriate to the application. As another example, the legal document standard Akoma Ntoso is universal scope and very flexible, which creates the risk of ambiguous representations. Therefore, when AKN is to be used in a local domain, it can be advisable to reduce the overall flexibility and complexity by specifying a uniform usage of a subset of AKN XML elements for the given use case.[2]

## Contents

* 1 Advantages
* 2 Disadvantages
* 3 Example profiles
* 4 References

## Advantages

* Defines an application-appropriate set of properties in a public and communicable manner. This permits the building of loosely coupled systems (i.e. independent of each other's detailed specifications) that still offer powerful capabilities.[citation needed]

## Disadvantages

* Narrow application scope, which may limit a profile's widespread applicability and also limits the likely synergy from re-use of tools from other projects outside that scope.[citation needed]
* Compared to the Dublin Core refinement approach (where a core property set may be made more specific, in a backwards-compatible manner), use of application profiles requires that applications must at least recognise these profiles and their roots. Even if the profile is based simply on Dublin Core, which the application already understands, this is of no use unless the application also recognises that this profile is treatable as Dublin Core.[citation needed]

## Example profiles

* Bath Profile

An International Z39.50 Specification for Library Applications and Resource Discovery[3]

* e-GMS

the UK e-Government Metadata Standard. An application profile of Dublin Core.

## References

1. ↑ "Dublin Core metadata glossary". 26 August 2003. Archived from the original on 21 June 2006. https://web.archive.org/web/20060621074245/http://dublincore.org/documents/2001/04/12/usageguide/glossary.shtml. Retrieved 2006-06-08.
2. ↑ Flatt, Amelie; Langner, Arne; Leps, Olof (2022) (in en). Model-Driven Development of Akoma Ntoso Application Profiles - A Conceptual Framework for Model-Based Generation of XML Subschemas (1st ed.). Heidelberg: Sprinter Nature. ISBN 978-3-031-14131-7.
3. ↑ "The Bath Profile". 13 March 2000. http://www.ukoln.ac.uk/interop-focus/activities/z3950/int_profile/bath/draft/stable1.html.

0.00

(0 votes)

Original source: https://en.wikipedia.org/wiki/Application profile. Read more

|

Retrieved from "https://handwiki.org/wiki/index.php?title=Application_profile&oldid=229545"