Lesson plan
Application profile
In the information sciences, an application profile consists of a set of metadata elements, policies, and guidelines defined for a particular application. 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.
Article summary
In the information sciences, an application profile consists of a set of metadata elements, policies, and guidelines defined for a particular application. 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.
Key claims
No claims recorded.
Discussion questions
- Summarise the article in your own words. Which single claim would you verify first, and why?
- Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
- If two sources disagreed about one of these facts, what would you need in order to trust one over the other?
Bibliography
No sources recorded.
Key claims and bibliography are generated from the same tracked claims and sources as the article page.