An Application Profile Using Darwin Core Rendered in the New Dublin Core Application Profile Framework Side: 1 of 1
The following text was automatically extracted from the image on this page using optical character recognition software:
HIGH-THROUGHPUT WORKFLOW FOR COMPUTER-ASSISTED HUMAN PARSING OF BIOLOGICAL SPECIMEN LABEL DATA
AN APPLICATION PROFILE USING DARWIN CORE RENDERED IN THE NEW DUBLI
Dublin Core Application Profile (DCAP)
Defines metadata records that meet specific application needs while providing semantic interoperability
with other applications on the basis of globally defined vocabularies and models.
Components of DCAP:
A DCAP is a set of documents addressing the following components:
" Functional Requirements (mandatory): Describes the functions that the application profile (AP) is
designed to support, as well as functions that are out of scope.
" Domain Model (mandatory): Describes the objects metadata will describe, and the relationships be-
tween those objects.
" Description Set Profile (DSP) (mandatory): Defines a set of metadata records that are valid in-
stances of an AP.
" Usage Guidelines (optional): Describes how to apply the AP, how the used properties are intended
to be used in the application context, etc.
" Encoding Syntax Guidelines (optional): Describes AP-specific syntaxes and/or syntax guideline, if
SCommunity Domain Model: A domain model which can be u;
tional Requirements for Bibliographic Records (FRBR) model f
SMetadata Vocabularies: One or more standard vocabularies 1
SDCMI Abstract Model: Specifies the components and constru
defines the nature of those components and how they are corr
Usage Guidelines: Provide instructions to create values for n
SDCMI Syntax Guidelines: Provide instructions on implements
into software applications. DCMI provides various encoding gu
SResource Description Framework (RDF): Provides a way to
semantics (http:l//www.w3.org/RDF/); a foundation which provi(
processing metadata RDF/S indicates an RDF Schema.
Apiary Functional Requirements
The Apiary Project's functional requirements include high-
level systems requirements and goals (e.g., optimizing the
workflow, system integration, and reusability of code) as well
as more detailed requirements, especially in terms of meta-
data needed for various objects that move through the sys-
tem. We used process-centered use case modeling to iden-
tify key objects, processes, and tasks. Specific metadata re-
quirements identified related to: types of metadata; standard
vocabularies (e.g., DwC); interoperability/shareability; con-
sistency and comprehensiveness; granularity; reusability;
and specific constraints on metadata terms.
Use Case Modeling Example
"" +- INSTITUTE of
" 0 EV
Apiary Domain Model
Description Set Profile -
The Apiary Domain Model defines four objects within the workflow that require metadata and shows the
relationships/derivations of the separate objects. For example, technical and administrative metadata
may be needed to manage the objects in the workflow. The Specimen Object will have DwC metadata
that is a result of the entire Apriary workflow. The Specimen Image Object is a scan of the herbarium
specimen sheet and the source from which the Region of Interest (ROI) Objects are derived; ROls may
include the primary label, first annotation, and other textual or graphical information on the herbarium
sheet. The Digital Text Object results from OCR on the ROI or manual transcription of data from an ROI.
Relationships between these objects can be one to one (1 ...1) or one to many (1 ...n) as indicated.
Apiary Metadata Vocabulary Terms
The Domain Model Objects have associated metadata properties
(terms) from multiple namespaces. DwC serves as the primary
source of terms (addressing the requirement for interoperability/
shareability). Objects may also have associated technical, preserva-
tion, and administrative metadata to serve the needs of the Apiary
system at every phase. Where essential to the Apiary application
and specimen data, locally-defined elements in an Apiary name-
space are being developed.
A DSP defines an information model and can be expressed in XML
data following guidelines for DSPs (http://dublincore.org/document,
<DescriptionTemplate ID="ApiarySpecimenCoreMetadata" maxOccur="l " n
<ResourceClass>http://rs. brit.orglap/objectslS pecimenMetadata</ResoL
<SyntaxEncod i ngSchemeOccurrence>disal lowed</SyntaxEnco
<VocabularyEncod i ngSchemeOccurrence>optional</Vocabu la
<VocabularyEncod i ngSchemeU RI >http://www. ipni .org/</Voca:
<ValueStringConstraint maxOccur="1 ">
The Utility of Application Profiles Rendered in DCAP
Region of Interest
"An application profile describes the set of guidelines, description rules, and constraints used in creating
a specific set of metadata records.. .application profiles are about providing high-level syntactic or struc-
tural interoperability in addition to the semantic interoperability" (http://dublincore.org/documents/
singapore-framework) By developing an Apiary AP, and especially the DSP, it can support one or more
of the following purposes:
* as a formal representation of the constraints of a Dublin Core Application Profile
* as configuration for databases
* as configuration for metadata editing tools.
DCMI has also issued a document, Interoperability Levels for Dublin Core Metadata (http://dublincore.org
assists developers in indicating conformance to specifications resulting in likely interoperability. The Apiar
Profile Interoperability. This should enable the production of shareable and interoperable metadata record
such records. Implementations of DCAPs in the biodiversity community should offer new and interesting c
Funded by U.S. Institute of Museum and Library Services National Leadership Grant # 06-08-0079-08
I 1 Tl w nn
N CORE APPLICATION PRC
1...n one to many relationship
1...1 - one to one relationship
This poster can be searched. Note: Results may vary based on the legibility of text within the document.
Citing and Sharing
Basic information for referencing this web page. We also provide extended guidance on usage rights, references, copying or embedding.
Reference the current side of this Poster.
Moen, William E.; Huang, Jane Q.; McCotter, Melody; Best, Jason H. & Neill, Amanda K. An Application Profile Using Darwin Core Rendered in the New Dublin Core Application Profile Framework, poster, November 2009; (digital.library.unt.edu/ark:/67531/metadc81371/m1/1/: accessed June 28, 2017), University of North Texas Libraries, Digital Library, digital.library.unt.edu; crediting UNT College of Information.