> KernelApplicationProfileDraft

The following 308 words could not be found in the dictionary of 550 words (including 550 LocalSpellingWords) and are highlighted below:

able   about   above   abstract   Abstract   according   action   additional   adjacent   allowed   allowing   also   an   and   anvlspec   Application   are   ark   as   aspects   Attach   avoid   bandwidth   base   based   basic   be   Beginning   begins   boils   borrows   both   burden   but   by   can   cdlib   characteristics   Citation   class   classes   collection   collections   commitment   commitments   compares   concise   content   context   Contributor   core   Core   correlating   Coverage   Creator   Date   date   dates   defines   description   descriptions   Descriptions   designed   detail   determinism   diglib   distills   do   document   documents   does   down   Dublin   dublincore   during   Each   Economy   eg   Electronic   element   Elements   elements   empty   encoding   encouraged   ended   ends   entered   erc   especially   essence   expense   explicitly   Expression   expression   externally   extra   eye   feature   File   flexibility   following   for   format   found   four   frames   Friendliness   friendly   from   Front   get   given   glance   goal   grasped   has   having   headers   holding   Identifier   identify   if   implicit   in   includes   indicating   information   inside   Interpretation   interpretation   into   is   Is   It   its   itself   journalistic   kernel   Kernel   kernelwiki   known   label   labels   languages   lexical   lines   listing   low   machine   made   management   manager   mapped   Mapping   meaningfully   meet   meta   Metadata   metadata   minimal   minimize   Model   model   more   Multi   name   need   needs   nine   none   normal   not   null   object   objects   of   on   one   open   opt   or   ordered   orderly   Organizations   origin   out   overall   overhead   Page   parsed   parser   pdf   perform   permitted   personage   plus   policies   positional   Predictability   problem   processing   produce   Profile   prohibitive   properties   property   providers   Publisher   purpose   query   ranges   readable   reading   record   records   Reduction   References   related   relationships   reliably   rely   relying   repeated   report   representations   required   requirement   Requirements   requirements   requirments   resource   Resource   rich   scheme   schemes   scripts   semantics   sets   should   simple   smaller   so   Some   sort   Sort   spatial   Spec   Spec00   specific   Specification   specification   specified   specifying   starts   story   string   strings   structure   sub   Subject   subset   subsets   such   support   supported   suppression   survey   surveying   target   tba   temporal   that   The   the   their   them   then   these   This   those   Title   to   To   tradition   troubleshooting   two   type   unac   unal   unap   unas   unav   unkn   useful   value   valued   values   visual   way   well   what   when   where   who   wish   with   without  

Clear message

DRAFT 1 -- The DC Kernel Application Profile -- 2007.08.07

This document defines the DC Kernel Application Profile (KAP), specifying its elements and requirements. The DC KAP is designed for providers that need to support the orderly management of their information objects, and wish to do so with minimal overhead in reading and processing metadata descriptions.

The document begins by listing kernel metadata requirements in more detail and correlating them with specific characteristics as found in the kernel metadata specification [KSpec]. It then compares the core DC semantics and DCMI Abstract Model [AModel] with kernel metadata elements and the Electronic Resource Citation (ERC) record structure for holding kernel resource descriptions.

Requirements

The overall goal of low-overhead, orderly management includes the needs to reliably identify problem objects during troubleshooting, and to query collections to produce ordered object subsets for the purpose of collection surveying. Organizations that perform orderly management should also be able to report externally on their support commitments and policies. The KAP frames these needs in the context of the following more specific requirments.

Reduction

Beginning with the 15 basic DC elements, the DC Kernel Specification [KSpec] distills out a smaller subset of elements to produce a concise description for troubleshooting that can be grasped in a glance. The kernel borrows from the journalistic tradition that "boils down" the essence of a story into the "who, what when, where" of an expression of an information resource.

Economy of Expression

To minimize the visual bandwidth in that glance, a simple eye- and machine-readable ERC format is specified that has both a normal and extra concise format (allowing suppression of labels by relying on positional elements). Multi-valued dates and ranges are also allowed so as to avoid having to rely on additional date elements, especially those indicating starts and ends of open-ended ranges.

Predictability

To meet the need for determinism during troubleshooting, the above four elements are required. Some flexibility in that requirement is permitted if the value for the given label is one of nine well-known values for "empty":

Sort-Friendliness

To be useful in orderly management, element values are encouraged to be entered in such a way that adjacent records in a collection survey can be meaningfully ordered by simple lexical sort on that element. The "sort-friendly" feature is not a requirement, i.e., providers can opt out if the expense is prohibitive.

Economy of Interpretation

To minimize burden of metadata interpretation by collection manager scripts, the ERC format is based on email headers [ANVL] and may be parsed in two lines of Perl (eg, without a DOM parser as required for XML).

Mapping from Kernel to Dublin Core Elements

Kernel elements are mapped to the 15 Dublin Core elements according to the "story" type. 

 erc:  the story of the expression of a resource
    who         from DC Creator, Contributor, or Publisher
    what        from DC Title
    when        from DC Date
    where       from DC Identifier

 about-erc:  the story of a resource's content
    about-who         from DC Subject (personage)
    about-what        from DC Subject
    about-when        from DC Coverage (temporal)
    about-where       from DC Coverage (spatial)

 meta-erc:  the story of the origin of the metadata record itself
    meta-who         (not mapped from DC)
    meta-what        (not mapped from DC)
    meta-when        (not mapped from DC)
    meta-where       (not mapped from DC)

 support-erc:  the story of a support commitment made to an object
    support-who         (not mapped from DC)
    support-what        (not mapped from DC)
    support-when        (not mapped from DC)
    support-where       (not mapped from DC)

The Abstract Model and DC Kernel Metadata Resource Descriptions

The following aspects of the DCMI abstract model are supported by the KAP:

The KAP does not support the following aspects of the DCMI abstract model:

URIs are not explicitly supported in the KAP, but may be implicit for:

Each property may be repeated.

References

[Spec] http://dublincore.org/kernelwiki/FrontPage?action=AttachFile&do=get&target=KernelSpec00.html
[Model] http://www.dublincore.org/documents/abstract-model/
[ANVL] http://www.cdlib.org/inside/diglib/ark/anvlspec.pdf