€cdocutils.nodes
document
q)q}q(U nametypesq}q(X cool urisqˆX overviewqNX data packagingqNX isreferencedbyq ˆX examplesq
NX lagoze-2008q ˆX! additional packaging technologiesq NX contentsq
NX! package serialization using bagitqNX resource map validationqNX referencing other data packagesqNX background discussionqNX user storiesqNX ore vocabulary documentqˆX" ecological metadata language (eml)qNX citoqˆX classes, fields, and methodsqNX( algorithm for constructing data packagesqNX datacite2rdfqˆX generating resource mapsqNX formatqˆX
boyko-2009qˆX isrequiredbyq ˆX sauermann_cyganiak-2008q ˆX deviation from the ore modelq NX netcdfq NX data package client designq NX
conformstoq!ˆX oai-oreq"ˆX foresite python libraryq#ˆX* package content associations using oai-oreq$NX synopsisq%NX eml-2010q&ˆX issues and resolutionq'NX
referencesq(ˆX very large data packagesq)NX
identifierq*ˆX requiresq+ˆX relationq,ˆX netcdf-2010q-ˆuUsubstitution_defsq.}q/Uparse_messagesq0]q1cdocutils.nodes
system_message
q2)q3}q4(U rawsourceq5U Uparentq6cdocutils.nodes
section
q7)q8}q9(h5U U
referencedq:Kh6h7)q;}q<(h5U h6hUsourceq=Xg /var/lib/jenkins/jobs/API_Documentation_trunk/workspace/api-documentation/source/design/DataPackage.txtq>Utagnameq?Usectionq@U
attributesqA}qB(UdupnamesqC]UclassesqD]UbackrefsqE]UidsqF]qGUdata-packagingqHaUnamesqI]qJhauUlineqKKUdocumentqLhUchildrenqM]qN(cdocutils.nodes
title
qO)qP}qQ(h5X Data PackagingqRh6h;h=h>h?UtitleqShA}qT(hF]hE]hC]hD]hI]UrefidqUUid10qVuhKKhLhhM]qWcdocutils.nodes
Text
qXX Data PackagingqY…qZ}q[(h5hRh6hPubaubcdocutils.nodes
topic
q\)q]}q^(h5U h6h;h=h>h?Utopicq_hA}q`(hC]hD]qaUcontentsqbahE]hF]qcUcontentsqdahI]qeh
auhKKhLhhM]qf(hO)qg}qh(h5X ContentshA}qi(hC]hD]hE]hF]hI]uh6h]hM]qjhXX Contentsqk…ql}qm(h5U h6hgubah?hSubcdocutils.nodes
bullet_list
qn)qo}qp(h5U h6h]h=Nh?U bullet_listqqhA}qr(hC]hD]hE]hF]hI]uhKNhLhhM]qscdocutils.nodes
list_item
qt)qu}qv(h5U hA}qw(hC]hD]hE]hF]hI]uh6hohM]qx(cdocutils.nodes
paragraph
qy)qz}q{(h5U hA}q|(hC]hD]hE]hF]hI]uh6huhM]q}cdocutils.nodes
reference
q~)q}q€(h5U hA}q(hF]q‚hVahE]hC]hD]hI]UrefidhHuh6hzhM]qƒhXX Data Packagingq„…q…}q†(h5hRh6hubah?U referenceq‡ubah?U paragraphqˆubhn)q‰}qŠ(h5U hA}q‹(hC]hD]hE]hF]hI]uh6huhM]qŒ(ht)q}qŽ(h5U hA}q(hC]hD]hE]hF]hI]uh6h‰hM]qhy)q‘}q’(h5U hA}q“(hC]hD]hE]hF]hI]uh6hhM]q”h~)q•}q–(h5U hA}q—(hF]q˜Uid11q™ahE]hC]hD]hI]UrefidUsynopsisqšuh6h‘hM]q›hXX Synopsisqœ…q}qž(h5X SynopsisqŸh6h•ubah?h‡ubah?hˆubah?U list_itemq ubht)q¡}q¢(h5U hA}q£(hC]hD]hE]hF]hI]uh6h‰hM]q¤(hy)q¥}q¦(h5U hA}q§(hC]hD]hE]hF]hI]uh6h¡hM]q¨h~)q©}qª(h5U hA}q«(hF]q¬Uid12qahE]hC]hD]hI]UrefidUgenerating-resource-mapsq®uh6h¥hM]q¯hXX Generating Resource Mapsq°…q±}q²(h5X Generating Resource Mapsq³h6h©ubah?h‡ubah?hˆubhn)q´}qµ(h5U hA}q¶(hC]hD]hE]hF]hI]uh6h¡hM]q·(ht)q¸}q¹(h5U hA}qº(hC]hD]hE]hF]hI]uh6h´hM]q»hy)q¼}q½(h5U hA}q¾(hC]hD]hE]hF]hI]uh6h¸hM]q¿h~)qÀ}qÁ(h5U hA}qÂ(hF]qÃUid13qÄahE]hC]hD]hI]UrefidU deviation-from-the-ore-modelqÅuh6h¼hM]qÆhXX Deviation from the ORE modelqÇ…qÈ}qÉ(h5X Deviation from the ORE modelqÊh6hÀubah?h‡ubah?hˆubah?h ubht)qË}qÌ(h5U hA}qÍ(hC]hD]hE]hF]hI]uh6h´hM]qÎhy)qÏ}qÐ(h5U hA}qÑ(hC]hD]hE]hF]hI]uh6hËhM]qÒh~)qÓ}qÔ(h5U hA}qÕ(hF]qÖUid14q×ahE]hC]hD]hI]UrefidU referencing-other-data-packagesqØuh6hÏhM]qÙhXX Referencing other data packagesqÚ…qÛ}qÜ(h5X Referencing other data packagesqÝh6hÓubah?h‡ubah?hˆubah?h ubht)qÞ}qß(h5U hA}qà(hC]hD]hE]hF]hI]uh6h´hM]qáhy)qâ}qã(h5U hA}qä(hC]hD]hE]hF]hI]uh6hÞhM]qåh~)qæ}qç(h5U hA}qè(hF]qéUid15qêahE]hC]hD]hI]UrefidUvery-large-data-packagesqëuh6hâhM]qìhXX Very large data packagesqí…qî}qï(h5X Very large data packagesqðh6hæubah?h‡ubah?hˆubah?h ubeh?hqubeh?h ubht)qñ}qò(h5U hA}qó(hC]hD]hE]hF]hI]uh6h‰hM]qôhy)qõ}qö(h5U hA}q÷(hC]hD]hE]hF]hI]uh6hñhM]qøh~)qù}qú(h5U hA}qû(hF]qüUid16qýahE]hC]hD]hI]UrefidUresource-map-validationqþuh6hõhM]qÿhXX Resource map validationr …r }r (h5X Resource map validationr h6hùubah?h‡ubah?hˆubah?h ubht)r }r (h5U hA}r (hC]hD]hE]hF]hI]uh6h‰hM]r (hy)r }r (h5U hA}r
(hC]hD]hE]hF]hI]uh6j hM]r h~)r }r
(h5U hA}r (hF]r Uid17r ahE]hC]hD]hI]UrefidUbackground-discussionr uh6j hM]r hXX Background Discussionr …r }r (h5X Background Discussionr h6j ubah?h‡ubah?hˆubhn)r }r (h5U hA}r (hC]hD]hE]hF]hI]uh6j hM]r (ht)r }r (h5U hA}r (hC]hD]hE]hF]hI]uh6j hM]r hy)r }r (h5U hA}r! (hC]hD]hE]hF]hI]uh6j hM]r" h~)r# }r$ (h5U hA}r% (hF]r& Uid18r' ahE]hC]hD]hI]UrefidUoverviewr( uh6j hM]r) hXX Overviewr* …r+ }r, (h5X Overviewr- h6j# ubah?h‡ubah?hˆubah?h ubht)r. }r/ (h5U hA}r0 (hC]hD]hE]hF]hI]uh6j hM]r1 hy)r2 }r3 (h5U hA}r4 (hC]hD]hE]hF]hI]uh6j. hM]r5 h~)r6 }r7 (h5U hA}r8 (hF]r9 Uid19r: ahE]hC]hD]hI]UrefidU user-storiesr; uh6j2 hM]r< hXX User storiesr= …r> }r? (h5X User storiesr@ h6j6 ubah?h‡ubah?hˆubah?h ubht)rA }rB (h5U hA}rC (hC]hD]hE]hF]hI]uh6j hM]rD hy)rE }rF (h5U hA}rG (hC]hD]hE]hF]hI]uh6jA hM]rH h~)rI }rJ (h5U hA}rK (hF]rL Uid20rM ahE]hC]hD]hI]UrefidU*package-content-associations-using-oai-orerN uh6jE hM]rO hXX* Package Content Associations Using OAI-ORErP …rQ }rR (h5X* Package Content Associations Using OAI-ORErS h6jI ubah?h‡ubah?hˆubah?h ubht)rT }rU (h5U hA}rV (hC]hD]hE]hF]hI]uh6j hM]rW hy)rX }rY (h5U hA}rZ (hC]hD]hE]hF]hI]uh6jT hM]r[ h~)r\ }r] (h5U hA}r^ (hF]r_ Uid21r` ahE]hC]hD]hI]UrefidUissues-and-resolutionra uh6jX hM]rb hXX Issues and Resolutionrc …rd }re (h5X Issues and Resolutionrf h6j\ ubah?h‡ubah?hˆubah?h ubht)rg }rh (h5U hA}ri (hC]hD]hE]hF]hI]uh6j hM]rj hy)rk }rl (h5U hA}rm (hC]hD]hE]hF]hI]uh6jg hM]rn h~)ro }rp (h5U hA}rq (hF]rr Uid22rs ahE]hC]hD]hI]UrefidUexamplesrt uh6jk hM]ru hXX Examplesrv …rw }rx (h5X Examplesry h6jo ubah?h‡ubah?hˆubah?h ubeh?hqubeh?h ubht)rz }r{ (h5U hA}r| (hC]hD]hE]hF]hI]uh6h‰hM]r} hy)r~ }r (h5U hA}r€ (hC]hD]hE]hF]hI]uh6jz hM]r h~)r‚ }rƒ (h5U hA}r„ (hF]r… Uid23r† ahE]hC]hD]hI]UrefidU!package-serialization-using-bagitr‡ uh6j~ hM]rˆ hXX! Package Serialization Using BagItr‰ …rŠ }r‹ (h5X! Package Serialization Using BagItrŒ h6j‚ ubah?h‡ubah?hˆubah?h ubht)r }rŽ (h5U hA}r (hC]hD]hE]hF]hI]uh6h‰hM]r (hy)r‘ }r’ (h5U hA}r“ (hC]hD]hE]hF]hI]uh6j hM]r” h~)r• }r– (h5U hA}r— (hF]r˜ Uid24r™ ahE]hC]hD]hI]UrefidUdata-package-client-designrš uh6j‘ hM]r› hXX Data Package Client Designrœ …r }rž (h5X Data Package Client DesignrŸ h6j• ubah?h‡ubah?hˆubhn)r }r¡ (h5U hA}r¢ (hC]hD]hE]hF]hI]uh6j hM]r£ (ht)r¤ }r¥ (h5U hA}r¦ (hC]hD]hE]hF]hI]uh6j hM]r§ hy)r¨ }r© (h5U hA}rª (hC]hD]hE]hF]hI]uh6j¤ hM]r« h~)r¬ }r (h5U hA}r® (hF]r¯ Uid25r° ahE]hC]hD]hI]UrefidUclasses-fields-and-methodsr± uh6j¨ hM]r² hXX Classes, Fields, and Methodsr³ …r´ }rµ (h5X Classes, Fields, and Methodsr¶ h6j¬ ubah?h‡ubah?hˆubah?h ubht)r· }r¸ (h5U hA}r¹ (hC]hD]hE]hF]hI]uh6j hM]rº hy)r» }r¼ (h5U hA}r½ (hC]hD]hE]hF]hI]uh6j· hM]r¾ h~)r¿ }rÀ (h5U hA}rÁ (hF]r Uid26rà ahE]hC]hD]hI]UrefidU(algorithm-for-constructing-data-packagesrÄ uh6j» hM]rÅ hXX( Algorithm for Constructing Data PackagesrÆ …rÇ }rÈ (h5X( Algorithm for Constructing Data PackagesrÉ h6j¿ ubah?h‡ubah?hˆubah?h ubeh?hqubeh?h ubht)rÊ }rË (h5U hA}rÌ (hC]hD]hE]hF]hI]uh6h‰hM]rÍ (hy)rÎ }rÏ (h5U hA}rÐ (hC]hD]hE]hF]hI]uh6jÊ hM]rÑ h~)rÒ }rÓ (h5U hA}rÔ (hF]rÕ Uid27rÖ ahE]hC]hD]hI]UrefidU!additional-packaging-technologiesr× uh6jÎ hM]rØ hXX! Additional Packaging TechnologiesrÙ …rÚ }rÛ (h5X! Additional Packaging TechnologiesrÜ h6jÒ ubah?h‡ubah?hˆubhn)rÝ }rÞ (h5U hA}rß (hC]hD]hE]hF]hI]uh6jÊ hM]rà (ht)rá }râ (h5U hA}rã (hC]hD]hE]hF]hI]uh6jÝ hM]rä hy)rå }ræ (h5U hA}rç (hC]hD]hE]hF]hI]uh6já hM]rè h~)ré }rê (h5U hA}rë (hF]rì Uid28rí ahE]hC]hD]hI]UrefidU ecological-metadata-language-emlrî uh6jå hM]rï hXX" Ecological Metadata Language (EML)rð …rñ }rò (h5X" Ecological Metadata Language (EML)ró h6jé ubah?h‡ubah?hˆubah?h ubht)rô }rõ (h5U hA}rö (hC]hD]hE]hF]hI]uh6jÝ hM]r÷ hy)rø }rù (h5U hA}rú (hC]hD]hE]hF]hI]uh6jô hM]rû h~)rü }rý (h5U hA}rþ (hF]rÿ Uid29r ahE]hC]hD]hI]UrefidUnetcdfr uh6jø hM]r hXX NetCDFr …r }r (h5X NetCDFr h6jü ubah?h‡ubah?hˆubah?h ubeh?hqubeh?h ubht)r }r (h5U hA}r (hC]hD]hE]hF]hI]uh6h‰hM]r
hy)r }r (h5U hA}r
(hC]hD]hE]hF]hI]uh6j hM]r h~)r }r (h5U hA}r (hF]r Uid30r ahE]hC]hD]hI]UrefidUid6r uh6j hM]r hXX
Referencesr …r }r (h5X
Referencesr h6j ubah?h‡ubah?hˆubah?h ubeh?hqubeh?h ubaubeubh7)r }r (h5U h6h;h=h>h?h@hA}r (hC]hD]hE]hF]r hšahI]r h%auhKKhLhhM]r (hO)r }r! (h5hŸh6j h=h>h?hShA}r" (hF]hE]hC]hD]hI]hUh™uhKKhLhhM]r# hXX Synopsisr$ …r% }r& (h5hŸh6j ubaubhy)r' }r( (h5XÞ A :term:`data package` in DataONE is composed of at least one :term:`science
metadata` document describing at least one :term:`data` object with the
relationships between them documented in a :term:`resource map` document.h6j h=h>h?hˆhA}r) (hC]hD]hE]hF]hI]uhKK hLhhM]r* (hXX A r+ …r, }r- (h5X A h6j' ubcsphinx.addnodes
pending_xref
r. )r/ }r0 (h5X :term:`data package`r1 h6j' h=h>h?U pending_xrefr2 hA}r3 (UreftypeX termUrefwarnr4 ˆU reftargetr5 X data packageU refdomainX stdr6 hF]hE]U refexplicit‰hC]hD]hI]Urefdocr7 X design/DataPackager8 uhKK hM]r9 cdocutils.nodes
inline
r: )r; }r< (h5j1 hA}r= (hC]hD]r> (Uxrefr? j6 X std-termr@ ehE]hF]hI]uh6j/ hM]rA hXX data packagerB …rC }rD (h5U h6j; ubah?UinlinerE ubaubhXX( in DataONE is composed of at least one rF …rG }rH (h5X( in DataONE is composed of at least one h6j' ubj. )rI }rJ (h5X :term:`science
metadata`rK h6j' h=h>h?j2 hA}rL (UreftypeX termj4 ˆj5 X science metadataU refdomainX stdrM hF]hE]U refexplicit‰hC]hD]hI]j7 j8 uhKK hM]rN j: )rO }rP (h5jK hA}rQ (hC]hD]rR (j? jM X std-termrS ehE]hF]hI]uh6jI hM]rT hXX science
metadatarU …rV }rW (h5U h6jO ubah?jE ubaubhXX" document describing at least one rX …rY }rZ (h5X" document describing at least one h6j' ubj. )r[ }r\ (h5X :term:`data`r] h6j' h=h>h?j2 hA}r^ (UreftypeX termj4 ˆj5 X dataU refdomainX stdr_ hF]hE]U refexplicit‰hC]hD]hI]j7 j8 uhKK hM]r` j: )ra }rb (h5j] hA}rc (hC]hD]rd (j? j_ X std-termre ehE]hF]hI]uh6j[ hM]rf hXX datarg …rh }ri (h5U h6ja ubah?jE ubaubhXX< object with the
relationships between them documented in a rj …rk }rl (h5X< object with the
relationships between them documented in a h6j' ubj. )rm }rn (h5X :term:`resource map`ro h6j' h=h>h?j2 hA}rp (UreftypeX termj4 ˆj5 X resource mapU refdomainX stdrq hF]hE]U refexplicit‰hC]hD]hI]j7 j8 uhKK hM]rr j: )rs }rt (h5jo hA}ru (hC]hD]rv (j? jq X std-termrw ehE]hF]hI]uh6jm hM]rx hXX resource mapry …rz }r{ (h5U h6js ubah?jE ubaubhXX
document.r| …r} }r~ (h5X
document.h6j' ubeubhy)r }r€ (h5X Resource maps are RDF documents that conform to the Open Archives Initiative's
Object Reuse and Exchange (`OAI-ORE`_) specification as described in detail
below. Resource maps are generated by :term:`Member Nodes` to define data
packages, and have a :term:`formatId` of::h6j h=h>h?hˆhA}r (hC]hD]hE]hF]hI]uhKK
hLhhM]r‚ (hXXj Resource maps are RDF documents that conform to the Open Archives Initiative's
Object Reuse and Exchange (rƒ …r„ }r… (h5Xj Resource maps are RDF documents that conform to the Open Archives Initiative's
Object Reuse and Exchange (h6j ubh~)r† }r‡ (h5X
`OAI-ORE`_Uresolvedrˆ Kh6j h?h‡hA}r‰ (UnameX OAI-OREUrefurirŠ X! https://www.openarchives.org/ore/r‹ hF]hE]hC]hD]hI]uhM]rŒ hXX OAI-OREr …rŽ }r (h5U h6j† ubaubhXXM ) specification as described in detail
below. Resource maps are generated by r …r‘ }r’ (h5XM ) specification as described in detail
below. Resource maps are generated by h6j ubj. )r“ }r” (h5X :term:`Member Nodes`r• h6j h=h>h?j2 hA}r– (UreftypeX termj4 ˆj5 X member nodesU refdomainX stdr— hF]hE]U refexplicit‰hC]hD]hI]j7 j8 uhKK
hM]r˜ j: )r™ }rš (h5j• hA}r› (hC]hD]rœ (j? j— X std-termr ehE]hF]hI]uh6j“ hM]rž hXX Member NodesrŸ …r }r¡ (h5U h6j™ ubah?jE ubaubhXX% to define data
packages, and have a r¢ …r£ }r¤ (h5X% to define data
packages, and have a h6j ubj. )r¥ }r¦ (h5X :term:`formatId`r§ h6j h=h>h?j2 hA}r¨ (UreftypeX termj4 ˆj5 X formatidU refdomainX stdr© hF]hE]U refexplicit‰hC]hD]hI]j7 j8 uhKK
hM]rª j: )r« }r¬ (h5j§ hA}r (hC]hD]r® (j? j© X std-termr¯ ehE]hF]hI]uh6j¥ hM]r° hXX formatIdr± …r² }r³ (h5U h6j« ubah?jE ubaubhXX of:r´ …rµ }r¶ (h5X of:h6j ubeubcdocutils.nodes
literal_block
r· )r¸ }r¹ (h5X& http://www.openarchives.org/ore/terms/h6j h=h>h?U
literal_blockrº hA}r» (U xml:spacer¼ Upreserver½ hF]hE]hC]hD]hI]uhKKhLhhM]r¾ hXX& http://www.openarchives.org/ore/terms/r¿ …rÀ }rÁ (h5U h6j¸ ubaubhy)r }rà (h5Xf Note this is a name space string. The actual ORE terms can be found in the
`ORE Vocabulary Document`_.h6j h=h>h?hˆhA}rÄ (hC]hD]hE]hF]hI]uhKKhLhhM]rÅ (hXXK Note this is a name space string. The actual ORE terms can be found in the
rÆ …rÇ }rÈ (h5XK Note this is a name space string. The actual ORE terms can be found in the
h6j ubh~)rÉ }rÊ (h5X `ORE Vocabulary Document`_jˆ Kh6j h?h‡hA}rË (UnameX ORE Vocabulary DocumentjŠ X. http://www.openarchives.org/ore/1.0/vocabularyrÌ hF]hE]hC]hD]hI]uhM]rÍ hXX ORE Vocabulary DocumentrÎ …rÏ }rÐ (h5U h6jÉ ubaubhXX .…rÑ }rÒ (h5X .h6j ubeubcdocutils.nodes
target
rÓ )rÔ }rÕ (h5X. .. _OAI-ORE: https://www.openarchives.org/ore/h:Kh6j h=h>h?UtargetrÖ hA}r× (jŠ j‹ hF]rØ Uoai-orerÙ ahE]hC]hD]hI]rÚ h"auhKKhLhhM]ubjÓ )rÛ }rÜ (h5XK .. _ORE Vocabulary Document: http://www.openarchives.org/ore/1.0/vocabularyh:Kh6j h=h>h?jÖ hA}rÝ (jŠ jÌ hF]rÞ Uore-vocabulary-documentrß ahE]hC]hD]hI]rà hauhKKhLhhM]ubcdocutils.nodes
image
rá )râ }rã (h5X( .. image:: images/datapackage_class.png
h6j h=h>h?Uimagerä hA}rå (UuriX# design/images/datapackage_class.pngræ hF]hE]hC]hD]U
candidatesrç }rè U*jæ shI]uhKKhLhhM]ubhy)ré }rê (h5Xn Overview class diagram for content model in DataONE. Class attributes refer to
the equivalent SOLR index entryrë h6j h=h>h?hˆhA}rì (hC]hD]hE]hF]hI]uhKK hLhhM]rí hXXn Overview class diagram for content model in DataONE. Class attributes refer to
the equivalent SOLR index entryrî …rï }rð (h5jë h6jé ubaubcdocutils.nodes
comment
rñ )rò }ró (h5X" @startuml images/datapackage_class.png
left to right direction
class DataONEObject {
String id
Integer size
String formatId
String AuthoritativeMN
Date dateUploaded
Boolean isPublic
String obsoletedBy
...
}
class ResourceMap {
Relation[]: relations
}
class Relation {
URI cito:documents
URI cito:isDocumentedBy
}
class ScienceMetadata {
String title
String abstract
String[] authors
Date beginDate
Date endDate
Float eastBoundingCoord
Float westBoundingCoord
Float northBoundingCoord
Float southBoundingCoord
...
}
class ScienceData {
}
DataONEObject <|-- ResourceMap
DataONEObject <|-- ScienceMetadata
DataONEObject <|-- ScienceData
ScienceData "0..*" - "0..*" ScienceMetadata
(ScienceMetadata, ScienceData) . Relation
ResourceMap o-- Relation
@endumlh6j h=h>h?Ucommentrô hA}rõ (j¼ j½ hF]hE]hC]hD]hI]uhKKQhLhhM]rö hXX" @startuml images/datapackage_class.png
left to right direction
class DataONEObject {
String id
Integer size
String formatId
String AuthoritativeMN
Date dateUploaded
Boolean isPublic
String obsoletedBy
...
}
class ResourceMap {
Relation[]: relations
}
class Relation {
URI cito:documents
URI cito:isDocumentedBy
}
class ScienceMetadata {
String title
String abstract
String[] authors
Date beginDate
Date endDate
Float eastBoundingCoord
Float westBoundingCoord
Float northBoundingCoord
Float southBoundingCoord
...
}
class ScienceData {
}
DataONEObject <|-- ResourceMap
DataONEObject <|-- ScienceMetadata
DataONEObject <|-- ScienceData
ScienceData "0..*" - "0..*" ScienceMetadata
(ScienceMetadata, ScienceData) . Relation
ResourceMap o-- Relation
@endumlr÷ …rø }rù (h5U h6jò ubaubeubh7)rú }rû (h5U h6h;h=h>h?h@hA}rü (hC]hD]hE]hF]rý h®ahI]rþ hauhKKShLhhM]rÿ (hO)r }r (h5h³h6jú h=h>h?hShA}r (hF]hE]hC]hD]hI]hUhuhKKShLhhM]r hXX Generating Resource Mapsr …r }r (h5h³h6j ubaubhy)r }r (h5X© While there are several formats discussed in the general discussion below,
DataONE currently only supports the RDF/XML serialization format, using the
:term:`formatId` of ``http://www/openarchives.org/ore/terms``. For more
information on OAI-ORE resource maps, see
http://www.openarchives.org/ore/1.0/primer, especially sections 3 and 4. For
more details on RDF/XML format, see
http://www.openarchives.org/ore/1.0/rdfxml.htmlh6jú h=h>h?hˆhA}r (hC]hD]hE]hF]hI]uhKKUhLhhM]r
(hXX— While there are several formats discussed in the general discussion below,
DataONE currently only supports the RDF/XML serialization format, using the
r …r }r
(h5X— While there are several formats discussed in the general discussion below,
DataONE currently only supports the RDF/XML serialization format, using the
h6j ubj. )r }r (h5X :term:`formatId`r h6j h=h>h?j2 hA}r (UreftypeX termj4 ˆj5 X formatidU refdomainX stdr hF]hE]U refexplicit‰hC]hD]hI]j7 j8 uhKKUhM]r j: )r }r (h5j hA}r (hC]hD]r (j? j X std-termr ehE]hF]hI]uh6j hM]r hXX formatIdr …r }r (h5U h6j ubah?jE ubaubhXX of r …r }r (h5X of h6j ubcdocutils.nodes
literal
r )r! }r" (h5X) ``http://www/openarchives.org/ore/terms``hA}r# (hC]hD]hE]hF]hI]uh6j hM]r$ hXX% http://www/openarchives.org/ore/termsr% …r& }r' (h5U h6j! ubah?Uliteralr( ubhXX5 . For more
information on OAI-ORE resource maps, see
r) …r* }r+ (h5X5 . For more
information on OAI-ORE resource maps, see
h6j ubh~)r, }r- (h5X* http://www.openarchives.org/ore/1.0/primerr. hA}r/ (Urefurij. hF]hE]hC]hD]hI]uh6j hM]r0 hXX* http://www.openarchives.org/ore/1.0/primerr1 …r2 }r3 (h5U h6j, ubah?h‡ubhXXG , especially sections 3 and 4. For
more details on RDF/XML format, see
r4 …r5 }r6 (h5XG , especially sections 3 and 4. For
more details on RDF/XML format, see
h6j ubh~)r7 }r8 (h5X/ http://www.openarchives.org/ore/1.0/rdfxml.htmlr9 hA}r: (Urefurij9 hF]hE]hC]hD]hI]uh6j hM]r; hXX/ http://www.openarchives.org/ore/1.0/rdfxml.htmlr< …r= }r> (h5U h6j7 ubah?h‡ubeubhy)r? }r@ (h5XŽ DataONE provides tools in both the Java and Python client libraries for building
and serializing / deserializing resource maps, both based on the foresite-toolkit
project (https://code.google.com/p/foresite-toolkit/). These are highly recommended
for those who do not want to spend time on learning the OAI-ORE implementation model
in detail in order to build and maintain a custom implementation.h6jú h=h>h?hˆhA}rA (hC]hD]hE]hF]hI]uhKK^hLhhM]rB (hXX¬ DataONE provides tools in both the Java and Python client libraries for building
and serializing / deserializing resource maps, both based on the foresite-toolkit
project (rC …rD }rE (h5X¬ DataONE provides tools in both the Java and Python client libraries for building
and serializing / deserializing resource maps, both based on the foresite-toolkit
project (h6j? ubh~)rF }rG (h5X+ https://code.google.com/p/foresite-toolkit/rH hA}rI (UrefurijH hF]hE]hC]hD]hI]uh6j? hM]rJ hXX+ https://code.google.com/p/foresite-toolkit/rK …rL }rM (h5U h6jF ubah?h‡ubhXX· ). These are highly recommended
for those who do not want to spend time on learning the OAI-ORE implementation model
in detail in order to build and maintain a custom implementation.rN …rO }rP (h5X· ). These are highly recommended
for those who do not want to spend time on learning the OAI-ORE implementation model
in detail in order to build and maintain a custom implementation.h6j? ubeubhy)rQ }rR (h5Xò The ORE data model itself is flexible and general purpose. In order to use it
for our purposes, DataONE places a few additional constraints on the model. (See
http://www.openarchives.org/ore/1.0/datamodel for details on the ORE data model).h6jú h=h>h?hˆhA}rS (hC]hD]hE]hF]hI]uhKKdhLhhM]rT (hXX¡ The ORE data model itself is flexible and general purpose. In order to use it
for our purposes, DataONE places a few additional constraints on the model. (See
rU …rV }rW (h5X¡ The ORE data model itself is flexible and general purpose. In order to use it
for our purposes, DataONE places a few additional constraints on the model. (See
h6jQ ubh~)rX }rY (h5X- http://www.openarchives.org/ore/1.0/datamodelrZ hA}r[ (UrefurijZ hF]hE]hC]hD]hI]uh6jQ hM]r\ hXX- http://www.openarchives.org/ore/1.0/datamodelr] …r^ }r_ (h5U h6jX ubah?h‡ubhXX$ for details on the ORE data model).r` …ra }rb (h5X$ for details on the ORE data model).h6jQ ubeubcdocutils.nodes
enumerated_list
rc )rd }re (h5U h6jú h=h>h?Uenumerated_listrf hA}rg (Usuffixrh U.hF]hE]hC]Uprefixri U hD]hI]Uenumtyperj Uarabicrk uhKKihLhhM]rl (ht)rm }rn (h5Xæ all DataONE objects in the map MUST be expressed as a URI using DataONE's
resolving service, instead of reference to a specific replica on a member
node. This is to separate the current physical location from the resource
itself.h6jd h=h>h?h hA}ro (hC]hD]hE]hF]hI]uhKNhLhhM]rp hy)rq }rr (h5Xæ all DataONE objects in the map MUST be expressed as a URI using DataONE's
resolving service, instead of reference to a specific replica on a member
node. This is to separate the current physical location from the resource
itself.rs h6jm h=h>h?hˆhA}rt (hC]hD]hE]hF]hI]uhKKihM]ru hXXæ all DataONE objects in the map MUST be expressed as a URI using DataONE's
resolving service, instead of reference to a specific replica on a member
node. This is to separate the current physical location from the resource
itself.rv …rw }rx (h5js h6jq ubaubaubht)ry }rz (h5XQ The aggregation resource URI SHOULD be expressed as a hash URI based on the
resource map URI, as recommended by ORE (see: http://www.openarchives.org/ore/1.0/primer#remHashURIs,
and http://www.openarchives.org/ore/1.0/http#Simple) This ensures that the
aggregation can be referenced directly in other resource maps and still be
resolved.h6jd h=h>h?h hA}r{ (hC]hD]hE]hF]hI]uhKNhLhhM]r| hy)r} }r~ (h5XQ The aggregation resource URI SHOULD be expressed as a hash URI based on the
resource map URI, as recommended by ORE (see: http://www.openarchives.org/ore/1.0/primer#remHashURIs,
and http://www.openarchives.org/ore/1.0/http#Simple) This ensures that the
aggregation can be referenced directly in other resource maps and still be
resolved.h6jy h=h>h?hˆhA}r (hC]hD]hE]hF]hI]uhKKmhM]r€ (hXXz The aggregation resource URI SHOULD be expressed as a hash URI based on the
resource map URI, as recommended by ORE (see: r …r‚ }rƒ (h5Xz The aggregation resource URI SHOULD be expressed as a hash URI based on the
resource map URI, as recommended by ORE (see: h6j} ubh~)r„ }r… (h5X6 http://www.openarchives.org/ore/1.0/primer#remHashURIsr† hA}r‡ (Urefurij† hF]hE]hC]hD]hI]uh6j} hM]rˆ hXX6 http://www.openarchives.org/ore/1.0/primer#remHashURIsr‰ …rŠ }r‹ (h5U h6j„ ubah?h‡ubhXX ,
and rŒ …r }rŽ (h5X ,
and h6j} ubh~)r }r (h5X/ http://www.openarchives.org/ore/1.0/http#Simpler‘ hA}r’ (Urefurij‘ hF]hE]hC]hD]hI]uh6j} hM]r“ hXX/ http://www.openarchives.org/ore/1.0/http#Simpler” …r• }r– (h5U h6j ubah?h‡ubhXXl ) This ensures that the
aggregation can be referenced directly in other resource maps and still be
resolved.r— …r˜ }r™ (h5Xl ) This ensures that the
aggregation can be referenced directly in other resource maps and still be
resolved.h6j} ubeubaubht)rš }r› (h5X‚ When referencing another DataONE data package, the URI of the package being
referenced MUST resolve to a resource map. The URI can either be the resource
map URI or the aggregation URI if it follows the hash URI format. Since some
existing resource maps do not use aggregation URI's that resolve to the
resource map, it is necessary to check their format before deciding which to use.h6jd h=h>h?h hA}rœ (hC]hD]hE]hF]hI]uhKNhLhhM]r hy)rž }rŸ (h5X‚ When referencing another DataONE data package, the URI of the package being
referenced MUST resolve to a resource map. The URI can either be the resource
map URI or the aggregation URI if it follows the hash URI format. Since some
existing resource maps do not use aggregation URI's that resolve to the
resource map, it is necessary to check their format before deciding which to use.r h6jš h=h>h?hˆhA}r¡ (hC]hD]hE]hF]hI]uhKKrhM]r¢ hXX‚ When referencing another DataONE data package, the URI of the package being
referenced MUST resolve to a resource map. The URI can either be the resource
map URI or the aggregation URI if it follows the hash URI format. Since some
existing resource maps do not use aggregation URI's that resolve to the
resource map, it is necessary to check their format before deciding which to use.r£ …r¤ }r¥ (h5j h6jž ubaubaubht)r¦ }r§ (h5X„ each resource with a representation in DataONE MUST be described with an
dcterms:identifier field containing the DataONE identifier.h6jd h=h>h?h hA}r¨ (hC]hD]hE]hF]hI]uhKNhLhhM]r© hy)rª }r« (h5X„ each resource with a representation in DataONE MUST be described with an
dcterms:identifier field containing the DataONE identifier.r¬ h6j¦ h=h>h?hˆhA}r (hC]hD]hE]hF]hI]uhKKwhM]r® hXX„ each resource with a representation in DataONE MUST be described with an
dcterms:identifier field containing the DataONE identifier.r¯ …r° }r± (h5j¬ h6jª ubaubaubht)r² }r³ (h5Xê when expressing an identifier in a URI, it must be URL encoded. When expressing
in the dcterms:identifier field, it must not. (Of course any XML encoding
would need to be applied as well, in the example below, there is none needed).h6jd h=h>h?h hA}r´ (hC]hD]hE]hF]hI]uhKNhLhhM]rµ hy)r¶ }r· (h5Xê when expressing an identifier in a URI, it must be URL encoded. When expressing
in the dcterms:identifier field, it must not. (Of course any XML encoding
would need to be applied as well, in the example below, there is none needed).r¸ h6j² h=h>h?hˆhA}r¹ (hC]hD]hE]hF]hI]uhKKyhM]rº hXXê when expressing an identifier in a URI, it must be URL encoded. When expressing
in the dcterms:identifier field, it must not. (Of course any XML encoding
would need to be applied as well, in the example below, there is none needed).r» …r¼ }r½ (h5j¸ h6j¶ ubaubaubht)r¾ }r¿ (h5X# the resource map MUST assert a triple with the pre:isDescribedBy relationship
between the resource map and the aggregation, following the recommendation that
aggregations with multiple resource maps express this relationship.
(see http://www.openarchives.org/ore/1.0/datamodel#ReM-to-aggr)
h6jd h=h>h?h hA}rÀ (hC]hD]hE]hF]hI]uhKNhLhhM]rÁ hy)r }rà (h5X! the resource map MUST assert a triple with the pre:isDescribedBy relationship
between the resource map and the aggregation, following the recommendation that
aggregations with multiple resource maps express this relationship.
(see http://www.openarchives.org/ore/1.0/datamodel#ReM-to-aggr)rÄ h6j¾ h=h>h?hˆhA}rÅ (hC]hD]hE]hF]hI]uhKK|hM]rÆ hXX! the resource map MUST assert a triple with the pre:isDescribedBy relationship
between the resource map and the aggregation, following the recommendation that
aggregations with multiple resource maps express this relationship.
(see http://www.openarchives.org/ore/1.0/datamodel#ReM-to-aggr)rÇ …rÈ }rÉ (h5jÄ h6j ubaubaubeubhy)rÊ }rË (h5Xl For example, the triple representing 'scimeta_id1/foo documents scidata_id1' would
look like the following::h6jú h=h>h?hˆhA}rÌ (hC]hD]hE]hF]hI]uhKK‚hLhhM]rÍ hXXk For example, the triple representing 'scimeta_id1/foo documents scidata_id1' would
look like the following:rÎ …rÏ }rÐ (h5Xk For example, the triple representing 'scimeta_id1/foo documents scidata_id1' would
look like the following:h6jÊ ubaubj· )rÑ }rÒ (h5Xù
scimeta_id/foo
...
h6jú h=h>h?jº hA}rÓ (j¼ j½ hF]hE]hC]hD]hI]uhKK…hLhhM]rÔ hXXù
scimeta_id/foo
...
rÕ …rÖ }r× (h5U h6jÑ ubaubhy)rØ }rÙ (h5X< and the aggregation resource would look like the following::rÚ h6jú h=h>h?hˆhA}rÛ (hC]hD]hE]hF]hI]uhKK‹hLhhM]rÜ hXX; and the aggregation resource would look like the following:rÝ …rÞ }rß (h5X; and the aggregation resource would look like the following:h6jØ ubaubj· )rà }rá (h5XÍ
...
h6jú h=h>h?jº hA}râ (j¼ j½ hF]hE]hC]hD]hI]uhKKhLhhM]rã hXXÍ
...
rä …rå }ræ (h5U h6jà ubaubhy)rç }rè (h5X` See the Examples section under Background Discussion below for a full example of
a resource map.ré h6jú h=h>h?hˆhA}rê (hC]hD]hE]hF]hI]uhKK–hLhhM]rë hXX` See the Examples section under Background Discussion below for a full example of
a resource map.rì …rí }rî (h5jé h6jç ubaubh7)rï }rð (h5U h6jú h=h>h?h@hA}rñ (hC]hD]hE]hF]rò hÅahI]ró h auhKKšhLhhM]rô (hO)rõ }rö (h5hÊh6jï h=h>h?hShA}r÷ (hF]hE]hC]hD]hI]hUhÄuhKKšhLhhM]rø hXX Deviation from the ORE modelrù …rú }rû (h5hÊh6jõ ubaubhy)rü }rý (h5XZ Because DataONE already contains resource maps whose aggregation URIs do not
conform to the ORE specification that they can be resolved to a resource map, we
cannot assert that the collection of resource maps adhere to the specification,
and therefore will not will not require conformity in this aspect for resource
maps submitted in the future.rþ h6jï h=h>h?hˆhA}rÿ (hC]hD]hE]hF]hI]uhKKœhLhhM]r hXXZ Because DataONE already contains resource maps whose aggregation URIs do not
conform to the ORE specification that they can be resolved to a resource map, we
cannot assert that the collection of resource maps adhere to the specification,
and therefore will not will not require conformity in this aspect for resource
maps submitted in the future.r …r }r (h5jþ h6jü ubaubhy)r }r (h5XŠ As a result, users must be careful when referencing aggregations directly from
other data packages, as not all of them will resolve to a resource map. Similarly,
if the collection of resource maps is put together into a triple store, these
non-resolving aggregation URIs cannot be guaranteed to be unique, the result of
which is that mistaken relationships between unrelated items would occur.r h6jï h=h>h?hˆhA}r (hC]hD]hE]hF]hI]uhKK¢hLhhM]r hXXŠ As a result, users must be careful when referencing aggregations directly from
other data packages, as not all of them will resolve to a resource map. Similarly,
if the collection of resource maps is put together into a triple store, these
non-resolving aggregation URIs cannot be guaranteed to be unique, the result of
which is that mistaken relationships between unrelated items would occur.r …r
}r (h5j h6j ubaubeubh7)r }r
(h5U h6jú h=h>h?h@hA}r (hC]hD]hE]hF]r hØahI]r hauhKK«hLhhM]r (hO)r }r (h5hÝh6j h=h>h?hShA}r (hF]hE]hC]hD]hI]hUh×uhKK«hLhhM]r hXX Referencing other data packagesr …r }r (h5hÝh6j ubaubhy)r }r (h5Xm The main use case in DataONE for referencing other data packages in a resource map
is that of nesting one inside another, which makes the 'other' data package itself
something that is being aggregated. Especially in such cases, it is necessary
that the URI used to represent the data package being aggregated can be resolved
to its resource map. If the aggregation URI follows the has URI format, it will
resolve to the resource map when following the URI. Otherwise, the URI of the
resource map should be used. In both cases clients following the URI of the
aggregated resource will get the resource map, as desired.r h6j h=h>h?hˆhA}r (hC]hD]hE]hF]hI]uhKKhLhhM]r hXXm The main use case in DataONE for referencing other data packages in a resource map
is that of nesting one inside another, which makes the 'other' data package itself
something that is being aggregated. Especially in such cases, it is necessary
that the URI used to represent the data package being aggregated can be resolved
to its resource map. If the aggregation URI follows the has URI format, it will
resolve to the resource map when following the URI. Otherwise, the URI of the
resource map should be used. In both cases clients following the URI of the
aggregated resource will get the resource map, as desired.r …r }r (h5j h6j ubaubhy)r! }r" (h5XT To check that the aggregation is in hash URI form, the following check can be used::r# h6j h=h>h?hˆhA}r$ (hC]hD]hE]hF]hI]uhKK¶hLhhM]r% hXXS To check that the aggregation is in hash URI form, the following check can be used:r& …r' }r( (h5XS To check that the aggregation is in hash URI form, the following check can be used:h6j! ubaubj· )r) }r* (h5X6 aggregation_X_uri startsWith (resourceMap_X_uri + "#")h6j h=h>h?jº hA}r+ (j¼ j½ hF]hE]hC]hD]hI]uhKK¸hLhhM]r, hXX6 aggregation_X_uri startsWith (resourceMap_X_uri + "#")r- …r. }r/ (h5U h6j) ubaubhy)r0 }r1 (h5Xà Notes: Future infrastructure development will likely involve standing up a triple-store
where all resource maps will be held. Any aggregation not in hash URI form cannot
be relied upon to be unique, otherwise incorrect connections between unrelated
objects are possible. Likely solutions for incorporation of existing non-hashURI
aggregations include either renaming the aggregations upon import, or treating
them as relative URIs that would be appended to the resourceMap URI.r2 h6j h=h>h?hˆhA}r3 (hC]hD]hE]hF]hI]uhKK»hLhhM]r4 hXXà Notes: Future infrastructure development will likely involve standing up a triple-store
where all resource maps will be held. Any aggregation not in hash URI form cannot
be relied upon to be unique, otherwise incorrect connections between unrelated
objects are possible. Likely solutions for incorporation of existing non-hashURI
aggregations include either renaming the aggregations upon import, or treating
them as relative URIs that would be appended to the resourceMap URI.r5 …r6 }r7 (h5j2 h6j0 ubaubeubh7)r8 }r9 (h5U h6jú h=h>h?h@hA}r: (hC]hD]hE]hF]r; hëahI]r< h)auhKKÄhLhhM]r= (hO)r> }r? (h5hðh6j8 h=h>h?hShA}r@ (hF]hE]hC]hD]hI]hUhêuhKKÄhLhhM]rA hXX Very large data packagesrB …rC }rD (h5hðh6j> ubaubhy)rE }rF (h5X Current tools for building and parsing resource maps are not able to handle data
packages that aggregate a very large number of objects. The DataPackage class
in d1_libclient_java was used to attempt to create serialized resource maps of
increasing size. Results are summarized below:rG h6j8 h=h>h?hˆhA}rH (hC]hD]hE]hF]hI]uhKKÆhLhhM]rI hXX Current tools for building and parsing resource maps are not able to handle data
packages that aggregate a very large number of objects. The DataPackage class
in d1_libclient_java was used to attempt to create serialized resource maps of
increasing size. Results are summarized below:rJ …rK }rL (h5jG h6jE ubaubcdocutils.nodes
table
rM )rN }rO (h5U h6j8 h=h>h?UtablerP hA}rQ (hC]hD]hE]hF]hI]uhKNhLhhM]rR cdocutils.nodes
tgroup
rS )rT }rU (h5U hA}rV (hF]hE]hC]hD]hI]UcolsKuh6jN hM]rW (cdocutils.nodes
colspec
rX )rY }rZ (h5U hA}r[ (hF]hE]hC]hD]hI]UcolwidthKuh6jT hM]h?Ucolspecr\ ubjX )r] }r^ (h5U hA}r_ (hF]hE]hC]hD]hI]UcolwidthK#uh6jT hM]h?j\ ubcdocutils.nodes
thead
r` )ra }rb (h5U hA}rc (hC]hD]hE]hF]hI]uh6jT hM]rd cdocutils.nodes
row
re )rf }rg (h5U hA}rh (hC]hD]hE]hF]hI]uh6ja hM]ri (cdocutils.nodes
entry
rj )rk }rl (h5U hA}rm (hC]hD]hE]hF]hI]uh6jf hM]rn hy)ro }rp (h5X # of data objectsrq h6jk h=h>h?hˆhA}rr (hC]hD]hE]hF]hI]uhKKÌhM]rs hXX # of data objectsrt …ru }rv (h5jq h6jo ubaubah?Uentryrw ubjj )rx }ry (h5U hA}rz (hC]hD]hE]hF]hI]uh6jf hM]r{ hy)r| }r} (h5X
time to buildr~ h6jx h=h>h?hˆhA}r (hC]hD]hE]hF]hI]uhKKÌhM]r€ hXX
time to buildr …r‚ }rƒ (h5j~ h6j| ubaubah?jw ubeh?Urowr„ ubah?Utheadr… ubcdocutils.nodes
tbody
r† )r‡ }rˆ (h5U hA}r‰ (hC]hD]hE]hF]hI]uh6jT hM]rŠ (je )r‹ }rŒ (h5U hA}r (hC]hD]hE]hF]hI]uh6j‡ hM]rŽ (jj )r }r (h5U hA}r‘ (hC]hD]hE]hF]hI]uh6j‹ hM]r’ hy)r“ }r” (h5X 100r• h6j h=h>h?hˆhA}r– (hC]hD]hE]hF]hI]uhKKÎhM]r— hXX 100r˜ …r™ }rš (h5j• h6j“ ubaubah?jw ubjj )r› }rœ (h5U hA}r (hC]hD]hE]hF]hI]uh6j‹ hM]rž hy)rŸ }r (h5X
2 secondsr¡ h6j› h=h>h?hˆhA}r¢ (hC]hD]hE]hF]hI]uhKKÎhM]r£ hXX
2 secondsr¤ …r¥ }r¦ (h5j¡ h6jŸ ubaubah?jw ubeh?j„ ubje )r§ }r¨ (h5U hA}r© (hC]hD]hE]hF]hI]uh6j‡ hM]rª (jj )r« }r¬ (h5U hA}r (hC]hD]hE]hF]hI]uh6j§ hM]r® hy)r¯ }r° (h5X 1000r± h6j« h=h>h?hˆhA}r² (hC]hD]hE]hF]hI]uhKKÏhM]r³ hXX 1000r´ …rµ }r¶ (h5j± h6j¯ ubaubah?jw ubjj )r· }r¸ (h5U hA}r¹ (hC]hD]hE]hF]hI]uh6j§ hM]rº hy)r» }r¼ (h5X
3 secondsr½ h6j· h=h>h?hˆhA}r¾ (hC]hD]hE]hF]hI]uhKKÏhM]r¿ hXX
3 secondsrÀ …rÁ }r (h5j½ h6j» ubaubah?jw ubeh?j„ ubje )rà }rÄ (h5U hA}rÅ (hC]hD]hE]hF]hI]uh6j‡ hM]rÆ (jj )rÇ }rÈ (h5U hA}rÉ (hC]hD]hE]hF]hI]uh6jà hM]rÊ hy)rË }rÌ (h5X 3000rÍ h6jÇ h=h>h?hˆhA}rÎ (hC]hD]hE]hF]hI]uhKKÐhM]rÏ hXX 3000rÐ …rÑ }rÒ (h5jÍ h6jË ubaubah?jw ubjj )rÓ }rÔ (h5U hA}rÕ (hC]hD]hE]hF]hI]uh6jà hM]rÖ hy)r× }rØ (h5X 20 secondsrÙ h6jÓ h=h>h?hˆhA}rÚ (hC]hD]hE]hF]hI]uhKKÐhM]rÛ hXX 20 secondsrÜ …rÝ }rÞ (h5jÙ h6j× ubaubah?jw ubeh?j„ ubje )rß }rà (h5U hA}rá (hC]hD]hE]hF]hI]uh6j‡ hM]râ (jj )rã }rä (h5U hA}rå (hC]hD]hE]hF]hI]uh6jß hM]ræ hy)rç }rè (h5X 10000ré h6jã h=h>h?hˆhA}rê (hC]hD]hE]hF]hI]uhKKÑhM]rë hXX 10000rì …rí }rî (h5jé h6jç ubaubah?jw ubjj )rï }rð (h5U hA}rñ (hC]hD]hE]hF]hI]uh6jß hM]rò hy)ró }rô (h5X
5 minutesrõ h6jï h=h>h?hˆhA}rö (hC]hD]hE]hF]hI]uhKKÑhM]r÷ hXX
5 minutesrø …rù }rú (h5jõ h6jó ubaubah?jw ubeh?j„ ubje )rû }rü (h5U hA}rý (hC]hD]hE]hF]hI]uh6j‡ hM]rþ (jj )rÿ }r (h5U hA}r (hC]hD]hE]hF]hI]uh6jû hM]r hy)r }r (h5X 30000r h6jÿ h=h>h?hˆhA}r (hC]hD]hE]hF]hI]uhKKÒhM]r hXX 30000r …r }r
(h5j h6j ubaubah?jw ubjj )r }r (h5U hA}r
(hC]hD]hE]hF]hI]uh6jû hM]r hy)r }r (h5X" heap memory error after 45 minutesr h6j h=h>h?hˆhA}r (hC]hD]hE]hF]hI]uhKKÒhM]r hXX" heap memory error after 45 minutesr …r }r (h5j h6j ubaubah?jw ubeh?j„ ubeh?Utbodyr ubeh?Utgroupr ubaubjñ )r }r (h5XR TODO: provide statistics for deserialization times for various size resource mapsh6j8 h=h>h?jô hA}r (j¼ j½ hF]hE]hC]hD]hI]uhKK×hLhhM]r hXXR TODO: provide statistics for deserialization times for various size resource mapsr …r }r (h5U h6j ubaubeubeubh7)r }r! (h5U h6h;h=h>h?h@hA}r" (hC]hD]hE]hF]r# hþahI]r$ hauhKKÙhLhhM]r% (hO)r& }r' (h5j h6j h=h>h?hShA}r( (hF]hE]hC]hD]hI]hUhýuhKKÙhLhhM]r) hXX Resource map validationr* …r+ }r, (h5j h6j& ubaubhy)r- }r. (h5XX Because DataONE indexing relies on the integrity of the resource maps it receives
from the member nodes, each resource map will be validated against the set of
constraints enumerated above. Resource maps that do not validate will fail
synchronization, and the exception returned to the member node via the method
MN_Read.syncrhonizationFailed.r/ h6j h=h>h?hˆhA}r0 (hC]hD]hE]hF]hI]uhKKÛhLhhM]r1 hXXX Because DataONE indexing relies on the integrity of the resource maps it receives
from the member nodes, each resource map will be validated against the set of
constraints enumerated above. Resource maps that do not validate will fail
synchronization, and the exception returned to the member node via the method
MN_Read.syncrhonizationFailed.r2 …r3 }r4 (h5j/ h6j- ubaubeubh7)r5 }r6 (h5U h6h;h=h>h?h@hA}r7 (hC]hD]hE]hF]r8 j ahI]r9 hauhKKåhLhhM]r: (hO)r; }r< (h5j h6j5 h=h>h?hShA}r= (hF]hE]hC]hD]hI]hUj uhKKåhLhhM]r> hXX Background Discussionr? …r@ }rA (h5j h6j; ubaubh7)rB }rC (h5U h6j5 h=h>h?h@hA}rD (hC]hD]hE]hF]rE j( ahI]rF hauhKKèhLhhM]rG (hO)rH }rI (h5j- h6jB h=h>h?hShA}rJ (hF]hE]hC]hD]hI]hUj' uhKKèhLhhM]rK hXX OverviewrL …rM }rN (h5j- h6jH ubaubhy)rO }rP (h5Xã Data, in the context of DataONE, is a discrete unit of digital content that is
expected to represent information obtained from some experiment or scientific
study. The :term:`data` are accompanied by :term:`science metadata`, which is a
separate unit of digital content that describes properties of the data. Each
unit of science data or science metadata is accompanied by :term:`system
metadata` which describes the digital object (e.g. hash, time stamps, ownership,
relationships).h6jB h=h>h?hˆhA}rQ (hC]hD]hE]hF]hI]uhKKêhLhhM]rR (hXX¨ Data, in the context of DataONE, is a discrete unit of digital content that is
expected to represent information obtained from some experiment or scientific
study. The rS …rT }rU (h5X¨ Data, in the context of DataONE, is a discrete unit of digital content that is
expected to represent information obtained from some experiment or scientific
study. The h6jO ubj. )rV }rW (h5X :term:`data`rX h6jO h=h>h?j2 hA}rY (UreftypeX termj4 ˆj5 X dataU refdomainX stdrZ hF]hE]U refexplicit‰hC]hD]hI]j7 j8 uhKKêhM]r[ j: )r\ }r] (h5jX hA}r^ (hC]hD]r_ (j? jZ X std-termr` ehE]hF]hI]uh6jV hM]ra hXX datarb …rc }rd (h5U h6j\ ubah?jE ubaubhXX are accompanied by re …rf }rg (h5X are accompanied by h6jO ubj. )rh }ri (h5X :term:`science metadata`rj h6jO h=h>h?j2 hA}rk (UreftypeX termj4 ˆj5 X science metadataU refdomainX stdrl hF]hE]U refexplicit‰hC]hD]hI]j7 j8 uhKKêhM]rm j: )rn }ro (h5jj hA}rp (hC]hD]rq (j? jl X std-termrr ehE]hF]hI]uh6jh hM]rs hXX science metadatart …ru }rv (h5U h6jn ubah?jE ubaubhXX• , which is a
separate unit of digital content that describes properties of the data. Each
unit of science data or science metadata is accompanied by rw …rx }ry (h5X• , which is a
separate unit of digital content that describes properties of the data. Each
unit of science data or science metadata is accompanied by h6jO ubj. )rz }r{ (h5X :term:`system
metadata`r| h6jO h=h>h?j2 hA}r} (UreftypeX termj4 ˆj5 X system metadataU refdomainX stdr~ hF]hE]U refexplicit‰hC]hD]hI]j7 j8 uhKKêhM]r j: )r€ }r (h5j| hA}r‚ (hC]hD]rƒ (j? j~ X std-termr„ ehE]hF]hI]uh6jz hM]r… hXX system
metadatar† …r‡ }rˆ (h5U h6j€ ubah?jE ubaubhXXW which describes the digital object (e.g. hash, time stamps, ownership,
relationships).r‰ …rŠ }r‹ (h5XW which describes the digital object (e.g. hash, time stamps, ownership,
relationships).h6jO ubeubhy)rΠ}r (h5XH In DataONE, data are treated as opaque sets of bytes and, along with their
associated science metadata, are stored on :term:`Member Node`\s (MN). A copy
of the science metadata is held by the :term:`Coordinating Node`\s (CN) and is
parsed to extract attributes to assist the discovery process (i.e. users
searching for content).h6jB h=h>h?hˆhA}rŽ (hC]hD]hE]hF]hI]uhKKòhLhhM]r (hXXv In DataONE, data are treated as opaque sets of bytes and, along with their
associated science metadata, are stored on r …r‘ }r’ (h5Xv In DataONE, data are treated as opaque sets of bytes and, along with their
associated science metadata, are stored on h6jŒ ubj. )r“ }r” (h5X :term:`Member Node`r• h6jŒ h=h>h?j2 hA}r– (UreftypeX termj4 ˆj5 X member nodeU refdomainX stdr— hF]hE]U refexplicit‰hC]hD]hI]j7 j8 uhKKòhM]r˜ j: )r™ }rš (h5j• hA}r› (hC]hD]rœ (j? j— X std-termr ehE]hF]hI]uh6j“ hM]rž hXX Member NoderŸ …r }r¡ (h5U h6j™ ubah?jE ubaubhXX6 s (MN). A copy
of the science metadata is held by the r¢ …r£ }r¤ (h5X7 \s (MN). A copy
of the science metadata is held by the h6jŒ ubj. )r¥ }r¦ (h5X :term:`Coordinating Node`r§ h6jŒ h=h>h?j2 hA}r¨ (UreftypeX termj4 ˆj5 X coordinating nodeU refdomainX stdr© hF]hE]U refexplicit‰hC]hD]hI]j7 j8 uhKKòhM]rª j: )r« }r¬ (h5j§ hA}r (hC]hD]r® (j? j© X std-termr¯ ehE]hF]hI]uh6j¥ hM]r° hXX Coordinating Noder± …r² }r³ (h5U h6j« ubah?jE ubaubhXXn s (CN) and is
parsed to extract attributes to assist the discovery process (i.e. users
searching for content).r´ …rµ }r¶ (h5Xo \s (CN) and is
parsed to extract attributes to assist the discovery process (i.e. users
searching for content).h6jŒ ubeubhy)r· }r¸ (h5Xù The opacity of data in DataONE is likely to change in the future to enable
processing of the data with operations such as translation (e.g. for format
migration), extraction (e.g. for rendering), and merging (e.g. to combine
multiple instances of data that are expressed in different formats). Such
operations rely upon a stable, accessible framework supporting reliable data
access, and so are targeted after the initial requirements of DataONE are met
and the core infrastructure is demonstrably robust.r¹ h6jB h=h>h?hˆhA}rº (hC]hD]hE]hF]hI]uhKKøhLhhM]r» hXXù The opacity of data in DataONE is likely to change in the future to enable
processing of the data with operations such as translation (e.g. for format
migration), extraction (e.g. for rendering), and merging (e.g. to combine
multiple instances of data that are expressed in different formats). Such
operations rely upon a stable, accessible framework supporting reliable data
access, and so are targeted after the initial requirements of DataONE are met
and the core infrastructure is demonstrably robust.r¼ …r½ }r¾ (h5j¹ h6j· ubaubhy)r¿ }rÀ (h5Xœ In order to properly interpret, preserve, and utilize a data object, users and
their software agents need access to the science metadata describing the data
objects. A :term:`data package` in DataONE provides the conceptual
relationships among the various components of the package that describe which
:term:`data` objects are described by which :term:`science metadata`
documents, and the role in that description that they play. This model
accommodates use of well-established existing metadata specifications such as
EML, BDP, and ISO 19115 for documenting science metadata while recognizing that
some of these do not readily incorporate mechanisms for consistent linkages to
and inclusion of data objects. The data package concept also provides a
consistent mechanism to define one or more serialized representations of a
package that can be used to transport the components of a data package from
one system to another.h6jB h=h>h?hˆhA}rÁ (hC]hD]hE]hF]hI]uhKM hLhhM]r (hXX¨ In order to properly interpret, preserve, and utilize a data object, users and
their software agents need access to the science metadata describing the data
objects. A rà …rÄ }rÅ (h5X¨ In order to properly interpret, preserve, and utilize a data object, users and
their software agents need access to the science metadata describing the data
objects. A h6j¿ ubj. )rÆ }rÇ (h5X :term:`data package`rÈ h6j¿ h=h>h?j2 hA}rÉ (UreftypeX termj4 ˆj5 X data packageU refdomainX stdrÊ hF]hE]U refexplicit‰hC]hD]hI]j7 j8 uhKM hM]rË j: )rÌ }rÍ (h5jÈ hA}rÎ (hC]hD]rÏ (j? jÊ X std-termrÐ ehE]hF]hI]uh6jÆ hM]rÑ hXX data packagerÒ …rÓ }rÔ (h5U h6jÌ ubah?jE ubaubhXXr in DataONE provides the conceptual
relationships among the various components of the package that describe which
rÕ …rÖ }r× (h5Xr in DataONE provides the conceptual
relationships among the various components of the package that describe which
h6j¿ ubj. )rØ }rÙ (h5X :term:`data`rÚ h6j¿ h=h>h?j2 hA}rÛ (UreftypeX termj4 ˆj5 X dataU refdomainX stdrÜ hF]hE]U refexplicit‰hC]hD]hI]j7 j8 uhKM hM]rÝ j: )rÞ }rß (h5jÚ hA}rà (hC]hD]rá (j? jÜ X std-termrâ ehE]hF]hI]uh6jØ hM]rã hXX datarä …rå }ræ (h5U h6jÞ ubah?jE ubaubhXX objects are described by which rç …rè }ré (h5X objects are described by which h6j¿ ubj. )rê }rë (h5X :term:`science metadata`rì h6j¿ h=h>h?j2 hA}rí (UreftypeX termj4 ˆj5 X science metadataU refdomainX stdrî hF]hE]U refexplicit‰hC]hD]hI]j7 j8 uhKM hM]rï j: )rð }rñ (h5jì hA}rò (hC]hD]ró (j? jî X std-termrô ehE]hF]hI]uh6jê hM]rõ hXX science metadatarö …r÷ }rø (h5U h6jð ubah?jE ubaubhXX*
documents, and the role in that description that they play. This model
accommodates use of well-established existing metadata specifications such as
EML, BDP, and ISO 19115 for documenting science metadata while recognizing that
some of these do not readily incorporate mechanisms for consistent linkages to
and inclusion of data objects. The data package concept also provides a
consistent mechanism to define one or more serialized representations of a
package that can be used to transport the components of a data package from
one system to another.rù …rú }rû (h5X*
documents, and the role in that description that they play. This model
accommodates use of well-established existing metadata specifications such as
EML, BDP, and ISO 19115 for documenting science metadata while recognizing that
some of these do not readily incorporate mechanisms for consistent linkages to
and inclusion of data objects. The data package concept also provides a
consistent mechanism to define one or more serialized representations of a
package that can be used to transport the components of a data package from
one system to another.h6j¿ ubeubcdocutils.nodes
note
rü )rý }rþ (h5XÆ The DataONE :doc:`SystemMetadata` format currently includes descriptions of
some of the relationships that would be within scope of the definition of a
Data Package. Specifically, the System Metadata fields
:attr:`SystemMetadata.obsoletes` and :attr:`SystemMetadata.obsoletedBy`
describe the relationship between two objects where one replaces the other
from a scientific utility perspective (such as an error-corrected version of
an existing data file).h6jB h=h>h?Unoterÿ hA}r (hC]hD]hE]hF]hI]uhKNhLhhM]r hy)r }r (h5XÆ The DataONE :doc:`SystemMetadata` format currently includes descriptions of
some of the relationships that would be within scope of the definition of a
Data Package. Specifically, the System Metadata fields
:attr:`SystemMetadata.obsoletes` and :attr:`SystemMetadata.obsoletedBy`
describe the relationship between two objects where one replaces the other
from a scientific utility perspective (such as an error-corrected version of
an existing data file).h6jý h=h>h?hˆhA}r (hC]hD]hE]hF]hI]uhKMhM]r (hXX The DataONE r …r }r (h5X The DataONE h6j ubj. )r }r
(h5X :doc:`SystemMetadata`r h6j h=h>h?j2 hA}r (UreftypeX docr
j4 ˆj5 X SystemMetadataU refdomainU hF]hE]U refexplicit‰hC]hD]hI]j7 j8 uhKMhM]r j: )r }r (h5j hA}r (hC]hD]r (j? j
ehE]hF]hI]uh6j hM]r hXX SystemMetadatar …r }r (h5U h6j ubah?jE ubaubhXX® format currently includes descriptions of
some of the relationships that would be within scope of the definition of a
Data Package. Specifically, the System Metadata fields
r …r }r (h5X® format currently includes descriptions of
some of the relationships that would be within scope of the definition of a
Data Package. Specifically, the System Metadata fields
h6j ubj. )r }r (h5X :attr:`SystemMetadata.obsoletes`r h6j h=h>h?j2 hA}r (UreftypeX attrj4 ‰j5 X SystemMetadata.obsoletesU refdomainX pyr hF]hE]U refexplicit‰hC]hD]hI]j7 j8 Upy:classr NU py:moduler NuhKMhM]r! j )r" }r# (h5j hA}r$ (hC]hD]r% (j? j X py-attrr& ehE]hF]hI]uh6j hM]r' hXX SystemMetadata.obsoletesr( …r) }r* (h5U h6j" ubah?j( ubaubhXX and r+ …r, }r- (h5X and h6j ubj. )r. }r/ (h5X" :attr:`SystemMetadata.obsoletedBy`r0 h6j h=h>h?j2 hA}r1 (UreftypeX attrj4 ‰j5 X SystemMetadata.obsoletedByU refdomainX pyr2 hF]hE]U refexplicit‰hC]hD]hI]j7 j8 j Nj NuhKMhM]r3 j )r4 }r5 (h5j0 hA}r6 (hC]hD]r7 (j? j2 X py-attrr8 ehE]hF]hI]uh6j. hM]r9 hXX SystemMetadata.obsoletedByr: …r; }r< (h5U h6j4 ubah?j( ubaubhXX°
describe the relationship between two objects where one replaces the other
from a scientific utility perspective (such as an error-corrected version of
an existing data file).r= …r> }r? (h5X°
describe the relationship between two objects where one replaces the other
from a scientific utility perspective (such as an error-corrected version of
an existing data file).h6j ubeubaubhy)r@ }rA (h5XÄ A *data package* will be represented in DataONE as a unique, additional class
of object with its own unique identifier different from the identifiers of its
components. Each of these data packages in DataONE will be represented by an
OAI-ORE Resource Map that contains an Aggregation indicating relationships
among the components of the package. The BagIt specification will be used to
optionally provide these components as a single serialized object.h6jB h=h>h?hˆhA}rB (hC]hD]hE]hF]hI]uhKMhLhhM]rC (hXX A rD …rE }rF (h5X A h6j@ ubcdocutils.nodes
emphasis
rG )rH }rI (h5X *data package*hA}rJ (hC]hD]hE]hF]hI]uh6j@ hM]rK hXX data packagerL …rM }rN (h5U h6jH ubah?UemphasisrO ubhXX´ will be represented in DataONE as a unique, additional class
of object with its own unique identifier different from the identifiers of its
components. Each of these data packages in DataONE will be represented by an
OAI-ORE Resource Map that contains an Aggregation indicating relationships
among the components of the package. The BagIt specification will be used to
optionally provide these components as a single serialized object.rP …rQ }rR (h5X´ will be represented in DataONE as a unique, additional class
of object with its own unique identifier different from the identifiers of its
components. Each of these data packages in DataONE will be represented by an
OAI-ORE Resource Map that contains an Aggregation indicating relationships
among the components of the package. The BagIt specification will be used to
optionally provide these components as a single serialized object.h6j@ ubeubeubh7)rS }rT (h5U h6j5 h=h>h?h@hA}rU (hC]hD]hE]hF]rV j; ahI]rW hauhKM!hLhhM]rX (hO)rY }rZ (h5j@ h6jS h=h>h?hShA}r[ (hF]hE]hC]hD]hI]hUj: uhKM!hLhhM]r\ hXX User storiesr] …r^ }r_ (h5j@ h6jY ubaubhn)r` }ra (h5U h6jS h=h>h?hqhA}rb (Ubulletrc X *hF]hE]hC]hD]hI]uhKM#hLhhM]rd (ht)re }rf (h5X® A user agent can download a description of a data package that provides the
DataONE identifiers for all science metadata and data object components
associated by the package
h6j` h=h>h?h hA}rg (hC]hD]hE]hF]hI]uhKNhLhhM]rh hy)ri }rj (h5X A user agent can download a description of a data package that provides the
DataONE identifiers for all science metadata and data object components
associated by the packagerk h6je h=h>h?hˆhA}rl (hC]hD]hE]hF]hI]uhKM#hM]rm hXX A user agent can download a description of a data package that provides the
DataONE identifiers for all science metadata and data object components
associated by the packagern …ro }rp (h5jk h6ji ubaubaubht)rq }rr (h5X A user agent can download a serialized version of a data package that
includes the science metadata and either the data bytes or references to the
data bytes via DataONE identifiers directly in the serialized version of the
package, and the system metadata for each of these objects.
h6j` h=h>h?h hA}rs (hC]hD]hE]hF]hI]uhKNhLhhM]rt hy)ru }rv (h5X A user agent can download a serialized version of a data package that
includes the science metadata and either the data bytes or references to the
data bytes via DataONE identifiers directly in the serialized version of the
package, and the system metadata for each of these objects.rw h6jq h=h>h?hˆhA}rx (hC]hD]hE]hF]hI]uhKM'hM]ry hXX A user agent can download a serialized version of a data package that
includes the science metadata and either the data bytes or references to the
data bytes via DataONE identifiers directly in the serialized version of the
package, and the system metadata for each of these objects.rz …r{ }r| (h5jw h6ju ubaubaubht)r} }r~ (h5XÃ The serialized form allows for the relationships between the various
components to be properly maintained (e.g., which system metadata documents
describe which data and science metadata objects)
h6j` h=h>h?h hA}r (hC]hD]hE]hF]hI]uhKNhLhhM]r€ hy)r }r‚ (h5XÂ The serialized form allows for the relationships between the various
components to be properly maintained (e.g., which system metadata documents
describe which data and science metadata objects)rƒ h6j} h=h>h?hˆhA}r„ (hC]hD]hE]hF]hI]uhKM,hM]r… hXXÂ The serialized form allows for the relationships between the various
components to be properly maintained (e.g., which system metadata documents
describe which data and science metadata objects)r† …r‡ }rˆ (h5jƒ h6j ubaubaubht)r‰ }rŠ (h5X. Data packages can be versioned, such that individual components of a package
can be replaced with new versions of those objects, new objects can be
added, existing objects can be removed, and the whole package is versioned
to differentiate it from earlier versions that contained different
components.
h6j` h=h>h?h hA}r‹ (hC]hD]hE]hF]hI]uhKNhLhhM]rŒ hy)r }rŽ (h5X- Data packages can be versioned, such that individual components of a package
can be replaced with new versions of those objects, new objects can be
added, existing objects can be removed, and the whole package is versioned
to differentiate it from earlier versions that contained different
components.r h6j‰ h=h>h?hˆhA}r (hC]hD]hE]hF]hI]uhKM0hM]r‘ hXX- Data packages can be versioned, such that individual components of a package
can be replaced with new versions of those objects, new objects can be
added, existing objects can be removed, and the whole package is versioned
to differentiate it from earlier versions that contained different
components.r’ …r“ }r” (h5j h6j ubaubaubht)r• }r– (h5X` A user agent can easily locate and inspect the science metadata associated
with any data object
h6j` h=h>h?h hA}r— (hC]hD]hE]hF]hI]uhKNhLhhM]r˜ hy)r™ }rš (h5X_ A user agent can easily locate and inspect the science metadata associated
with any data objectr› h6j• h=h>h?hˆhA}rœ (hC]hD]hE]hF]hI]uhKM6hM]r hXX_ A user agent can easily locate and inspect the science metadata associated
with any data objectrž …rŸ }r (h5j› h6j™ ubaubaubht)r¡ }r¢ (h5Xf A user agent can easily locate and access the data objects associated with a
science metadata object.
h6j` h=h>h?h hA}r£ (hC]hD]hE]hF]hI]uhKNhLhhM]r¤ hy)r¥ }r¦ (h5Xe A user agent can easily locate and access the data objects associated with a
science metadata object.r§ h6j¡ h=h>h?hˆhA}r¨ (hC]hD]hE]hF]hI]uhKM9hM]r© hXXe A user agent can easily locate and access the data objects associated with a
science metadata object.rª …r« }r¬ (h5j§ h6j¥ ubaubaubht)r }r® (h5XÈ Data object formats should be well-described in science metadata, ideally to
sufficient detail to allow software agents to parse and load the data and
science metadata objects for additional processing, querying, and
manipulation The data objects supported should minimally include:
* Data Tables in CSV and other fixed and delimited text formats
* NetCDF files
* Raster images in various formats
* Vector data in specific, community-accepted formats
h6j` h=h>h?h hA}r¯ (hC]hD]hE]hF]hI]uhKNhLhhM]r° (hy)r± }r² (h5X Data object formats should be well-described in science metadata, ideally to
sufficient detail to allow software agents to parse and load the data and
science metadata objects for additional processing, querying, and
manipulation The data objects supported should minimally include:r³ h6j h=h>h?hˆhA}r´ (hC]hD]hE]hF]hI]uhKM<hM]rµ hXX Data object formats should be well-described in science metadata, ideally to
sufficient detail to allow software agents to parse and load the data and
science metadata objects for additional processing, querying, and
manipulation The data objects supported should minimally include:r¶ …r· }r¸ (h5j³ h6j± ubaubcdocutils.nodes
block_quote
r¹ )rº }r» (h5U hA}r¼ (hC]hD]hE]hF]hI]uh6j hM]r½ hn)r¾ }r¿ (h5U hA}rÀ (jc X *hF]hE]hC]hD]hI]uh6jº hM]rÁ (ht)r }rà (h5X= Data Tables in CSV and other fixed and delimited text formatsrÄ hA}rÅ (hC]hD]hE]hF]hI]uh6j¾ hM]rÆ hy)rÇ }rÈ (h5jÄ h6j h=h>h?hˆhA}rÉ (hC]hD]hE]hF]hI]uhKMAhM]rÊ hXX= Data Tables in CSV and other fixed and delimited text formatsrË …rÌ }rÍ (h5jÄ h6jÇ ubaubah?h ubht)rÎ }rÏ (h5X NetCDF filesrÐ hA}rÑ (hC]hD]hE]hF]hI]uh6j¾ hM]rÒ hy)rÓ }rÔ (h5jÐ h6jÎ h=h>h?hˆhA}rÕ (hC]hD]hE]hF]hI]uhKMBhM]rÖ hXX NetCDF filesr× …rØ }rÙ (h5jÐ h6jÓ ubaubah?h ubht)rÚ }rÛ (h5X Raster images in various formatsrÜ hA}rÝ (hC]hD]hE]hF]hI]uh6j¾ hM]rÞ hy)rß }rà (h5jÜ h6jÚ h=h>h?hˆhA}rá (hC]hD]hE]hF]hI]uhKMChM]râ hXX Raster images in various formatsrã …rä }rå (h5jÜ h6jß ubaubah?h ubht)ræ }rç (h5X4 Vector data in specific, community-accepted formats
hA}rè (hC]hD]hE]hF]hI]uh6j¾ hM]ré hy)rê }rë (h5X3 Vector data in specific, community-accepted formatsrì h6jæ h=h>h?hˆhA}rí (hC]hD]hE]hF]hI]uhKMDhM]rî hXX3 Vector data in specific, community-accepted formatsrï …rð }rñ (h5jì h6jê ubaubah?h ubeh?hqubah?U block_quoterò ubeubht)ró }rô (h5X¬ A scientist can load all of the supported data objects from a data package
found in a metadata search without directly knowing the identifiers for
individual data objects.
h6j` h=h>h?h hA}rõ (hC]hD]hE]hF]hI]uhKNhLhhM]rö hy)r÷ }rø (h5X« A scientist can load all of the supported data objects from a data package
found in a metadata search without directly knowing the identifiers for
individual data objects.rù h6jó h=h>h?hˆhA}rú (hC]hD]hE]hF]hI]uhKMFhM]rû hXX« A scientist can load all of the supported data objects from a data package
found in a metadata search without directly knowing the identifiers for
individual data objects.rü …rý }rþ (h5jù h6j÷ ubaubaubht)rÿ }r (h5X³ A scientist can upload a new data object and associated science metadata in
order to create a new data package, or to extend or create a new version of
an existing data package
h6j` h=h>h?h hA}r (hC]hD]hE]hF]hI]uhKNhLhhM]r hy)r }r (h5X° A scientist can upload a new data object and associated science metadata in
order to create a new data package, or to extend or create a new version of
an existing data packager h6jÿ h=h>h?hˆhA}r (hC]hD]hE]hF]hI]uhKMJhM]r hXX° A scientist can upload a new data object and associated science metadata in
order to create a new data package, or to extend or create a new version of
an existing data packager …r }r
(h5j h6j ubaubaubeubeubh7)r }r (h5U h6j5 h=h>h?h@hA}r
(hC]hD]hE]hF]r jN ahI]r h$auhKMQhLhhM]r (hO)r }r (h5jS h6j h=h>h?hShA}r (hF]hE]hC]hD]hI]hUjM uhKMQhLhhM]r hXX* Package Content Associations Using OAI-OREr …r }r (h5jS h6j ubaubhy)r }r (h5Xn The Open Archives Initiative's Object Reuse and Exchange (OAI-ORE)
[Lagoze-2008]_ "defines standards for the description and exchange of
aggregations of Web resources". OAI-ORE provides a mechanism for describing
aggregations of distinct resources on the web by using their respective URIs
to provide linkages in an RDF model. Each Aggregation is given its own
distinct identifying URI, and ORE recommends the use of `Cool URIs`_ for the
Semantic Web [Sauermann_Cyganiak-2008]_ as a mechanism to redirect from the
Aggregation URI to a specific representation of the Aggregation, called a
Resource Map, that can be represented in one of several different
serializations such as RDF/XML, turtle, and Atom XML. Because relationships
among resources are provided using RDF predicates, there is tremendous
flexibility in the type of relationships that can be defined. ORE provides
specific predicates that define relationship types between the Aggregation and
a Resource Map ('ore:describes') and between the Aggregation and the Resources
that it aggregates ('ore:aggregates'). These concepts relate closely to
similar concepts in DataONE.h6j h=h>h?hˆhA}r (hC]hD]hE]hF]hI]uhKMShLhhM]r (hXXC The Open Archives Initiative's Object Reuse and Exchange (OAI-ORE)
r …r }r (h5XC The Open Archives Initiative's Object Reuse and Exchange (OAI-ORE)
h6j ubj. )r }r (h5X Lagoze-2008r! h6j h=h>h?j2 hA}r" (UreftypeUcitationr# UrefwarnˆU reftargetj! U refdomainUstdr$ hF]r% Uid1r& ahE]hC]hD]hI]uhKMShLhhM]r' hXX
[Lagoze-2008]r( …r) }r* (h5U h6j ubaubhXXP "defines standards for the description and exchange of
aggregations of Web resources". OAI-ORE provides a mechanism for describing
aggregations of distinct resources on the web by using their respective URIs
to provide linkages in an RDF model. Each Aggregation is given its own
distinct identifying URI, and ORE recommends the use of r+ …r, }r- (h5XP "defines standards for the description and exchange of
aggregations of Web resources". OAI-ORE provides a mechanism for describing
aggregations of distinct resources on the web by using their respective URIs
to provide linkages in an RDF model. Each Aggregation is given its own
distinct identifying URI, and ORE recommends the use of h6j ubh~)r. }r/ (h5X `Cool URIs`_jˆ Kh6j h?h‡hA}r0 (UnameX Cool URIsjŠ X http://www.w3.org/TR/cooluris/r1 hF]hE]hC]hD]hI]uhM]r2 hXX Cool URIsr3 …r4 }r5 (h5U h6j. ubaubhXX for the
Semantic Web r6 …r7 }r8 (h5X for the
Semantic Web h6j ubj. )r9 }r: (h5X Sauermann_Cyganiak-2008r; h6j h=h>h?j2 hA}r< (Ureftypej# UrefwarnˆU reftargetj; U refdomainj$ hF]r= Uid2r> ahE]hC]hD]hI]uhKMShLhhM]r? hXX [Sauermann_Cyganiak-2008]r@ …rA }rB (h5U h6j9 ubaubhXX‘ as a mechanism to redirect from the
Aggregation URI to a specific representation of the Aggregation, called a
Resource Map, that can be represented in one of several different
serializations such as RDF/XML, turtle, and Atom XML. Because relationships
among resources are provided using RDF predicates, there is tremendous
flexibility in the type of relationships that can be defined. ORE provides
specific predicates that define relationship types between the Aggregation and
a Resource Map ('ore:describes') and between the Aggregation and the Resources
that it aggregates ('ore:aggregates'). These concepts relate closely to
similar concepts in DataONE.rC …rD }rE (h5X‘ as a mechanism to redirect from the
Aggregation URI to a specific representation of the Aggregation, called a
Resource Map, that can be represented in one of several different
serializations such as RDF/XML, turtle, and Atom XML. Because relationships
among resources are provided using RDF predicates, there is tremendous
flexibility in the type of relationships that can be defined. ORE provides
specific predicates that define relationship types between the Aggregation and
a Resource Map ('ore:describes') and between the Aggregation and the Resources
that it aggregates ('ore:aggregates'). These concepts relate closely to
similar concepts in DataONE.h6j ubeubcdocutils.nodes
definition_list
rF )rG }rH (h5U h6j h=Nh?Udefinition_listrI hA}rJ (hC]hD]hE]hF]hI]uhKNhLhhM]rK cdocutils.nodes
definition_list_item
rL )rM }rN (h5X Beneficial features
* Uses traditional web URIs as global identifiers
* Compatible with the Linked Data philosophy
* Supports arbitrary graphs of resources and aggregations
h6jG h=h>h?Udefinition_list_itemrO hA}rP (hC]hD]hE]hF]hI]uhKMghM]rQ (cdocutils.nodes
term
rR )rS }rT (h5X Beneficial featuresrU h6jM h=h>h?UtermrV hA}rW (hC]hD]hE]hF]hI]uhKMghM]rX hXX Beneficial featuresrY …rZ }r[ (h5jU h6jS ubaubcdocutils.nodes
definition
r\ )r] }r^ (h5U hA}r_ (hC]hD]hE]hF]hI]uh6jM hM]r` hn)ra }rb (h5U hA}rc (jc X *hF]hE]hC]hD]hI]uh6j] hM]rd (ht)re }rf (h5X/ Uses traditional web URIs as global identifiersrg hA}rh (hC]hD]hE]hF]hI]uh6ja hM]ri hy)rj }rk (h5jg h6je h=h>h?hˆhA}rl (hC]hD]hE]hF]hI]uhKMehM]rm hXX/ Uses traditional web URIs as global identifiersrn …ro }rp (h5jg h6jj ubaubah?h ubht)rq }rr (h5X* Compatible with the Linked Data philosophyrs hA}rt (hC]hD]hE]hF]hI]uh6ja hM]ru hy)rv }rw (h5js h6jq h=h>h?hˆhA}rx (hC]hD]hE]hF]hI]uhKMfhM]ry hXX* Compatible with the Linked Data philosophyrz …r{ }r| (h5js h6jv ubaubah?h ubht)r} }r~ (h5X8 Supports arbitrary graphs of resources and aggregations
hA}r (hC]hD]hE]hF]hI]uh6ja hM]r€ hy)r }r‚ (h5X7 Supports arbitrary graphs of resources and aggregationsrƒ h6j} h=h>h?hˆhA}r„ (hC]hD]hE]hF]hI]uhKMghM]r… hXX7 Supports arbitrary graphs of resources and aggregationsr† …r‡ }rˆ (h5jƒ h6j ubaubah?h ubeh?hqubah?U
definitionr‰ ubeubaubeubh7)rŠ }r‹ (h5U h6j5 h=h>h?h@hA}rŒ (hC]hD]hE]hF]r ja ahI]rŽ h'auhKMjhLhhM]r (hO)r }r‘ (h5jf h6jŠ h=h>h?hShA}r’ (hF]hE]hC]hD]hI]hUj` uhKMjhLhhM]r“ hXX Issues and Resolutionr” …r• }r– (h5jf h6j ubaubjF )r— }r˜ (h5U h6jŠ h=Nh?jI hA}r™ (hC]hD]hE]hF]hI]uhKNhLhhM]rš (jL )r› }rœ (h5X™ Issues
* Does not provide a direct serialization of the Aggregation with the bytes
inline
* No data model for internal structure of enclosed resources
h6j— h=h>h?jO hA}r (hC]hD]hE]hF]hI]uhKMohM]rž (jR )rŸ }r (h5X Issuesr¡ h6j› h=h>h?jV hA}r¢ (hC]hD]hE]hF]hI]uhKMohM]r£ hXX Issuesr¤ …r¥ }r¦ (h5j¡ h6jŸ ubaubj\ )r§ }r¨ (h5U hA}r© (hC]hD]hE]hF]hI]uh6j› hM]rª hn)r« }r¬ (h5U hA}r (jc X *hF]hE]hC]hD]hI]uh6j§ hM]r® (ht)r¯ }r° (h5XP Does not provide a direct serialization of the Aggregation with the bytes
inlinehA}r± (hC]hD]hE]hF]hI]uh6j« hM]r² hy)r³ }r´ (h5XP Does not provide a direct serialization of the Aggregation with the bytes
inlinerµ h6j¯ h=h>h?hˆhA}r¶ (hC]hD]hE]hF]hI]uhKMmhM]r· hXXP Does not provide a direct serialization of the Aggregation with the bytes
inliner¸ …r¹ }rº (h5jµ h6j³ ubaubah?h ubht)r» }r¼ (h5X; No data model for internal structure of enclosed resources
hA}r½ (hC]hD]hE]hF]hI]uh6j« hM]r¾ hy)r¿ }rÀ (h5X: No data model for internal structure of enclosed resourcesrÁ h6j» h=h>h?hˆhA}r (hC]hD]hE]hF]hI]uhKMohM]rà hXX: No data model for internal structure of enclosed resourcesrÄ …rÅ }rÆ (h5jÁ h6j¿ ubaubah?h ubeh?hqubah?j‰ ubeubjL )rÇ }rÈ (h5XJ Questions
* Do URIs really have to be used, or can other resource identifiers such as
DOIs be used?
* Is there a more elegant way to link the Aggregation to a Resource Map than
using the `Cool URIs`_ approach of redirection, especially when multiple
physical copies of a Resource might exist at multiple physical locations?
h6j— h=h>h?jO hA}rÉ (hC]hD]hE]hF]hI]uhKMvhLhhM]rÊ (jR )rË }rÌ (h5X QuestionsrÍ h6jÇ h=h>h?jV hA}rÎ (hC]hD]hE]hF]hI]uhKMvhM]rÏ hXX QuestionsrÐ …rÑ }rÒ (h5jÍ h6jË ubaubj\ )rÓ }rÔ (h5U hA}rÕ (hC]hD]hE]hF]hI]uh6jÇ hM]rÖ hn)r× }rØ (h5U hA}rÙ (jc X *hF]hE]hC]hD]hI]uh6jÓ hM]rÚ (ht)rÛ }rÜ (h5XW Do URIs really have to be used, or can other resource identifiers such as
DOIs be used?hA}rÝ (hC]hD]hE]hF]hI]uh6j× hM]rÞ hy)rß }rà (h5XW Do URIs really have to be used, or can other resource identifiers such as
DOIs be used?rá h6jÛ h=h>h?hˆhA}râ (hC]hD]hE]hF]hI]uhKMrhM]rã hXXW Do URIs really have to be used, or can other resource identifiers such as
DOIs be used?rä …rå }ræ (h5já h6jß ubaubah?h ubht)rç }rè (h5XÞ Is there a more elegant way to link the Aggregation to a Resource Map than
using the `Cool URIs`_ approach of redirection, especially when multiple
physical copies of a Resource might exist at multiple physical locations?
hA}ré (hC]hD]hE]hF]hI]uh6j× hM]rê hy)rë }rì (h5XÝ Is there a more elegant way to link the Aggregation to a Resource Map than
using the `Cool URIs`_ approach of redirection, especially when multiple
physical copies of a Resource might exist at multiple physical locations?h6jç h=h>h?hˆhA}rí (hC]hD]hE]hF]hI]uhKMthM]rî (hXXU Is there a more elegant way to link the Aggregation to a Resource Map than
using the rï …rð }rñ (h5XU Is there a more elegant way to link the Aggregation to a Resource Map than
using the h6jë ubh~)rò }ró (h5X `Cool URIs`_jˆ Kh6jë h?h‡hA}rô (UnameX Cool URIsjŠ j1 hF]hE]hC]hD]hI]uhM]rõ hXX Cool URIsrö …r÷ }rø (h5U h6jò ubaubhXX| approach of redirection, especially when multiple
physical copies of a Resource might exist at multiple physical locations?rù …rú }rû (h5X| approach of redirection, especially when multiple
physical copies of a Resource might exist at multiple physical locations?h6jë ubeubah?h ubeh?hqubah?j‰ ubeubeubcdocutils.nodes
figure
rü )rý }rþ (h5U h6jŠ h=h>h?Ufigurerÿ hA}r (hC]hD]hE]hF]r Uid7r ahI]uhKMzhLhhM]r (já )r }r (h5X† .. figure:: http://www.openarchives.org/ore/1.0/datamodel-images/ore_uml.png
**Figure 1.** General model for an OAI-ORE document.
h6jý h=h>h?jä hA}r (UuriX@ http://www.openarchives.org/ore/1.0/datamodel-images/ore_uml.pngr hF]hE]hC]hD]jç }r U?j shI]uhKMzhM]ubcdocutils.nodes
caption
r )r
}r (h5X4 **Figure 1.** General model for an OAI-ORE document.h6jý h=h>h?Ucaptionr hA}r
(hC]hD]hE]hF]hI]uhKMzhM]r (cdocutils.nodes
strong
r )r }r (h5X
**Figure 1.**hA}r (hC]hD]hE]hF]hI]uh6j
hM]r hXX Figure 1.r …r }r (h5U h6j ubah?Ustrongr ubhXX' General model for an OAI-ORE document.r …r }r (h5X' General model for an OAI-ORE document.h6j
ubeubeubjü )r }r (h5U h6jŠ h=h>h?jÿ hA}r (hC]hD]hE]hF]r Uid8r ahI]uhKM~hLhhM]r (já )r! }r" (h5XÑ .. figure:: images/package_eg_1.png
**Figure 2.** Simple OAI-ORE representation of a data package with single
science metadata (*scimeta_id*) and data(*scidata_id*) objects. There are
two issues that need to be resolved for DataONE: a) how to assert that the
aggregated object *scidata_id* is described by the metadata *scimeta_id*;
and b) identifiers in OAI-ORE *must* be "protocol-based URIs", which is
more restrictive that DataONE requires.
h6j h=h>h?jä hA}r# (UuriX design/images/package_eg_1.pngr$ hF]hE]hC]hD]jç }r% U*j$ shI]uhKM~hM]ubj )r& }r' (h5X˜ **Figure 2.** Simple OAI-ORE representation of a data package with single
science metadata (*scimeta_id*) and data(*scidata_id*) objects. There are
two issues that need to be resolved for DataONE: a) how to assert that the
aggregated object *scidata_id* is described by the metadata *scimeta_id*;
and b) identifiers in OAI-ORE *must* be "protocol-based URIs", which is
more restrictive that DataONE requires.h6j h=h>h?j hA}r( (hC]hD]hE]hF]hI]uhKM~hM]r) (j )r* }r+ (h5X
**Figure 2.**hA}r, (hC]hD]hE]hF]hI]uh6j& hM]r- hXX Figure 2.r. …r/ }r0 (h5U h6j* ubah?j ubhXXO Simple OAI-ORE representation of a data package with single
science metadata (r1 …r2 }r3 (h5XO Simple OAI-ORE representation of a data package with single
science metadata (h6j& ubjG )r4 }r5 (h5X *scimeta_id*hA}r6 (hC]hD]hE]hF]hI]uh6j& hM]r7 hXX
scimeta_idr8 …r9 }r: (h5U h6j4 ubah?jO ubhXX ) and data(r; …r< }r= (h5X ) and data(h6j& ubjG )r> }r? (h5X *scidata_id*hA}r@ (hC]hD]hE]hF]hI]uh6j& hM]rA hXX
scidata_idrB …rC }rD (h5U h6j> ubah?jO ubhXXr ) objects. There are
two issues that need to be resolved for DataONE: a) how to assert that the
aggregated object rE …rF }rG (h5Xr ) objects. There are
two issues that need to be resolved for DataONE: a) how to assert that the
aggregated object h6j& ubjG )rH }rI (h5X *scidata_id*hA}rJ (hC]hD]hE]hF]hI]uh6j& hM]rK hXX
scidata_idrL …rM }rN (h5U h6jH ubah?jO ubhXX is described by the metadata rO …rP }rQ (h5X is described by the metadata h6j& ubjG )rR }rS (h5X *scimeta_id*hA}rT (hC]hD]hE]hF]hI]uh6j& hM]rU hXX
scimeta_idrV …rW }rX (h5U h6jR ubah?jO ubhXX ;
and b) identifiers in OAI-ORE rY …rZ }r[ (h5X ;
and b) identifiers in OAI-ORE h6j& ubjG )r\ }r] (h5X *must*hA}r^ (hC]hD]hE]hF]hI]uh6j& hM]r_ hXX mustr` …ra }rb (h5U h6j\ ubah?jO ubhXXK be "protocol-based URIs", which is
more restrictive that DataONE requires.rc …rd }re (h5XK be "protocol-based URIs", which is
more restrictive that DataONE requires.h6j& ubeubeubhy)rf }rg (h5X
**Issue:**rh h6jŠ h=h>h?hˆhA}ri (hC]hD]hE]hF]hI]uhKM†hLhhM]rj j )rk }rl (h5jh hA}rm (hC]hD]hE]hF]hI]uh6jf hM]rn hXX Issue:ro …rp }rq (h5U h6jk ubah?j ubaubhy)rr }rs (h5X‘ There are no predicates in ORE that can be used to indicate that the
aggregated object *scimeta_id* describes the data indicated by *scidata_id*.h6jŠ h=h>h?hˆhA}rt (hC]hD]hE]hF]hI]uhKMˆhLhhM]ru (hXXW There are no predicates in ORE that can be used to indicate that the
aggregated object rv …rw }rx (h5XW There are no predicates in ORE that can be used to indicate that the
aggregated object h6jr ubjG )ry }rz (h5X *scimeta_id*hA}r{ (hC]hD]hE]hF]hI]uh6jr hM]r| hXX
scimeta_idr} …r~ }r (h5U h6jy ubah?jO ubhXX! describes the data indicated by r€ …r }r‚ (h5X! describes the data indicated by h6jr ubjG )rƒ }r„ (h5X *scidata_id*hA}r… (hC]hD]hE]hF]hI]uh6jr hM]r† hXX
scidata_idr‡ …rˆ }r‰ (h5U h6jƒ ubah?jO ubhXX .…rŠ }r‹ (h5X .h6jr ubeubhy)rŒ }r (h5X **Options:**rŽ h6jŠ h=h>h?hˆhA}r (hC]hD]hE]hF]hI]uhKM‹hLhhM]r j )r‘ }r’ (h5jŽ hA}r“ (hC]hD]hE]hF]hI]uh6jŒ hM]r” hXX Options:r• …r– }r— (h5U h6j‘ ubah?j ubaubjc )r˜ }r™ (h5U h6jŠ h=h>h?jf hA}rš (jh U.hF]hE]hC]ji U hD]hI]jj jk uhKMhLhhM]r› (ht)rœ }r (h5Xé References between *scimeta_id* and *scidata_id* can be supported through
non-ORE RDF elements. Reuse of existing terms should be emphasized.
For example, the DCMI Type Vocabulary defines a *Dataset* type that could be
used to indicate that *scidata_id* refers to a data object by attaching the
Dublin Core Terms Type predicate to the ORE aggregated object. Other
possibilities from dcterms include `references`_ and `isReferencedBy`_,
`requires`_ and `isRequiredBy`_, and `relation`_.
In the document Mapping DataCite Metadata Scheme Terms (v2.0) to ontologies
(DataCite2RDF_), Shotton and Peroni provide a mapping between concepts
described in the DataCite schema and existing ontologies with the general
goal of expressing DataCite in RDF. The recommendation provided therein is to
use terms drawn from the Citation Typing Ontology (CiTO_) and others. The
semantics of the CiTO terms *documents* and *isDocumentedBy* match nicely
with the relationships between data and science metadata objects.
h6j˜ h=h>h?h hA}rž (hC]hD]hE]hF]hI]uhKNhLhhM]rŸ (hy)r }r¡ (h5X References between *scimeta_id* and *scidata_id* can be supported through
non-ORE RDF elements. Reuse of existing terms should be emphasized.h6jœ h=h>h?hˆhA}r¢ (hC]hD]hE]hF]hI]uhKMhM]r£ (hXX References between r¤ …r¥ }r¦ (h5X References between h6j ubjG )r§ }r¨ (h5X *scimeta_id*hA}r© (hC]hD]hE]hF]hI]uh6j hM]rª hXX
scimeta_idr« …r¬ }r (h5U h6j§ ubah?jO ubhXX and r® …r¯ }r° (h5X and h6j ubjG )r± }r² (h5X *scidata_id*hA}r³ (hC]hD]hE]hF]hI]uh6j hM]r´ hXX
scidata_idrµ …r¶ }r· (h5U h6j± ubah?jO ubhXX] can be supported through
non-ORE RDF elements. Reuse of existing terms should be emphasized.r¸ …r¹ }rº (h5X] can be supported through
non-ORE RDF elements. Reuse of existing terms should be emphasized.h6j ubeubhy)r» }r¼ (h5XW For example, the DCMI Type Vocabulary defines a *Dataset* type that could be
used to indicate that *scidata_id* refers to a data object by attaching the
Dublin Core Terms Type predicate to the ORE aggregated object. Other
possibilities from dcterms include `references`_ and `isReferencedBy`_,
`requires`_ and `isRequiredBy`_, and `relation`_.h6jœ h=h>h?hˆhA}r½ (hC]hD]hE]hF]hI]uhKMhM]r¾ (hXX0 For example, the DCMI Type Vocabulary defines a r¿ …rÀ }rÁ (h5X0 For example, the DCMI Type Vocabulary defines a h6j» ubjG )r }rà (h5X *Dataset*hA}rÄ (hC]hD]hE]hF]hI]uh6j» hM]rÅ hXX DatasetrÆ …rÇ }rÈ (h5U h6j ubah?jO ubhXX* type that could be
used to indicate that rÉ …rÊ }rË (h5X* type that could be
used to indicate that h6j» ubjG )rÌ }rÍ (h5X *scidata_id*hA}rÎ (hC]hD]hE]hF]hI]uh6j» hM]rÏ hXX
scidata_idrÐ …rÑ }rÒ (h5U h6jÌ ubah?jO ubhXX’ refers to a data object by attaching the
Dublin Core Terms Type predicate to the ORE aggregated object. Other
possibilities from dcterms include rÓ …rÔ }rÕ (h5X’ refers to a data object by attaching the
Dublin Core Terms Type predicate to the ORE aggregated object. Other
possibilities from dcterms include h6j» ubh~)rÖ }r× (h5X
`references`_jˆ Kh6j» h?h‡hA}rØ (UnameX
referencesrÙ jŠ X< http://dublincore.org/documents/dcmi-terms/#terms-referencesrÚ hF]hE]hC]hD]hI]uhM]rÛ hXX
referencesrÜ …rÝ }rÞ (h5U h6jÖ ubaubhXX and rß …rà }rá (h5X and h6j» ubh~)râ }rã (h5X `isReferencedBy`_jˆ Kh6j» h?h‡hA}rä (UnameX isReferencedByjŠ X@ http://dublincore.org/documents/dcmi-terms/#terms-isReferencedByrå hF]hE]hC]hD]hI]uhM]ræ hXX isReferencedByrç …rè }ré (h5U h6jâ ubaubhXX ,
rê …rë }rì (h5X ,
h6j» ubh~)rí }rî (h5X `requires`_jˆ Kh6j» h?h‡hA}rï (UnameX requiresrð jŠ X: http://dublincore.org/documents/dcmi-terms/#terms-requiresrñ hF]hE]hC]hD]hI]uhM]rò hXX requiresró …rô }rõ (h5U h6jí ubaubhXX and rö …r÷ }rø (h5X and h6j» ubh~)rù }rú (h5X `isRequiredBy`_jˆ Kh6j» h?h‡hA}rû (UnameX isRequiredByjŠ X> http://dublincore.org/documents/dcmi-terms/#terms-isRequiredByrü hF]hE]hC]hD]hI]uhM]rý hXX isRequiredByrþ …rÿ }r (h5U h6jù ubaubhXX , and r …r }r (h5X , and h6j» ubh~)r }r (h5X `relation`_jˆ Kh6j» h?h‡hA}r (UnameX relationr jŠ X: http://dublincore.org/documents/dcmi-terms/#terms-relationr hF]hE]hC]hD]hI]uhM]r hXX relationr
…r }r (h5U h6j ubaubhXX .…r
}r (h5X .h6j» ubeubhy)r }r (h5X In the document Mapping DataCite Metadata Scheme Terms (v2.0) to ontologies
(DataCite2RDF_), Shotton and Peroni provide a mapping between concepts
described in the DataCite schema and existing ontologies with the general
goal of expressing DataCite in RDF. The recommendation provided therein is to
use terms drawn from the Citation Typing Ontology (CiTO_) and others. The
semantics of the CiTO terms *documents* and *isDocumentedBy* match nicely
with the relationships between data and science metadata objects.h6jœ h=h>h?hˆhA}r (hC]hD]hE]hF]hI]uhKM–hM]r (hXXM In the document Mapping DataCite Metadata Scheme Terms (v2.0) to ontologies
(r …r }r (h5XM In the document Mapping DataCite Metadata Scheme Terms (v2.0) to ontologies
(h6j ubh~)r }r (h5X
DataCite2RDF_jˆ Kh6j h?h‡hA}r (UnameX DataCite2RDFjŠ Xn https://docs.google.com/document/d/1paJgvmCMu3pbM4in6PjWAKO0gP-6ultii3DWQslygq4/edit?authkey=CMeV3tgF&hl=en_GBr hF]hE]hC]hD]hI]uhM]r hXX DataCite2RDFr …r }r (h5U h6j ubaubhXX ), Shotton and Peroni provide a mapping between concepts
described in the DataCite schema and existing ontologies with the general
goal of expressing DataCite in RDF. The recommendation provided therein is to
use terms drawn from the Citation Typing Ontology (r …r }r (h5X ), Shotton and Peroni provide a mapping between concepts
described in the DataCite schema and existing ontologies with the general
goal of expressing DataCite in RDF. The recommendation provided therein is to
use terms drawn from the Citation Typing Ontology (h6j ubh~)r! }r" (h5X CiTO_jˆ Kh6j h?h‡hA}r# (UnameX CiTOjŠ X http://purl.org/spar/cito/r$ hF]hE]hC]hD]hI]uhM]r% hXX CiTOr& …r' }r( (h5U h6j! ubaubhXX. ) and others. The
semantics of the CiTO terms r) …r* }r+ (h5X. ) and others. The
semantics of the CiTO terms h6j ubjG )r, }r- (h5X *documents*hA}r. (hC]hD]hE]hF]hI]uh6j hM]r/ hXX documentsr0 …r1 }r2 (h5U h6j, ubah?jO ubhXX and r3 …r4 }r5 (h5X and h6j ubjG )r6 }r7 (h5X *isDocumentedBy*hA}r8 (hC]hD]hE]hF]hI]uh6j hM]r9 hXX isDocumentedByr: …r; }r< (h5U h6j6 ubah?jO ubhXXO match nicely
with the relationships between data and science metadata objects.r= …r> }r? (h5XO match nicely
with the relationships between data and science metadata objects.h6j ubeubeubht)r@ }rA (h5X\ That a science metadata object actually describes one or more data objects
can be inferred simply from its presence in a resource map aggregation.
Detection of science metadata vs. data would be highly dependent on the
object format for the object as expressed in it's system metadata. This could
be augmented by adding the `format`_ predicate from dcterms, with the object
being the corresponding entry in the object format registry. However, this
approach will not indicate which data objects are described by which metadata
documents in the case where multiple metadata documents exist in a package.
h6j˜ h=h>h?h hA}rB (hC]hD]hE]hF]hI]uhKNhLhhM]rC hy)rD }rE (h5XZ That a science metadata object actually describes one or more data objects
can be inferred simply from its presence in a resource map aggregation.
Detection of science metadata vs. data would be highly dependent on the
object format for the object as expressed in it's system metadata. This could
be augmented by adding the `format`_ predicate from dcterms, with the object
being the corresponding entry in the object format registry. However, this
approach will not indicate which data objects are described by which metadata
documents in the case where multiple metadata documents exist in a package.h6j@ h=h>h?hˆhA}rF (hC]hD]hE]hF]hI]uhKM hM]rG (hXXD That a science metadata object actually describes one or more data objects
can be inferred simply from its presence in a resource map aggregation.
Detection of science metadata vs. data would be highly dependent on the
object format for the object as expressed in it's system metadata. This could
be augmented by adding the rH …rI }rJ (h5XD That a science metadata object actually describes one or more data objects
can be inferred simply from its presence in a resource map aggregation.
Detection of science metadata vs. data would be highly dependent on the
object format for the object as expressed in it's system metadata. This could
be augmented by adding the h6jD ubh~)rK }rL (h5X `format`_jˆ Kh6jD h?h‡hA}rM (UnameX formatrN jŠ X8 http://dublincore.org/documents/dcmi-terms/#terms-formatrO hF]hE]hC]hD]hI]uhM]rP hXX formatrQ …rR }rS (h5U h6jK ubaubhXX
predicate from dcterms, with the object
being the corresponding entry in the object format registry. However, this
approach will not indicate which data objects are described by which metadata
documents in the case where multiple metadata documents exist in a package.rT …rU }rV (h5X
predicate from dcterms, with the object
being the corresponding entry in the object format registry. However, this
approach will not indicate which data objects are described by which metadata
documents in the case where multiple metadata documents exist in a package.h6jD ubeubaubeubhy)rW }rX (h5X **Resolution:**rY h6jŠ h=h>h?hˆhA}rZ (hC]hD]hE]hF]hI]uhKMªhLhhM]r[ j )r\ }r] (h5jY hA}r^ (hC]hD]hE]hF]hI]uh6jW hM]r_ hXX Resolution:r` …ra }rb (h5U h6j\ ubah?j ubaubhy)rc }rd (h5X1 Relationships between aggregated objects are indicated using terms drawn from
the CiTO_ ontology, with *cito:documents* attached to an aggregated science
metadata entry with the object of the triple being the URI of the relevant
aggregated data object, and the converse indicated by *cito:isDocumentedBy*.h6jŠ h=h>h?hˆhA}re (hC]hD]hE]hF]hI]uhKM¬hLhhM]rf (hXXR Relationships between aggregated objects are indicated using terms drawn from
the rg …rh }ri (h5XR Relationships between aggregated objects are indicated using terms drawn from
the h6jc ubh~)rj }rk (h5X CiTO_jˆ Kh6jc h?h‡hA}rl (UnameX CiTOjŠ j$ hF]hE]hC]hD]hI]uhM]rm hXX CiTOrn …ro }rp (h5U h6jj ubaubhXX ontology, with rq …rr }rs (h5X ontology, with h6jc ubjG )rt }ru (h5X *cito:documents*hA}rv (hC]hD]hE]hF]hI]uh6jc hM]rw hXX cito:documentsrx …ry }rz (h5U h6jt ubah?jO ubhXX¤ attached to an aggregated science
metadata entry with the object of the triple being the URI of the relevant
aggregated data object, and the converse indicated by r{ …r| }r} (h5X¤ attached to an aggregated science
metadata entry with the object of the triple being the URI of the relevant
aggregated data object, and the converse indicated by h6jc ubjG )r~ }r (h5X *cito:isDocumentedBy*hA}r€ (hC]hD]hE]hF]hI]uh6jc hM]r hXX cito:isDocumentedByr‚ …rƒ }r„ (h5U h6j~ ubah?jO ubhXX .…r… }r† (h5X .h6jc ubeubhy)r‡ }rˆ (h5X
**Issue:**r‰ h6jŠ h=h>h?hˆhA}rŠ (hC]hD]hE]hF]hI]uhKM²hLhhM]r‹ j )rŒ }r (h5j‰ hA}rŽ (hC]hD]hE]hF]hI]uh6j‡ hM]r hXX Issue:r …r‘ }r’ (h5U h6jŒ ubah?j ubaubhy)r“ }r” (h5X× Identifiers in OAI-ORE documents must technically be "protocol-based URIs"
(http://www.openarchives.org/ore/1.0/datamodel#Aggregated_Resource), whereas
identifiers in DataONE can be essentially any non-blank string.h6jŠ h=h>h?hˆhA}r• (hC]hD]hE]hF]hI]uhKM´hLhhM]r– (hXXL Identifiers in OAI-ORE documents must technically be "protocol-based URIs"
(r— …r˜ }r™ (h5XL Identifiers in OAI-ORE documents must technically be "protocol-based URIs"
(h6j“ ubh~)rš }r› (h5XA http://www.openarchives.org/ore/1.0/datamodel#Aggregated_Resourcerœ hA}r (Urefurijœ hF]hE]hC]hD]hI]uh6j“ hM]rž hXXA http://www.openarchives.org/ore/1.0/datamodel#Aggregated_ResourcerŸ …r }r¡ (h5U h6jš ubah?h‡ubhXXJ ), whereas
identifiers in DataONE can be essentially any non-blank string.r¢ …r£ }r¤ (h5XJ ), whereas
identifiers in DataONE can be essentially any non-blank string.h6j“ ubeubhy)r¥ }r¦ (h5X **Options:**r§ h6jŠ h=h>h?hˆhA}r¨ (hC]hD]hE]hF]hI]uhKM¸hLhhM]r© j )rª }r« (h5j§ hA}r¬ (hC]hD]hE]hF]hI]uh6j¥ hM]r hXX Options:r® …r¯ }r° (h5U h6jª ubah?j ubaubjc )r± }r² (h5U h6jŠ h=h>h?jf hA}r³ (jh U.hF]hE]hC]ji U hD]hI]jj jk uhKMºhLhhM]r´ (ht)rµ }r¶ (h5X Ignore the OAI-ORE requirement for URI identifiers. The identifiers will
still work fine in the DataONE context, but would not be friendly for anyone
accessing the ORE document without an appropriate DataONE client to resolve
and retrieve the referenced objects.
h6j± h=h>h?h hA}r· (hC]hD]hE]hF]hI]uhKNhLhhM]r¸ hy)r¹ }rº (h5X Ignore the OAI-ORE requirement for URI identifiers. The identifiers will
still work fine in the DataONE context, but would not be friendly for anyone
accessing the ORE document without an appropriate DataONE client to resolve
and retrieve the referenced objects.r» h6jµ h=h>h?hˆhA}r¼ (hC]hD]hE]hF]hI]uhKM¼hM]r½ hXX Ignore the OAI-ORE requirement for URI identifiers. The identifiers will
still work fine in the DataONE context, but would not be friendly for anyone
accessing the ORE document without an appropriate DataONE client to resolve
and retrieve the referenced objects.r¾ …r¿ }rÀ (h5j» h6j¹ ubaubaubht)rÁ }r (h5X@ Wrap the identifiers with a DataONE REST service URL that retrieves the
object being referenced. So for example, if the DataONE identifier for the
object was *scimeta_id*, then the URI used in the ORE document to reference
the aggregated object would *http://cn.dataone.org/object/scimeta_id*. The
:func:`CN_read.get` operation would be modified to do a resolve, then a HTTP
302 redirect to the node that contains the content. This would also require
that the client libraries are updated to support redirection.
This option has the advantage of keeping the the ORE document functional for
non-DataONE users but has the disadvantage of obfuscating the object
identifiers. The later issue could be addressed by adding the dcterms
`identifier`_ property to the aggregated object with the object being the
actual DataONE identifier.
h6j± h=h>h?h hA}rà (hC]hD]hE]hF]hI]uhKNhLhhM]rÄ (hy)rÅ }rÆ (h5X Wrap the identifiers with a DataONE REST service URL that retrieves the
object being referenced. So for example, if the DataONE identifier for the
object was *scimeta_id*, then the URI used in the ORE document to reference
the aggregated object would *http://cn.dataone.org/object/scimeta_id*. The
:func:`CN_read.get` operation would be modified to do a resolve, then a HTTP
302 redirect to the node that contains the content. This would also require
that the client libraries are updated to support redirection.h6jÁ h=h>h?hˆhA}rÇ (hC]hD]hE]hF]hI]uhKMÃhM]rÈ (hXXž Wrap the identifiers with a DataONE REST service URL that retrieves the
object being referenced. So for example, if the DataONE identifier for the
object was rÉ …rÊ }rË (h5Xž Wrap the identifiers with a DataONE REST service URL that retrieves the
object being referenced. So for example, if the DataONE identifier for the
object was h6jÅ ubjG )rÌ }rÍ (h5X *scimeta_id*hA}rÎ (hC]hD]hE]hF]hI]uh6jÅ hM]rÏ hXX
scimeta_idrÐ …rÑ }rÒ (h5U h6jÌ ubah?jO ubhXXQ , then the URI used in the ORE document to reference
the aggregated object would rÓ …rÔ }rÕ (h5XQ , then the URI used in the ORE document to reference
the aggregated object would h6jÅ ubjG )rÖ }r× (h5X) *http://cn.dataone.org/object/scimeta_id*hA}rØ (hC]hD]hE]hF]hI]uh6jÅ hM]rÙ hXX' http://cn.dataone.org/object/scimeta_idrÚ …rÛ }rÜ (h5U h6jÖ ubah?jO ubhXX . The
rÝ …rÞ }rß (h5X . The
h6jÅ ubj. )rà }rá (h5X :func:`CN_read.get`râ h6jÅ h=h>h?j2 hA}rã (UreftypeX funcj4 ‰j5 X CN_read.getU refdomainX pyrä hF]hE]U refexplicit‰hC]hD]hI]j7 j8 j Nj NuhKMÃhM]rå j )ræ }rç (h5jâ hA}rè (hC]hD]ré (j? jä X py-funcrê ehE]hF]hI]uh6jà hM]rë hXX
CN_read.get()rì …rí }rî (h5U h6jæ ubah?j( ubaubhXXÃ operation would be modified to do a resolve, then a HTTP
302 redirect to the node that contains the content. This would also require
that the client libraries are updated to support redirection.rï …rð }rñ (h5XÃ operation would be modified to do a resolve, then a HTTP
302 redirect to the node that contains the content. This would also require
that the client libraries are updated to support redirection.h6jÅ ubeubhy)rò }ró (h5X< This option has the advantage of keeping the the ORE document functional for
non-DataONE users but has the disadvantage of obfuscating the object
identifiers. The later issue could be addressed by adding the dcterms
`identifier`_ property to the aggregated object with the object being the
actual DataONE identifier.h6jÁ h=h>h?hˆhA}rô (hC]hD]hE]hF]hI]uhKMËhM]rõ (hXXØ This option has the advantage of keeping the the ORE document functional for
non-DataONE users but has the disadvantage of obfuscating the object
identifiers. The later issue could be addressed by adding the dcterms
rö …r÷ }rø (h5XØ This option has the advantage of keeping the the ORE document functional for
non-DataONE users but has the disadvantage of obfuscating the object
identifiers. The later issue could be addressed by adding the dcterms
h6jò ubh~)rù }rú (h5X
`identifier`_jˆ Kh6jò h?h‡hA}rû (UnameX
identifierrü jŠ X< http://dublincore.org/documents/dcmi-terms/#terms-identifierrý hF]hE]hC]hD]hI]uhM]rþ hXX
identifierrÿ …r
}r
(h5U h6jù ubaubhXXW property to the aggregated object with the object being the
actual DataONE identifier.r
…r
}r
(h5XW property to the aggregated object with the object being the
actual DataONE identifier.h6jò ubeubeubeubhy)r
}r
(h5X **Resolution:**r
h6jŠ h=h>h?hˆhA}r
(hC]hD]hE]hF]hI]uhKMÒhLhhM]r
j )r
}r
(h5j
hA}r
(hC]hD]hE]hF]hI]uh6j
hM]r
hXX Resolution:r
…r
}r
(h5U h6j
ubah?j ubaubhy)r
}r
(h5X ORE URIs for aggregated objects are constructed by prepending the
:func:`CNCore.resolve` REST URL to the identifier (with the identifier
appropriately URI path encoded). :func:`CNRead.resolve` returns an
:class:`Types.ObjectLocationList` as the response body, and a HTTP status of
302 with the first node listed in the ObjectLocationList being the target of
the redirect. The literal DataONE identifier for the aggregated object is
added to the ORE aggregate entry as a dcterms `identifier`_ property. DataONE
clients will utilize the *dcterms:identifier* entry to determine the DataONE
identifier of the object and utilize the normal *resolve* and *get* approach
for retrieving the object. The URLs contained in the ORE document will
continue to be handled as expected by other clients.h6jŠ h=h>h?hˆhA}r
(hC]hD]hE]hF]hI]uhKMÔhLhhM]r
(hXXB ORE URIs for aggregated objects are constructed by prepending the
r
…r
}r
(h5XB ORE URIs for aggregated objects are constructed by prepending the
h6j
ubj. )r
}r
(h5X :func:`CNCore.resolve`r
h6j
h=h>h?j2 hA}r
(UreftypeX funcj4 ‰j5 X CNCore.resolveU refdomainX pyr
hF]hE]U refexplicit‰hC]hD]hI]j7 j8 j Nj NuhKMÔhM]r
j )r
}r
(h5j
hA}r
(hC]hD]r!
(j? j
X py-funcr"
ehE]hF]hI]uh6j
hM]r#
hXX CNCore.resolve()r$
…r%
}r&
(h5U h6j
ubah?j( ubaubhXXR REST URL to the identifier (with the identifier
appropriately URI path encoded). r'
…r(
}r)
(h5XR REST URL to the identifier (with the identifier
appropriately URI path encoded). h6j
ubj. )r*
}r+
(h5X :func:`CNRead.resolve`r,
h6j
h=h>h?j2 hA}r-
(UreftypeX funcj4 ‰j5 X CNRead.resolveU refdomainX pyr.
hF]hE]U refexplicit‰hC]hD]hI]j7 j8 j Nj NuhKMÔhM]r/
j )r0
}r1
(h5j,
hA}r2
(hC]hD]r3
(j? j.
X py-funcr4
ehE]hF]hI]uh6j*
hM]r5
hXX CNRead.resolve()r6
…r7
}r8
(h5U h6j0
ubah?j( ubaubhXX returns an
r9
…r:
}r;
(h5X returns an
h6j
ubj. )r<
}r=
(h5X! :class:`Types.ObjectLocationList`r>
h6j
h=h>h?j2 hA}r?
(UreftypeX classj4 ‰j5 X Types.ObjectLocationListU refdomainX pyr@
hF]hE]U refexplicit‰hC]hD]hI]j7 j8 j Nj NuhKMÔhM]rA
j )rB
}rC
(h5j>
hA}rD
(hC]hD]rE
(j? j@
X py-classrF
ehE]hF]hI]uh6j<
hM]rG
hXX Types.ObjectLocationListrH
…rI
}rJ
(h5U h6jB
ubah?j( ubaubhXXñ as the response body, and a HTTP status of
302 with the first node listed in the ObjectLocationList being the target of
the redirect. The literal DataONE identifier for the aggregated object is
added to the ORE aggregate entry as a dcterms rK
…rL
}rM
(h5Xñ as the response body, and a HTTP status of
302 with the first node listed in the ObjectLocationList being the target of
the redirect. The literal DataONE identifier for the aggregated object is
added to the ORE aggregate entry as a dcterms h6j
ubh~)rN
}rO
(h5X
`identifier`_jˆ Kh6j
h?h‡hA}rP
(UnameX
identifierjŠ jý hF]hE]hC]hD]hI]uhM]rQ
hXX
identifierrR
…rS
}rT
(h5U h6jN
ubaubhXX, property. DataONE
clients will utilize the rU
…rV
}rW
(h5X, property. DataONE
clients will utilize the h6j
ubjG )rX
}rY
(h5X *dcterms:identifier*hA}rZ
(hC]hD]hE]hF]hI]uh6j
hM]r[
hXX dcterms:identifierr\
…r]
}r^
(h5U h6jX
ubah?jO ubhXXP entry to determine the DataONE
identifier of the object and utilize the normal r_
…r`
}ra
(h5XP entry to determine the DataONE
identifier of the object and utilize the normal h6j
ubjG )rb
}rc
(h5X *resolve*hA}rd
(hC]hD]hE]hF]hI]uh6j
hM]re
hXX resolverf
…rg
}rh
(h5U h6jb
ubah?jO ubhXX and ri
…rj
}rk
(h5X and h6j
ubjG )rl
}rm
(h5X *get*hA}rn
(hC]hD]hE]hF]hI]uh6j
hM]ro
hXX getrp
…rq
}rr
(h5U h6jl
ubah?jO ubhXX… approach
for retrieving the object. The URLs contained in the ORE document will
continue to be handled as expected by other clients.rs
…rt
}ru
(h5X… approach
for retrieving the object. The URLs contained in the ORE document will
continue to be handled as expected by other clients.h6j
ubeubeubh7)rv
}rw
(h5U h6j5 h=h>h?h@hA}rx
(hC]hD]hE]hF]ry
jt ahI]rz
h
auhKMâhLhhM]r{
(hO)r|
}r}
(h5jy h6jv
h=h>h?hShA}r~
(hF]hE]hC]hD]hI]hUjs uhKMâhLhhM]r
hXX Examplesr€
…r
}r‚
(h5jy h6j|
ubaubhy)rƒ
}r„
(h5X_ An RDF-XML rendering of the example from Figure 2 following the
recommendations as generated using the `Foresite python library`_ is presented
below. This OAI-ORE document is an example of a simple data package in
DataONE, where a single science metadata document (identifier = *scimeta_id*)
describes a single data object (identifier = *scidata_id*).h6jv
h=h>h?hˆhA}r…
(hC]hD]hE]hF]hI]uhKMähLhhM]r†
(hXXg An RDF-XML rendering of the example from Figure 2 following the
recommendations as generated using the r‡
…rˆ
}r‰
(h5Xg An RDF-XML rendering of the example from Figure 2 following the
recommendations as generated using the h6jƒ
ubh~)rŠ
}r‹
(h5X `Foresite python library`_jˆ Kh6jƒ
h?h‡hA}rŒ
(UnameX Foresite python libraryjŠ X< http://code.google.com/p/foresite-toolkit/wiki/PythonLibraryr
hF]hE]hC]hD]hI]uhM]rŽ
hXX Foresite python libraryr
…r
}r‘
(h5U h6jŠ
ubaubhXX• is presented
below. This OAI-ORE document is an example of a simple data package in
DataONE, where a single science metadata document (identifier = r’
…r“
}r”
(h5X• is presented
below. This OAI-ORE document is an example of a simple data package in
DataONE, where a single science metadata document (identifier = h6jƒ
ubjG )r•
}r–
(h5X *scimeta_id*hA}r—
(hC]hD]hE]hF]hI]uh6jƒ
hM]r˜
hXX
scimeta_idr™
…rš
}r›
(h5U h6j•
ubah?jO ubhXX/ )
describes a single data object (identifier = rœ
…r
}rž
(h5X/ )
describes a single data object (identifier = h6jƒ
ubjG )rŸ
}r
(h5X *scidata_id*hA}r¡
(hC]hD]hE]hF]hI]uh6jƒ
hM]r¢
hXX
scidata_idr£
…r¤
}r¥
(h5U h6jŸ
ubah?jO ubhXX ).r¦
…r§
}r¨
(h5X ).h6jƒ
ubeubj· )r©
}rª
(h5X`
foresite@googlegroups.com
Foresite Toolkit (Python)
scimeta_id
A reference to a science metadata document using a DataONE identifier.
ResourceMap
resource_map_id
2011-08-12T12:55:16Z
application/rdf+xml
2011-08-12T12:55:16Z
Aggregation
Simple aggregation of science metadata and data
scidata_id
A reference to a science data object using a DataONE identifier
h6jv
h=h>h?jº hA}r«
(Ulinenosr¬
‰Ulanguager
X xmlj¼ j½ hF]hE]hC]Uhighlight_argsr®
}hD]hI]uhKMêhLhhM]r¯
hXX`
foresite@googlegroups.com
Foresite Toolkit (Python)
scimeta_id
A reference to a science metadata document using a DataONE identifier.
ResourceMap
resource_map_id
2011-08-12T12:55:16Z
application/rdf+xml
2011-08-12T12:55:16Z
Aggregation
Simple aggregation of science metadata and data
scidata_id
A reference to a science data object using a DataONE identifier
r°
…r±
}r²
(h5U h6j©
ubaubhy)r³
}r´
(h5X The same in N3::rµ
h6jv
h=h>h?hˆhA}r¶
(hC]hD]hE]hF]hI]uhKM hLhhM]r·
hXX The same in N3:r¸
…r¹
}rº
(h5X The same in N3:h6j³
ubaubj· )r»
}r¼
(h5X @prefix cito: .
@prefix dc: .
@prefix dcterms: .
@prefix foaf: .
@prefix ore: .
@prefix rdfs1: .
a ;
dc:format "text/rdf+n3";
dcterms:created "2011-08-12T12:57:03Z";
dcterms:creator ;
dcterms:identifier "resource_map_id";
dcterms:modified "2011-08-12T12:57:03Z";
ore:describes .
a ;
dcterms:title "Simple aggregation of science metadata and data";
ore:aggregates ,
.
foaf:mbox "foresite@googlegroups.com";
foaf:name "Foresite Toolkit (Python)" .
rdfs1:isDefinedBy ore:;
rdfs1:label "Aggregation" .
rdfs1:isDefinedBy ore:;
rdfs1:label "ResourceMap" .
dcterms:description "A reference to a science data object using a DataONE identifier";
dcterms:identifier "scidata_id";
cito:isDocumentedBy .
dcterms:description "A reference to a science metadata document using a DataONE identifier.";
dcterms:identifier "scimeta_id";
cito:documents .h6jv
h=h>h?jº hA}r½
(j¼ j½ hF]hE]hC]hD]hI]uhKM!hLhhM]r¾
hXX @prefix cito: .
@prefix dc: .
@prefix dcterms: .
@prefix foaf: .
@prefix ore: .
@prefix rdfs1: .
a ;
dc:format "text/rdf+n3";
dcterms:created "2011-08-12T12:57:03Z";
dcterms:creator ;
dcterms:identifier "resource_map_id";
dcterms:modified "2011-08-12T12:57:03Z";
ore:describes .
a ;
dcterms:title "Simple aggregation of science metadata and data";
ore:aggregates ,
.
foaf:mbox "foresite@googlegroups.com";
foaf:name "Foresite Toolkit (Python)" .
rdfs1:isDefinedBy ore:;
rdfs1:label "Aggregation" .
rdfs1:isDefinedBy ore:;
rdfs1:label "ResourceMap" .
dcterms:description "A reference to a science data object using a DataONE identifier";
dcterms:identifier "scidata_id";
cito:isDocumentedBy .
dcterms:description "A reference to a science metadata document using a DataONE identifier.";
dcterms:identifier "scimeta_id";
cito:documents .r¿
…rÀ
}rÁ
(h5U h6j»
ubaubjü )rÂ
}rÃ
(h5U h6jv
h=h>h?jÿ hA}rÄ
(hC]hD]hE]hF]rÅ
Uid9rÆ
ahI]uhKMJhLhhM]rÇ
(já )rÈ
}rÉ
(h5Xg .. figure:: images/resourcemap_eg_1.png
**Figure 3.** Also rendered using the W3C RDF validator.
h6jÂ
h=h>h?jä hA}rÊ
(UuriX" design/images/resourcemap_eg_1.pngrË
hF]hE]hC]hD]jç }rÌ
U*jË
shI]uhKMJhM]ubj )rÍ
}rÎ
(h5X8 **Figure 3.** Also rendered using the W3C RDF validator.h6jÂ
h=h>h?j hA}rÏ
(hC]hD]hE]hF]hI]uhKMJhM]rÐ
(j )rÑ
}rÒ
(h5X
**Figure 3.**hA}rÓ
(hC]hD]hE]hF]hI]uh6jÍ
hM]rÔ
hXX Figure 3.rÕ
…rÖ
}r×
(h5U h6jÑ
ubah?j ubhXX+ Also rendered using the W3C RDF validator.rØ
…rÙ
}rÚ
(h5X+ Also rendered using the W3C RDF validator.h6jÍ
ubeubeubjÓ )rÛ
}rÜ
(h5X€ .. _DataCite2RDF: https://docs.google.com/document/d/1paJgvmCMu3pbM4in6PjWAKO0gP-6ultii3DWQslygq4/edit?authkey=CMeV3tgF&hl=en_GBh:Kh6jv
h=h>h?jÖ hA}rÝ
(jŠ j hF]rÞ
U datacite2rdfrß
ahE]hC]hD]hI]rà
hauhKMNhLhhM]ubjÓ )rá
}râ
(h5XL .. _conformsTo: http://dublincore.org/documents/dcmi-terms/#terms-conformsToh6jv
h=h>h?jÖ hA}rã
(jŠ X< http://dublincore.org/documents/dcmi-terms/#terms-conformsTohF]rä
U
conformstorå
ahE]hC]hD]hI]ræ
h!auhKMPhLhhM]ubjÓ )rç
}rè
(h5XL .. _references: http://dublincore.org/documents/dcmi-terms/#terms-referencesh:Kh6jv
h=h>h?jÖ hA}ré
(jŠ jÚ hF]rê
U
referencesrë
ahE]hC]hD]hI]rì
h(auhKMRhLhhM]ubjÓ )rí
}rî
(h5XT .. _isReferencedBy: http://dublincore.org/documents/dcmi-terms/#terms-isReferencedByh:Kh6jv
h=h>h?jÖ hA}rï
(jŠ jå hF]rð
Uisreferencedbyrñ
ahE]hC]hD]hI]rò
h auhKMThLhhM]ubjÓ )ró
}rô
(h5XH .. _requires: http://dublincore.org/documents/dcmi-terms/#terms-requiresh:Kh6jv
h=h>h?jÖ hA}rõ
(jŠ jñ hF]rö
Urequiresr÷
ahE]hC]hD]hI]rø
h+auhKMVhLhhM]ubjÓ )rù
}rú
(h5XP .. _isRequiredBy: http://dublincore.org/documents/dcmi-terms/#terms-isRequiredByh:Kh6jv
h=h>h?jÖ hA}rû
(jŠ jü hF]rü
U isrequiredbyrý
ahE]hC]hD]hI]rþ
h auhKMXhLhhM]ubjÓ )rÿ
}r (h5XH .. _relation: http://dublincore.org/documents/dcmi-terms/#terms-relationh:Kh6jv
h=h>h?jÖ hA}r (jŠ j hF]r Urelationr ahE]hC]hD]hI]r h,auhKMZhLhhM]ubjÓ )r }r (h5XD .. _format: http://dublincore.org/documents/dcmi-terms/#terms-formath:Kh6jv
h=h>h?jÖ hA}r (jŠ jO hF]r Uformatr ahE]hC]hD]hI]r
hauhKM\hLhhM]ubjÓ )r }r (h5XL .. _identifier: http://dublincore.org/documents/dcmi-terms/#terms-identifierh:Kh6jv
h=h>h?jÖ hA}r
(jŠ jý hF]r U
identifierr ahE]hC]hD]hI]r h*auhKM^hLhhM]ubjÓ )r }r (h5X$ .. _CiTO: http://purl.org/spar/cito/h:Kh6jv
h=h>h?jÖ hA}r (jŠ j$ hF]r Ucitor ahE]hC]hD]hI]r hauhKM`hLhhM]ubeubeubh7)r }r (h5U h6h;h=h>h?h@hA}r (hC]hD]hE]hF]r j‡ ahI]r hauhKMehLhhM]r (hO)r }r (h5jŒ h6j h=h>h?hShA}r (hF]hE]hC]hD]hI]hUj† uhKMehLhhM]r hXX! Package Serialization Using BagItr! …r" }r# (h5jŒ h6j ubaubhy)r$ }r% (h5XË The BagIt File Packaging Format [Boyko-2009]_ "is a hierarchical file
packaging format designed to support disk-based or network-based storage and
transfer of generalized digital content" (p.3). BagIt is defined in an
Internet RFC that is currently being revised and is being considered in
several library implementations. BagIt mainly provides a consistent mechanism
for a serialized representation of a group of opaque objects using commonly
available technological approaches (such as the zip archive format). BagIt
includes a specification for including metadata about each of the objects, the
bag itself, and fixity attributes so that any BagIt implementation can
validate the components contained within a package. Unlike NetCDF and EML, BagIt
does not attempt to provide a data model for the data it carries, instead
asserting that consuming applications will know how to handle package contents
based on the metadata included in the bag or via external knowledge.h6j h=h>h?hˆhA}r& (hC]hD]hE]hF]hI]uhKMghLhhM]r' (hXX The BagIt File Packaging Format r( …r) }r* (h5X The BagIt File Packaging Format h6j$ ubj. )r+ }r, (h5X
Boyko-2009r- h6j$ h=h>h?j2 hA}r. (Ureftypej# UrefwarnˆU reftargetj- U refdomainj$ hF]r/ Uid3r0 ahE]hC]hD]hI]uhKMghLhhM]r1 hXX [Boyko-2009]r2 …r3 }r4 (h5U h6j+ ubaubhXXž "is a hierarchical file
packaging format designed to support disk-based or network-based storage and
transfer of generalized digital content" (p.3). BagIt is defined in an
Internet RFC that is currently being revised and is being considered in
several library implementations. BagIt mainly provides a consistent mechanism
for a serialized representation of a group of opaque objects using commonly
available technological approaches (such as the zip archive format). BagIt
includes a specification for including metadata about each of the objects, the
bag itself, and fixity attributes so that any BagIt implementation can
validate the components contained within a package. Unlike NetCDF and EML, BagIt
does not attempt to provide a data model for the data it carries, instead
asserting that consuming applications will know how to handle package contents
based on the metadata included in the bag or via external knowledge.r5 …r6 }r7 (h5Xž "is a hierarchical file
packaging format designed to support disk-based or network-based storage and
transfer of generalized digital content" (p.3). BagIt is defined in an
Internet RFC that is currently being revised and is being considered in
several library implementations. BagIt mainly provides a consistent mechanism
for a serialized representation of a group of opaque objects using commonly
available technological approaches (such as the zip archive format). BagIt
includes a specification for including metadata about each of the objects, the
bag itself, and fixity attributes so that any BagIt implementation can
validate the components contained within a package. Unlike NetCDF and EML, BagIt
does not attempt to provide a data model for the data it carries, instead
asserting that consuming applications will know how to handle package contents
based on the metadata included in the bag or via external knowledge.h6j$ ubeubhy)r8 }r9 (h5X Beneficial featuresr: h6j h=h>h?hˆhA}r; (hC]hD]hE]hF]hI]uhKMuhLhhM]r< hXX Beneficial featuresr= …r> }r? (h5j: h6j8 ubaubj¹ )r@ }rA (h5U h6j h=Nh?jò hA}rB (hC]hD]hE]hF]hI]uhKNhLhhM]rC hn)rD }rE (h5U hA}rF (jc X *hF]hE]hC]hD]hI]uh6j@ hM]rG (ht)rH }rI (h5XB Simple and clear serialization, easy to parse, simple to recreate
hA}rJ (hC]hD]hE]hF]hI]uh6jD hM]rK hy)rL }rM (h5XA Simple and clear serialization, easy to parse, simple to recreaterN h6jH h=h>h?hˆhA}rO (hC]hD]hE]hF]hI]uhKMwhM]rP hXXA Simple and clear serialization, easy to parse, simple to recreaterQ …rR }rS (h5jN h6jL ubaubah?h ubht)rT }rU (h5Xr Allows referencing external resources via URI, which are used to populate
objects in the bag when it is processed
hA}rV (hC]hD]hE]hF]hI]uh6jD hM]rW hy)rX }rY (h5Xq Allows referencing external resources via URI, which are used to populate
objects in the bag when it is processedrZ h6jT h=h>h?hˆhA}r[ (hC]hD]hE]hF]hI]uhKMyhM]r\ hXXq Allows referencing external resources via URI, which are used to populate
objects in the bag when it is processedr] …r^ }r_ (h5jZ h6jX ubaubah?h ubeh?hqubaubhy)r` }ra (h5X Issuesrb h6j h=h>h?hˆhA}rc (hC]hD]hE]hF]hI]uhKM|hLhhM]rd hXX Issuesre …rf }rg (h5jb h6j` ubaubj¹ )rh }ri (h5U h6j h=Nh?jò hA}rj (hC]hD]hE]hF]hI]uhKNhLhhM]rk hn)rl }rm (h5U hA}rn (jc X *hF]hE]hC]hD]hI]uh6jh hM]ro (ht)rp }rq (h5X; No data model for internal structure of enclosed resources
hA}rr (hC]hD]hE]hF]hI]uh6jl hM]rs hy)rt }ru (h5X: No data model for internal structure of enclosed resourcesrv h6jp h=h>h?hˆhA}rw (hC]hD]hE]hF]hI]uhKM~hM]rx hXX: No data model for internal structure of enclosed resourcesry …rz }r{ (h5jv h6jt ubaubah?h ubht)r| }r} (h5X= Hierarchical structure is not extensible to arbitrary graphs
hA}r~ (hC]hD]hE]hF]hI]uh6jl hM]r hy)r€ }r (h5X< Hierarchical structure is not extensible to arbitrary graphsr‚ h6j| h=h>h?hˆhA}rƒ (hC]hD]hE]hF]hI]uhKM€hM]r„ hXX< Hierarchical structure is not extensible to arbitrary graphsr… …r† }r‡ (h5j‚ h6j€ ubaubah?h ubht)rˆ }r‰ (h5X9 No explicit definition of the identifier for each object
hA}rŠ (hC]hD]hE]hF]hI]uh6jl hM]r‹ hy)rŒ }r (h5X8 No explicit definition of the identifier for each objectrŽ h6jˆ h=h>h?hˆhA}r (hC]hD]hE]hF]hI]uhKM‚hM]r hXX8 No explicit definition of the identifier for each objectr‘ …r’ }r“ (h5jŽ h6jŒ ubaubah?h ubht)r” }r• (h5Xì No clear delineation of the boundaries of objects within a hierarchy (e.g.,
for any given sub-object in the hierarchy, is it identified by the name of
its parent directory or by its own filename, or by a locally-scoped version
of both?
hA}r– (hC]hD]hE]hF]hI]uh6jl hM]r— hy)r˜ }r™ (h5Xë No clear delineation of the boundaries of objects within a hierarchy (e.g.,
for any given sub-object in the hierarchy, is it identified by the name of
its parent directory or by its own filename, or by a locally-scoped version
of both?rš h6j” h=h>h?hˆhA}r› (hC]hD]hE]hF]hI]uhKM„hM]rœ hXXë No clear delineation of the boundaries of objects within a hierarchy (e.g.,
for any given sub-object in the hierarchy, is it identified by the name of
its parent directory or by its own filename, or by a locally-scoped version
of both?r …rž }rŸ (h5jš h6j˜ ubaubah?h ubeh?hqubaubhy)r }r¡ (h5X Questionsr¢ h6j h=h>h?hˆhA}r£ (hC]hD]hE]hF]hI]uhKM‰hLhhM]r¤ hXX Questionsr¥ …r¦ }r§ (h5j¢ h6j ubaubj¹ )r¨ }r© (h5U h6j h=Nh?jò hA}rª (hC]hD]hE]hF]hI]uhKNhLhhM]r« hn)r¬ }r (h5U hA}r® (jc X *hF]hE]hC]hD]hI]uh6j¨ hM]r¯ (ht)r° }r± (h5X¢ How is a URI or other identifier for data objects represented in the
metadata, and how is it mapped to the data object to which it applies in
the data hierarchy?
hA}r² (hC]hD]hE]hF]hI]uh6j¬ hM]r³ hy)r´ }rµ (h5X¡ How is a URI or other identifier for data objects represented in the
metadata, and how is it mapped to the data object to which it applies in
the data hierarchy?r¶ h6j° h=h>h?hˆhA}r· (hC]hD]hE]hF]hI]uhKM‹hM]r¸ hXX¡ How is a URI or other identifier for data objects represented in the
metadata, and how is it mapped to the data object to which it applies in
the data hierarchy?r¹ …rº }r» (h5j¶ h6j´ ubaubah?h ubht)r¼ }r½ (h5Xƒ To be valid, must all of the fetch.txt URLs be downloaded and checksummed,
and how is this handled for particularly large objects?
hA}r¾ (hC]hD]hE]hF]hI]uh6j¬ hM]r¿ hy)rÀ }rÁ (h5X‚ To be valid, must all of the fetch.txt URLs be downloaded and checksummed,
and how is this handled for particularly large objects?r h6j¼ h=h>h?hˆhA}rà (hC]hD]hE]hF]hI]uhKMhM]rÄ hXX‚ To be valid, must all of the fetch.txt URLs be downloaded and checksummed,
and how is this handled for particularly large objects?rÅ …rÆ }rÇ (h5j h6jÀ ubaubah?h ubht)rÈ }rÉ (h5X[ How are large objects that would normally exceed file system size
limitations be handled?
hA}rÊ (hC]hD]hE]hF]hI]uh6j¬ hM]rË hy)rÌ }rÍ (h5XY How are large objects that would normally exceed file system size
limitations be handled?rÎ h6jÈ h=h>h?hˆhA}rÏ (hC]hD]hE]hF]hI]uhKM’hM]rÐ hXXY How are large objects that would normally exceed file system size
limitations be handled?rÑ …rÒ }rÓ (h5jÎ h6jÌ ubaubah?h ubeh?hqubaubhy)rÔ }rÕ (h5X° The structure of a Data Package will follow the BagIt specification with the
exception of the following additions and changes described here. The basic
structure of a bag is::h6j h=h>h?hˆhA}rÖ (hC]hD]hE]hF]hI]uhKM–hLhhM]r× hXX¯ The structure of a Data Package will follow the BagIt specification with the
exception of the following additions and changes described here. The basic
structure of a bag is:rØ …rÙ }rÚ (h5X¯ The structure of a Data Package will follow the BagIt specification with the
exception of the following additions and changes described here. The basic
structure of a bag is:h6jÔ ubaubj· )rÛ }rÜ (h5X /
├── bagit.txt
├── bag-info.txt
├── manifest-.txt
├── oai-ore.txt
├── pid-mapping.txt
└── data
├── data-file-1.csv
├── data-file-2.csv
├── data-file-3.hdf
└── metadata-file-1.xmlh6j h=h>h?jº hA}rÝ (j¼ j½ hF]hE]hC]hD]hI]uhKMšhLhhM]rÞ hXX /
├── bagit.txt
├── bag-info.txt
├── manifest-.txt
├── oai-ore.txt
├── pid-mapping.txt
└── data
├── data-file-1.csv
├── data-file-2.csv
├── data-file-3.hdf
└── metadata-file-1.xmlrß …rà }rá (h5U h6jÛ ubaubhy)râ }rã (h5X! The first addition is the presence of an OAI-ORE document ``oai-ore.txt`` within
the base directory that uses the object identifiers for DataONE objects and
describes the relationships among the objects in the package. The second
addition is the inclusion of ``pid-mapping.txt`` tag file showing the
correspondence between the persistent identifier for an object and its file
location in the bag, expressed relative to the base directory. The contents of
the file consist of one line for each data object in the bag, with each line of
the form::h6j h=h>h?hˆhA}rä (hC]hD]hE]hF]hI]uhKM§hLhhM]rå (hXX: The first addition is the presence of an OAI-ORE document ræ …rç }rè (h5X: The first addition is the presence of an OAI-ORE document h6jâ ubj )ré }rê (h5X ``oai-ore.txt``hA}rë (hC]hD]hE]hF]hI]uh6jâ hM]rì hXX oai-ore.txtrí …rî }rï (h5U h6jé ubah?j( ubhXXº within
the base directory that uses the object identifiers for DataONE objects and
describes the relationships among the objects in the package. The second
addition is the inclusion of rð …rñ }rò (h5Xº within
the base directory that uses the object identifiers for DataONE objects and
describes the relationships among the objects in the package. The second
addition is the inclusion of h6jâ ubj )ró }rô (h5X ``pid-mapping.txt``hA}rõ (hC]hD]hE]hF]hI]uh6jâ hM]rö hXX pid-mapping.txtr÷ …rø }rù (h5U h6jó ubah?j( ubhXX
tag file showing the
correspondence between the persistent identifier for an object and its file
location in the bag, expressed relative to the base directory. The contents of
the file consist of one line for each data object in the bag, with each line of
the form:rú …rû }rü (h5X
tag file showing the
correspondence between the persistent identifier for an object and its file
location in the bag, expressed relative to the base directory. The contents of
the file consist of one line for each data object in the bag, with each line of
the form:h6jâ ubeubj· )rý }rþ (h5X PID FILEPATHh6j h=h>h?jº hA}rÿ (j¼ j½ hF]hE]hC]hD]hI]uhKM°hLhhM]r hXX PID FILEPATHr …r }r (h5U h6jý ubaubhy)r }r (h5XÄ where PID is the persistent identifier for the object and FILEPATH is the path
in the bag to the file containing the bytes of the file. For example, a
typical pid-mapping.txt file might contain::h6j h=h>h?hˆhA}r (hC]hD]hE]hF]hI]uhKM²hLhhM]r hXXÃ where PID is the persistent identifier for the object and FILEPATH is the path
in the bag to the file containing the bytes of the file. For example, a
typical pid-mapping.txt file might contain:r …r }r
(h5XÃ where PID is the persistent identifier for the object and FILEPATH is the path
in the bag to the file containing the bytes of the file. For example, a
typical pid-mapping.txt file might contain:h6j ubaubj· )r }r (h5X¯ doi://10.xxxx/AA/TG43 data/data-file-1.csv
doi://10.xxxx/AA/7AW3 data/data-file-2.csv
doi://10.xxxx/AA/790I data/data-file-3.csv
doi://10.xxxx/AA/76AV data/metadata-file-1.xmlh6j h=h>h?jº hA}r
(j¼ j½ hF]hE]hC]hD]hI]uhKM¶hLhhM]r hXX¯ doi://10.xxxx/AA/TG43 data/data-file-1.csv
doi://10.xxxx/AA/7AW3 data/data-file-2.csv
doi://10.xxxx/AA/790I data/data-file-3.csv
doi://10.xxxx/AA/76AV data/metadata-file-1.xmlr …r }r (h5U h6j ubaubhy)r }r (h5X" The bag can be serialized as a single file for transport following the BagIt
specifications. Any objects that are listed in the OAI-ORE file but are missing
from the bag data directory (and therefore from the pid-mapping.txt) must be
downloaded independently via the DataONE MNRead service.r h6j h=h>h?hˆhA}r (hC]hD]hE]hF]hI]uhKM»hLhhM]r hXX" The bag can be serialized as a single file for transport following the BagIt
specifications. Any objects that are listed in the OAI-ORE file but are missing
from the bag data directory (and therefore from the pid-mapping.txt) must be
downloaded independently via the DataONE MNRead service.r …r }r (h5j h6j ubaubeubh7)r }r (h5U h6h;h=h>h?h@hA}r (hC]hD]hE]hF]r jš ahI]r h auhKMÂhLhhM]r (hO)r }r! (h5jŸ h6j h=h>h?hShA}r" (hF]hE]hC]hD]hI]hUj™ uhKMÂhLhhM]r# hXX Data Package Client Designr$ …r% }r& (h5jŸ h6j ubaubhy)r' }r( (h5X_ Although DataONE CNs and MNs will treat data as opaque, it is useful to design
clients that understand the structure of Data Packages and have a common
semantics for representing the components and their relationships. Client
applications can then be built in various analytical environments and
processing languages that allow simplified manipulation and processing of the
associated sets of objects contained in a Data Package. For example, given an
identifier for a data object, a client should be able to easily query CNs to
find the package(s) with which it is associated, and be able to easily locate
and access the other components of the package to gain an understanding of the
structure and semantics of the data object and its associated package
components. Although initially this feature would mainly be used for providing
simplified access to these components, in future versions of DataONE we
envision that the structure and semantics of each object will be clear based
on science metadata and annotations, allowing advanced data querying,
processing, and analysis on highly heterogeneous sources of data.r) h6j h=h>h?hˆhA}r* (hC]hD]hE]hF]hI]uhKMÄhLhhM]r+ hXX_ Although DataONE CNs and MNs will treat data as opaque, it is useful to design
clients that understand the structure of Data Packages and have a common
semantics for representing the components and their relationships. Client
applications can then be built in various analytical environments and
processing languages that allow simplified manipulation and processing of the
associated sets of objects contained in a Data Package. For example, given an
identifier for a data object, a client should be able to easily query CNs to
find the package(s) with which it is associated, and be able to easily locate
and access the other components of the package to gain an understanding of the
structure and semantics of the data object and its associated package
components. Although initially this feature would mainly be used for providing
simplified access to these components, in future versions of DataONE we
envision that the structure and semantics of each object will be clear based
on science metadata and annotations, allowing advanced data querying,
processing, and analysis on highly heterogeneous sources of data.r, …r- }r. (h5j) h6j' ubaubh7)r/ }r0 (h5U h6j h=h>h?h@hA}r1 (hC]hD]hE]hF]r2 j± ahI]r3 hauhKMÖhLhhM]r4 (hO)r5 }r6 (h5j¶ h6j/ h=h>h?hShA}r7 (hF]hE]hC]hD]hI]hUj° uhKMÖhLhhM]r8 hXX Classes, Fields, and Methodsr9 …r: }r; (h5j¶ h6j5 ubaubhn)r< }r= (h5U h6j/ h=h>h?hqhA}r> (jc X *hF]hE]hC]hD]hI]uhKMØhLhhM]r? (ht)r@ }rA (h5X• DataPackage
* Fields
* identifier
* D1Object[] objects
* Constructors
* DataPackage(Identifier)
* Methods
* add(DataObject): DataPackage
* size(): int
* contains(Identifier): boolean
* get(Identifier): D1Object
* remove(Identifier): void
* identifiers(): List
* getTitle(): String
* getCreator(): String
* getDisplayURL(): String
h6j< h=Nh?h hA}rB (hC]hD]hE]hF]hI]uhKNhLhhM]rC jF )rD }rE (h5U hA}rF (hC]hD]hE]hF]hI]uh6j@ hM]rG jL )rH }rI (h5X† DataPackage
* Fields
* identifier
* D1Object[] objects
* Constructors
* DataPackage(Identifier)
* Methods
* add(DataObject): DataPackage
* size(): int
* contains(Identifier): boolean
* get(Identifier): D1Object
* remove(Identifier): void
* identifiers(): List
* getTitle(): String
* getCreator(): String
* getDisplayURL(): String
h6jD h=h>h?jO hA}rJ (hC]hD]hE]hF]hI]uhKMçhM]rK (jR )rL }rM (h5X DataPackagerN h6jH h=h>h?jV hA}rO (hC]hD]hE]hF]hI]uhKMçhM]rP hXX DataPackagerQ …rR }rS (h5jN h6jL ubaubj\ )rT }rU (h5U hA}rV (hC]hD]hE]hF]hI]uh6jH hM]rW hn)rX }rY (h5U hA}rZ (jc X *hF]hE]hC]hD]hI]uh6jT hM]r[ (ht)r\ }r] (h5X, Fields
* identifier
* D1Object[] objectshA}r^ (hC]hD]hE]hF]hI]uh6jX hM]r_ jF )r` }ra (h5U hA}rb (hC]hD]hE]hF]hI]uh6j\ hM]rc jL )rd }re (h5X( Fields
* identifier
* D1Object[] objectsh6j` h=h>h?jO hA}rf (hC]hD]hE]hF]hI]uhKMÚhM]rg (jR )rh }ri (h5X Fieldsrj h6jd h=h>h?jV hA}rk (hC]hD]hE]hF]hI]uhKMÚhM]rl hXX Fieldsrm …rn }ro (h5jj h6jh ubaubj\ )rp }rq (h5U hA}rr (hC]hD]hE]hF]hI]uh6jd hM]rs hn)rt }ru (h5U hA}rv (jc X *hF]hE]hC]hD]hI]uh6jp hM]rw (ht)rx }ry (h5X
identifierrz hA}r{ (hC]hD]hE]hF]hI]uh6jt hM]r| hy)r} }r~ (h5jz h6jx h=h>h?hˆhA}r (hC]hD]hE]hF]hI]uhKMÚhM]r€ hXX
identifierr …r‚ }rƒ (h5jz h6j} ubaubah?h ubht)r„ }r… (h5X D1Object[] objectsr† hA}r‡ (hC]hD]hE]hF]hI]uh6jt hM]rˆ hy)r‰ }rŠ (h5j† h6j„ h=h>h?hˆhA}r‹ (hC]hD]hE]hF]hI]uhKMÛhM]rŒ hXX D1Object[] objectsr …rŽ }r (h5j† h6j‰ ubaubah?h ubeh?hqubah?j‰ ubeubah?jI ubah?h ubht)r }r‘ (h5X( Constructors
* DataPackage(Identifier)hA}r’ (hC]hD]hE]hF]hI]uh6jX hM]r“ jF )r” }r• (h5U hA}r– (hC]hD]hE]hF]hI]uh6j hM]r— jL )r˜ }r™ (h5X& Constructors
* DataPackage(Identifier)h6j” h=h>h?jO hA}rš (hC]hD]hE]hF]hI]uhKMÜhM]r› (jR )rœ }r (h5X Constructorsrž h6j˜ h=h>h?jV hA}rŸ (hC]hD]hE]hF]hI]uhKMÜhM]r hXX Constructorsr¡ …r¢ }r£ (h5jž h6jœ ubaubj\ )r¤ }r¥ (h5U hA}r¦ (hC]hD]hE]hF]hI]uh6j˜ hM]r§ hn)r¨ }r© (h5U hA}rª (jc X *hF]hE]hC]hD]hI]uh6j¤ hM]r« ht)r¬ }r (h5X DataPackage(Identifier)r® hA}r¯ (hC]hD]hE]hF]hI]uh6j¨ hM]r° hy)r± }r² (h5j® h6j¬ h=h>h?hˆhA}r³ (hC]hD]hE]hF]hI]uhKMÝhM]r´ hXX DataPackage(Identifier)rµ …r¶ }r· (h5j® h6j± ubaubah?h ubah?hqubah?j‰ ubeubah?jI ubah?h ubht)r¸ }r¹ (h5X Methods
* add(DataObject): DataPackage
* size(): int
* contains(Identifier): boolean
* get(Identifier): D1Object
* remove(Identifier): void
* identifiers(): List
* getTitle(): String
* getCreator(): String
* getDisplayURL(): String
hA}rº (hC]hD]hE]hF]hI]uh6jX hM]r» jF )r¼ }r½ (h5U hA}r¾ (hC]hD]hE]hF]hI]uh6j¸ hM]r¿ jL )rÀ }rÁ (h5Xô Methods
* add(DataObject): DataPackage
* size(): int
* contains(Identifier): boolean
* get(Identifier): D1Object
* remove(Identifier): void
* identifiers(): List
* getTitle(): String
* getCreator(): String
* getDisplayURL(): String
h6j¼ h=h>h?jO hA}r (hC]hD]hE]hF]hI]uhKMçhM]rà (jR )rÄ }rÅ (h5X MethodsrÆ h6jÀ h=h>h?jV hA}rÇ (hC]hD]hE]hF]hI]uhKMçhM]rÈ hXX MethodsrÉ …rÊ }rË (h5jÆ h6jÄ ubaubj\ )rÌ }rÍ (h5U hA}rÎ (hC]hD]hE]hF]hI]uh6jÀ hM]rÏ hn)rÐ }rÑ (h5U hA}rÒ (jc X *hF]hE]hC]hD]hI]uh6jÌ hM]rÓ (ht)rÔ }rÕ (h5X add(DataObject): DataPackagerÖ hA}r× (hC]hD]hE]hF]hI]uh6jÐ hM]rØ hy)rÙ }rÚ (h5jÖ h6jÔ h=h>h?hˆhA}rÛ (hC]hD]hE]hF]hI]uhKMßhM]rÜ hXX add(DataObject): DataPackagerÝ …rÞ }rß (h5jÖ h6jÙ ubaubah?h ubht)rà }rá (h5X size(): intrâ hA}rã (hC]hD]hE]hF]hI]uh6jÐ hM]rä hy)rå }ræ (h5jâ h6jà h=h>h?hˆhA}rç (hC]hD]hE]hF]hI]uhKMàhM]rè hXX size(): intré …rê }rë (h5jâ h6jå ubaubah?h ubht)rì }rí (h5X contains(Identifier): booleanrî hA}rï (hC]hD]hE]hF]hI]uh6jÐ hM]rð hy)rñ }rò (h5jî h6jì h=h>h?hˆhA}ró (hC]hD]hE]hF]hI]uhKMáhM]rô hXX contains(Identifier): booleanrõ …rö }r÷ (h5jî h6jñ ubaubah?h ubht)rø }rù (h5X get(Identifier): D1Objectrú hA}rû (hC]hD]hE]hF]hI]uh6jÐ hM]rü hy)rý }rþ (h5jú h6jø h=h>h?hˆhA}rÿ (hC]hD]hE]hF]hI]uhKMâhM]r
hXX get(Identifier): D1Objectr
…r
}r
(h5jú h6jý ubaubah?h ubht)r
}r
(h5X remove(Identifier): voidr
hA}r
(hC]hD]hE]hF]hI]uh6jÐ hM]r
hy)r
}r
(h5j
h6j
h=h>h?hˆhA}r
(hC]hD]hE]hF]hI]uhKMãhM]r
hXX remove(Identifier): voidr
…r
}r
(h5j
h6j
ubaubah?h ubht)r
}r
(h5X identifiers(): Listr
hA}r
(hC]hD]hE]hF]hI]uh6jÐ hM]r
hy)r
}r
(h5j
h6j
h=h>h?hˆhA}r
(hC]hD]hE]hF]hI]uhKMähM]r
hXX identifiers(): Listr
…r
}r
(h5j
h6j
ubaubah?h ubht)r
}r
(h5X getTitle(): Stringr
hA}r
(hC]hD]hE]hF]hI]uh6jÐ hM]r
hy)r!
}r"
(h5j
h6j
h=h>h?hˆhA}r#
(hC]hD]hE]hF]hI]uhKMåhM]r$
hXX getTitle(): Stringr%
…r&
}r'
(h5j
h6j!
ubaubah?h ubht)r(
}r)
(h5X getCreator(): Stringr*
hA}r+
(hC]hD]hE]hF]hI]uh6jÐ hM]r,
hy)r-
}r.
(h5j*
h6j(
h=h>h?hˆhA}r/
(hC]hD]hE]hF]hI]uhKMæhM]r0
hXX getCreator(): Stringr1
…r2
}r3
(h5j*
h6j-
ubaubah?h ubht)r4
}r5
(h5X getDisplayURL(): String
hA}r6
(hC]hD]hE]hF]hI]uh6jÐ hM]r7
hy)r8
}r9
(h5X getDisplayURL(): Stringr:
h6j4
h=h>h?hˆhA}r;
(hC]hD]hE]hF]hI]uhKMçhM]r<
hXX getDisplayURL(): Stringr=
…r>
}r?
(h5j:
h6j8
ubaubah?h ubeh?hqubah?j‰ ubeubah?jI ubah?h ubeh?hqubah?j‰ ubeubah?jI ubaubht)r@
}rA
(h5Xÿ D1Object
* Fields
* SystemMetadata sysmeta (contains the Identifier for this object)
* byte[] data
* Constructors
* DataObject(Identifier)
* Methods
* getIdentifier(): Identifier
* getType(): ObjectFormat
* getSystemMetadata(): SystemMetadata
* setSystemMetadata(SystemMetadata): void
* getData(): byte[]
* setData(byte[]): void
* getDescribeList(): List
* getDescribeByList(): List
* getObsoltedByList(): List
h6j< h=Nh?h hA}rB
(hC]hD]hE]hF]hI]uhKNhLhhM]rC
jF )rD
}rE
(h5U hA}rF
(hC]hD]hE]hF]hI]uh6j@
hM]rG
jL )rH
}rI
(h5Xð D1Object
* Fields
* SystemMetadata sysmeta (contains the Identifier for this object)
* byte[] data
* Constructors
* DataObject(Identifier)
* Methods
* getIdentifier(): Identifier
* getType(): ObjectFormat
* getSystemMetadata(): SystemMetadata
* setSystemMetadata(SystemMetadata): void
* getData(): byte[]
* setData(byte[]): void
* getDescribeList(): List
* getDescribeByList(): List
* getObsoltedByList(): List
h6jD
h=h>h?jO hA}rJ
(hC]hD]hE]hF]hI]uhKMùhM]rK
(jR )rL
}rM
(h5X D1ObjectrN
h6jH
h=h>h?jV hA}rO
(hC]hD]hE]hF]hI]uhKMùhM]rP
hXX D1ObjectrQ
…rR
}rS
(h5jN
h6jL
ubaubj\ )rT
}rU
(h5U hA}rV
(hC]hD]hE]hF]hI]uh6jH
hM]rW
hn)rX
}rY
(h5U hA}rZ
(jc X *hF]hE]hC]hD]hI]uh6jT
hM]r[
(ht)r\
}r]
(h5X[ Fields
* SystemMetadata sysmeta (contains the Identifier for this object)
* byte[] datahA}r^
(hC]hD]hE]hF]hI]uh6jX
hM]r_
jF )r`
}ra
(h5U hA}rb
(hC]hD]hE]hF]hI]uh6j\
hM]rc
jL )rd
}re
(h5XW Fields
* SystemMetadata sysmeta (contains the Identifier for this object)
* byte[] datah6j`
h=h>h?jO hA}rf
(hC]hD]hE]hF]hI]uhKMëhM]rg
(jR )rh
}ri
(h5X Fieldsrj
h6jd
h=h>h?jV hA}rk
(hC]hD]hE]hF]hI]uhKMëhM]rl
hXX Fieldsrm
…rn
}ro
(h5jj
h6jh
ubaubj\ )rp
}rq
(h5U hA}rr
(hC]hD]hE]hF]hI]uh6jd
hM]rs
hn)rt
}ru
(h5U hA}rv
(jc X *hF]hE]hC]hD]hI]uh6jp
hM]rw
(ht)rx
}ry
(h5X@ SystemMetadata sysmeta (contains the Identifier for this object)rz
hA}r{
(hC]hD]hE]hF]hI]uh6jt
hM]r|
hy)r}
}r~
(h5jz
h6jx
h=h>h?hˆhA}r
(hC]hD]hE]hF]hI]uhKMëhM]r€
hXX@ SystemMetadata sysmeta (contains the Identifier for this object)r
…r‚
}rƒ
(h5jz
h6j}
ubaubah?h ubht)r„
}r…
(h5X byte[] datar†
hA}r‡
(hC]hD]hE]hF]hI]uh6jt
hM]rˆ
hy)r‰
}rŠ
(h5j†
h6j„
h=h>h?hˆhA}r‹
(hC]hD]hE]hF]hI]uhKMìhM]rŒ
hXX byte[] datar
…rŽ
}r
(h5j†
h6j‰
ubaubah?h ubeh?hqubah?j‰ ubeubah?jI ubah?h ubht)r
}r‘
(h5X' Constructors
* DataObject(Identifier)hA}r’
(hC]hD]hE]hF]hI]uh6jX
hM]r“
jF )r”
}r•
(h5U hA}r–
(hC]hD]hE]hF]hI]uh6j
hM]r—
jL )r˜
}r™
(h5X% Constructors
* DataObject(Identifier)h6j”
h=h>h?jO hA}rš
(hC]hD]hE]hF]hI]uhKMíhM]r›
(jR )rœ
}r
(h5X Constructorsrž
h6j˜
h=h>h?jV hA}rŸ
(hC]hD]hE]hF]hI]uhKMíhM]r
hXX Constructorsr¡
…r¢
}r£
(h5jž
h6jœ
ubaubj\ )r¤
}r¥
(h5U hA}r¦
(hC]hD]hE]hF]hI]uh6j˜
hM]r§
hn)r¨
}r©
(h5U hA}rª
(jc X *hF]hE]hC]hD]hI]uh6j¤
hM]r«
ht)r¬
}r
(h5X DataObject(Identifier)r®
hA}r¯
(hC]hD]hE]hF]hI]uh6j¨
hM]r°
hy)r±
}r²
(h5j®
h6j¬
h=h>h?hˆhA}r³
(hC]hD]hE]hF]hI]uhKMîhM]r´
hXX DataObject(Identifier)rµ
…r¶
}r·
(h5j®
h6j±
ubaubah?h ubah?hqubah?j‰ ubeubah?jI ubah?h ubht)r¸
}r¹
(h5XE Methods
* getIdentifier(): Identifier
* getType(): ObjectFormat
* getSystemMetadata(): SystemMetadata
* setSystemMetadata(SystemMetadata): void
* getData(): byte[]
* setData(byte[]): void
* getDescribeList(): List
* getDescribeByList(): List
* getObsoltedByList(): List
hA}rº
(hC]hD]hE]hF]hI]uh6jX
hM]r»
jF )r¼
}r½
(h5U hA}r¾
(hC]hD]hE]hF]hI]uh6j¸
hM]r¿
jL )rÀ
}rÁ
(h5X3 Methods
* getIdentifier(): Identifier
* getType(): ObjectFormat
* getSystemMetadata(): SystemMetadata
* setSystemMetadata(SystemMetadata): void
* getData(): byte[]
* setData(byte[]): void
* getDescribeList(): List
* getDescribeByList(): List
* getObsoltedByList(): List
h6j¼
h=h>h?jO hA}rÂ
(hC]hD]hE]hF]hI]uhKMùhM]rÃ
(jR )rÄ
}rÅ
(h5X MethodsrÆ
h6jÀ
h=h>h?jV hA}rÇ
(hC]hD]hE]hF]hI]uhKMùhM]rÈ
hXX MethodsrÉ
…rÊ
}rË
(h5jÆ
h6jÄ
ubaubj\ )rÌ
}rÍ
(h5U hA}rÎ
(hC]hD]hE]hF]hI]uh6jÀ
hM]rÏ
hn)rÐ
}rÑ
(h5U hA}rÒ
(jc X *hF]hE]hC]hD]hI]uh6jÌ
hM]rÓ
(ht)rÔ
}rÕ
(h5X getIdentifier(): IdentifierrÖ
hA}r×
(hC]hD]hE]hF]hI]uh6jÐ
hM]rØ
hy)rÙ
}rÚ
(h5jÖ
h6jÔ
h=h>h?hˆhA}rÛ
(hC]hD]hE]hF]hI]uhKMðhM]rÜ
hXX getIdentifier(): IdentifierrÝ
…rÞ
}rß
(h5jÖ
h6jÙ
ubaubah?h ubht)rà
}rá
(h5X getType(): ObjectFormatrâ
hA}rã
(hC]hD]hE]hF]hI]uh6jÐ
hM]rä
hy)rå
}ræ
(h5jâ
h6jà
h=h>h?hˆhA}rç
(hC]hD]hE]hF]hI]uhKMñhM]rè
hXX getType(): ObjectFormatré
…rê
}rë
(h5jâ
h6jå
ubaubah?h ubht)rì
}rí
(h5X# getSystemMetadata(): SystemMetadatarî
hA}rï
(hC]hD]hE]hF]hI]uh6jÐ
hM]rð
hy)rñ
}rò
(h5jî
h6jì
h=h>h?hˆhA}ró
(hC]hD]hE]hF]hI]uhKMòhM]rô
hXX# getSystemMetadata(): SystemMetadatarõ
…rö
}r÷
(h5jî
h6jñ
ubaubah?h ubht)rø
}rù
(h5X' setSystemMetadata(SystemMetadata): voidrú
hA}rû
(hC]hD]hE]hF]hI]uh6jÐ
hM]rü
hy)rý
}rþ
(h5jú
h6jø
h=h>h?hˆhA}rÿ
(hC]hD]hE]hF]hI]uhKMóhM]r hXX' setSystemMetadata(SystemMetadata): voidr …r }r (h5jú
h6jý
ubaubah?h ubht)r }r (h5X getData(): byte[]r hA}r (hC]hD]hE]hF]hI]uh6jÐ
hM]r hy)r }r
(h5j h6j h=h>h?hˆhA}r (hC]hD]hE]hF]hI]uhKMôhM]r hXX getData(): byte[]r
…r }r (h5j h6j ubaubah?h ubht)r }r (h5X setData(byte[]): voidr hA}r (hC]hD]hE]hF]hI]uh6jÐ
hM]r hy)r }r (h5j h6j h=h>h?hˆhA}r (hC]hD]hE]hF]hI]uhKMõhM]r hXX setData(byte[]): voidr …r }r (h5j h6j ubaubah?h ubht)r }r (h5X# getDescribeList(): Listr hA}r (hC]hD]hE]hF]hI]uh6jÐ
hM]r hy)r! }r" (h5j h6j h=h>h?hˆhA}r# (hC]hD]hE]hF]hI]uhKMöhM]r$ hXX# getDescribeList(): Listr% …r& }r' (h5j h6j! ubaubah?h ubht)r( }r) (h5X% getDescribeByList(): Listr* hA}r+ (hC]hD]hE]hF]hI]uh6jÐ
hM]r, hy)r- }r. (h5j* h6j( h=h>h?hˆhA}r/ (hC]hD]hE]hF]hI]uhKM÷hM]r0 hXX% getDescribeByList(): Listr1 …r2 }r3 (h5j* h6j- ubaubah?h ubht)r4 }r5 (h5X' getObsoltedByList(): List
hA}r6 (hC]hD]hE]hF]hI]uh6jÐ
hM]r7 hy)r8 }r9 (h5X% getObsoltedByList(): Listr: h6j4 h=h>h?hˆhA}r; (hC]hD]hE]hF]hI]uhKMøhM]r< hXX% getObsoltedByList(): Listr= …r> }r? (h5j: h6j8 ubaubah?h ubeh?hqubah?j‰ ubeubah?jI ubah?h ubeh?hqubah?j‰ ubeubah?jI ubaubeubeubh7)r@ }rA (h5U h6j h=h>h?h@hA}rB (hC]hD]hE]hF]rC jÄ ahI]rD hauhKMühLhhM]rE (hO)rF }rG (h5jÉ h6j@ h=h>h?hShA}rH (hF]hE]hC]hD]hI]hUjà uhKMühLhhM]rI hXX( Algorithm for Constructing Data PackagesrJ …rK }rL (h5jÉ h6jF ubaubhy)rM }rN (h5XÙ Constructing a data package involves taking a PID as passed to the client,
and using that PID to query the system metadata to find all associated
science metadata objects and other data objects. If the PID points at a
scimeta object, it can be used to loop through all of the data objects it
describes. If the PID points at a data object, trace back to its scimeta
object first, then populate the data package, and then loop over all
associated data objects. In pseudocode:rO h6j@ h=h>h?hˆhA}rP (hC]hD]hE]hF]hI]uhKMþhLhhM]rQ hXXÙ Constructing a data package involves taking a PID as passed to the client,
and using that PID to query the system metadata to find all associated
science metadata objects and other data objects. If the PID points at a
scimeta object, it can be used to loop through all of the data objects it
describes. If the PID points at a data object, trace back to its scimeta
object first, then populate the data package, and then loop over all
associated data objects. In pseudocode:rR …rS }rT (h5jO h6jM ubaubhn)rU }rV (h5U h6j@ h=h>h?hqhA}rW (jc X *hF]hE]hC]hD]hI]uhKMhLhhM]rX (ht)rY }rZ (h5X mn = cn.resolve(PID)r[ h6jU h=h>h?h hA}r\ (hC]hD]hE]hF]hI]uhKNhLhhM]r] hy)r^ }r_ (h5j[ h6jY h=h>h?hˆhA}r` (hC]hD]hE]hF]hI]uhKMhM]ra hXX mn = cn.resolve(PID)rb …rc }rd (h5j[ h6j^ ubaubaubht)re }rf (h5X sysmeta = getSystemMetadata(PID)rg h6jU h=h>h?h hA}rh (hC]hD]hE]hF]hI]uhKNhLhhM]ri hy)rj }rk (h5jg h6je h=h>h?hˆhA}rl (hC]hD]hE]hF]hI]uhKMhM]rm hXX sysmeta = getSystemMetadata(PID)rn …ro }rp (h5jg h6jj ubaubaubht)rq }rr (h5X switch(sysmeta.getObjectFormat())
1. case: EML or FGDC or other metadata format
a. scimeta = mn.get(PID)
b. construct DataPackage dp with sysmeta and scimeta
c. for each objid in sysmeta.getDescribes()
* mn = cn.resolve(objid)
* objsysmeta = cn.getsysmetadata(objid)
* objdata = mn.get(objid)
* construct dobj = DataObject(objid, objsysmeta, objdata)
* dp.addData(dobj)
2. case: all other objects considered data objects
a. scimetaid = sysmeta.getDescribedBy()
b. mn = cn.resolve(scimetaid)
c. scisysmeta = cn.getsystemmetadata(scimetaid)
d. scimeta = mn.get(scimetaid)
e. construct DataPackage dp with scisysmeta and scimeta
f. objdata = mn.get(objid)
g. construct dobj = DataObject(ID, sysmeta, objdata)
h. follow step 1.3 above to get remainder of data objects in package
h6jU h=Nh?h hA}rs (hC]hD]hE]hF]hI]uhKNhLhhM]rt jF )ru }rv (h5U hA}rw (hC]hD]hE]hF]hI]uh6jq hM]rx jL )ry }rz (h5X] switch(sysmeta.getObjectFormat())
1. case: EML or FGDC or other metadata format
a. scimeta = mn.get(PID)
b. construct DataPackage dp with sysmeta and scimeta
c. for each objid in sysmeta.getDescribes()
* mn = cn.resolve(objid)
* objsysmeta = cn.getsysmetadata(objid)
* objdata = mn.get(objid)
* construct dobj = DataObject(objid, objsysmeta, objdata)
* dp.addData(dobj)
2. case: all other objects considered data objects
a. scimetaid = sysmeta.getDescribedBy()
b. mn = cn.resolve(scimetaid)
c. scisysmeta = cn.getsystemmetadata(scimetaid)
d. scimeta = mn.get(scimetaid)
e. construct DataPackage dp with scisysmeta and scimeta
f. objdata = mn.get(objid)
g. construct dobj = DataObject(ID, sysmeta, objdata)
h. follow step 1.3 above to get remainder of data objects in package
h6ju h=h>h?jO hA}r{ (hC]hD]hE]hF]hI]uhKM hM]r| (jR )r} }r~ (h5X! switch(sysmeta.getObjectFormat())r h6jy h=h>h?jV hA}r€ (hC]hD]hE]hF]hI]uhKM hM]r hXX! switch(sysmeta.getObjectFormat())r‚ …rƒ }r„ (h5j h6j} ubaubj\ )r… }r† (h5U hA}r‡ (hC]hD]hE]hF]hI]uh6jy hM]rˆ jc )r‰ }rŠ (h5U hA}r‹ (jh U.hF]hE]hC]ji U hD]hI]jj jk uh6j… hM]rŒ (ht)r }rŽ (h5Xi case: EML or FGDC or other metadata format
a. scimeta = mn.get(PID)
b. construct DataPackage dp with sysmeta and scimeta
c. for each objid in sysmeta.getDescribes()
* mn = cn.resolve(objid)
* objsysmeta = cn.getsysmetadata(objid)
* objdata = mn.get(objid)
* construct dobj = DataObject(objid, objsysmeta, objdata)
* dp.addData(dobj)
hA}r (hC]hD]hE]hF]hI]uh6j‰ hM]r jF )r‘ }r’ (h5U hA}r“ (hC]hD]hE]hF]hI]uh6j hM]r” jL )r• }r– (h5Xa case: EML or FGDC or other metadata format
a. scimeta = mn.get(PID)
b. construct DataPackage dp with sysmeta and scimeta
c. for each objid in sysmeta.getDescribes()
* mn = cn.resolve(objid)
* objsysmeta = cn.getsysmetadata(objid)
* objdata = mn.get(objid)
* construct dobj = DataObject(objid, objsysmeta, objdata)
* dp.addData(dobj)
h6j‘ h=h>h?jO hA}r— (hC]hD]hE]hF]hI]uhKMhM]r˜ (jR )r™ }rš (h5X* case: EML or FGDC or other metadata formatr› h6j• h=h>h?jV hA}rœ (hC]hD]hE]hF]hI]uhKMhM]r hXX* case: EML or FGDC or other metadata formatrž …rŸ }r (h5j› h6j™ ubaubj\ )r¡ }r¢ (h5U hA}r£ (hC]hD]hE]hF]hI]uh6j• hM]r¤ jc )r¥ }r¦ (h5U hA}r§ (jh U.hF]hE]hC]ji U hD]hI]jj U
loweralphar¨ uh6j¡ hM]r© (ht)rª }r« (h5X scimeta = mn.get(PID)r¬ hA}r (hC]hD]hE]hF]hI]uh6j¥ hM]r® hy)r¯ }r° (h5j¬ h6jª h=h>h?hˆhA}r± (hC]hD]hE]hF]hI]uhKM
hM]r² hXX scimeta = mn.get(PID)r³ …r´ }rµ (h5j¬ h6j¯ ubaubah?h ubht)r¶ }r· (h5X1 construct DataPackage dp with sysmeta and scimetar¸ hA}r¹ (hC]hD]hE]hF]hI]uh6j¥ hM]rº hy)r» }r¼ (h5j¸ h6j¶ h=h>h?hˆhA}r½ (hC]hD]hE]hF]hI]uhKM hM]r¾ hXX1 construct DataPackage dp with sysmeta and scimetar¿ …rÀ }rÁ (h5j¸ h6j» ubaubah?h ubht)r }rà (h5XÖ for each objid in sysmeta.getDescribes()
* mn = cn.resolve(objid)
* objsysmeta = cn.getsysmetadata(objid)
* objdata = mn.get(objid)
* construct dobj = DataObject(objid, objsysmeta, objdata)
* dp.addData(dobj)
hA}rÄ (hC]hD]hE]hF]hI]uh6j¥ hM]rÅ jF )rÆ }rÇ (h5U hA}rÈ (hC]hD]hE]hF]hI]uh6j hM]rÉ jL )rÊ }rË (h5XÑ for each objid in sysmeta.getDescribes()
* mn = cn.resolve(objid)
* objsysmeta = cn.getsysmetadata(objid)
* objdata = mn.get(objid)
* construct dobj = DataObject(objid, objsysmeta, objdata)
* dp.addData(dobj)
h6jÆ h=h>h?jO hA}rÌ (hC]hD]hE]hF]hI]uhKMhM]rÍ (jR )rÎ }rÏ (h5X( for each objid in sysmeta.getDescribes()rÐ h6jÊ h=h>h?jV hA}rÑ (hC]hD]hE]hF]hI]uhKMhM]rÒ hXX( for each objid in sysmeta.getDescribes()rÓ …rÔ }rÕ (h5jÐ h6jÎ ubaubj\ )rÖ }r× (h5U hA}rØ (hC]hD]hE]hF]hI]uh6jÊ hM]rÙ hn)rÚ }rÛ (h5U hA}rÜ (jc X *hF]hE]hC]hD]hI]uh6jÖ hM]rÝ (ht)rÞ }rß (h5X mn = cn.resolve(objid)rà hA}rá (hC]hD]hE]hF]hI]uh6jÚ hM]râ hy)rã }rä (h5jà h6jÞ h=h>h?hˆhA}rå (hC]hD]hE]hF]hI]uhKM
hM]ræ hXX mn = cn.resolve(objid)rç …rè }ré (h5jà h6jã ubaubah?h ubht)rê }rë (h5X% objsysmeta = cn.getsysmetadata(objid)rì hA}rí (hC]hD]hE]hF]hI]uh6jÚ hM]rî hy)rï }rð (h5jì h6jê h=h>h?hˆhA}rñ (hC]hD]hE]hF]hI]uhKMhM]rò hXX% objsysmeta = cn.getsysmetadata(objid)ró …rô }rõ (h5jì h6jï ubaubah?h ubht)rö }r÷ (h5X objdata = mn.get(objid)rø hA}rù (hC]hD]hE]hF]hI]uh6jÚ hM]rú hy)rû }rü (h5jø h6jö h=h>h?hˆhA}rý (hC]hD]hE]hF]hI]uhKMhM]rþ hXX objdata = mn.get(objid)rÿ …r }r (h5jø h6jû ubaubah?h ubht)r }r (h5X7 construct dobj = DataObject(objid, objsysmeta, objdata)r hA}r (hC]hD]hE]hF]hI]uh6jÚ hM]r hy)r }r (h5j h6j h=h>h?hˆhA}r (hC]hD]hE]hF]hI]uhKMhM]r
hXX7 construct dobj = DataObject(objid, objsysmeta, objdata)r …r }r
(h5j h6j ubaubah?h ubht)r }r (h5X dp.addData(dobj)
hA}r (hC]hD]hE]hF]hI]uh6jÚ hM]r hy)r }r (h5X dp.addData(dobj)r h6j h=h>h?hˆhA}r (hC]hD]hE]hF]hI]uhKMhM]r hXX dp.addData(dobj)r …r }r (h5j h6j ubaubah?h ubeh?hqubah?j‰ ubeubah?jI ubah?h ubeh?jf ubah?j‰ ubeubah?jI ubah?h ubht)r }r (h5X› case: all other objects considered data objects
a. scimetaid = sysmeta.getDescribedBy()
b. mn = cn.resolve(scimetaid)
c. scisysmeta = cn.getsystemmetadata(scimetaid)
d. scimeta = mn.get(scimetaid)
e. construct DataPackage dp with scisysmeta and scimeta
f. objdata = mn.get(objid)
g. construct dobj = DataObject(ID, sysmeta, objdata)
h. follow step 1.3 above to get remainder of data objects in package
hA}r (hC]hD]hE]hF]hI]uh6j‰ hM]r jF )r }r (h5U hA}r (hC]hD]hE]hF]hI]uh6j hM]r! jL )r" }r# (h5X“ case: all other objects considered data objects
a. scimetaid = sysmeta.getDescribedBy()
b. mn = cn.resolve(scimetaid)
c. scisysmeta = cn.getsystemmetadata(scimetaid)
d. scimeta = mn.get(scimetaid)
e. construct DataPackage dp with scisysmeta and scimeta
f. objdata = mn.get(objid)
g. construct dobj = DataObject(ID, sysmeta, objdata)
h. follow step 1.3 above to get remainder of data objects in package
h6j h=h>h?jO hA}r$ (hC]hD]hE]hF]hI]uhKM hM]r% (jR )r& }r' (h5X/ case: all other objects considered data objectsr( h6j" h=h>h?jV hA}r) (hC]hD]hE]hF]hI]uhKM hM]r* hXX/ case: all other objects considered data objectsr+ …r, }r- (h5j( h6j& ubaubj\ )r. }r/ (h5U hA}r0 (hC]hD]hE]hF]hI]uh6j" hM]r1 jc )r2 }r3 (h5U hA}r4 (jh U.hF]hE]hC]ji U hD]hI]jj j¨ uh6j. hM]r5 (ht)r6 }r7 (h5X$ scimetaid = sysmeta.getDescribedBy()r8 hA}r9 (hC]hD]hE]hF]hI]uh6j2 hM]r: hy)r; }r< (h5j8 h6j6 h=h>h?hˆhA}r= (hC]hD]hE]hF]hI]uhKMhM]r> hXX$ scimetaid = sysmeta.getDescribedBy()r? …r@ }rA (h5j8 h6j; ubaubah?h ubht)rB }rC (h5X mn = cn.resolve(scimetaid)rD hA}rE (hC]hD]hE]hF]hI]uh6j2 hM]rF hy)rG }rH (h5jD h6jB h=h>h?hˆhA}rI (hC]hD]hE]hF]hI]uhKMhM]rJ hXX mn = cn.resolve(scimetaid)rK …rL }rM (h5jD h6jG ubaubah?h ubht)rN }rO (h5X, scisysmeta = cn.getsystemmetadata(scimetaid)rP hA}rQ (hC]hD]hE]hF]hI]uh6j2 hM]rR hy)rS }rT (h5jP h6jN h=h>h?hˆhA}rU (hC]hD]hE]hF]hI]uhKMhM]rV hXX, scisysmeta = cn.getsystemmetadata(scimetaid)rW …rX }rY (h5jP h6jS ubaubah?h ubht)rZ }r[ (h5X scimeta = mn.get(scimetaid)r\ hA}r] (hC]hD]hE]hF]hI]uh6j2 hM]r^ hy)r_ }r` (h5j\ h6jZ h=h>h?hˆhA}ra (hC]hD]hE]hF]hI]uhKMhM]rb hXX scimeta = mn.get(scimetaid)rc …rd }re (h5j\ h6j_ ubaubah?h ubht)rf }rg (h5X4 construct DataPackage dp with scisysmeta and scimetarh hA}ri (hC]hD]hE]hF]hI]uh6j2 hM]rj hy)rk }rl (h5jh h6jf h=h>h?hˆhA}rm (hC]hD]hE]hF]hI]uhKMhM]rn hXX4 construct DataPackage dp with scisysmeta and scimetaro …rp }rq (h5jh h6jk ubaubah?h ubht)rr }rs (h5X objdata = mn.get(objid)rt hA}ru (hC]hD]hE]hF]hI]uh6j2 hM]rv hy)rw }rx (h5jt h6jr h=h>h?hˆhA}ry (hC]hD]hE]hF]hI]uhKMhM]rz hXX objdata = mn.get(objid)r{ …r| }r} (h5jt h6jw ubaubah?h ubht)r~ }r (h5X1 construct dobj = DataObject(ID, sysmeta, objdata)r€ hA}r (hC]hD]hE]hF]hI]uh6j2 hM]r‚ hy)rƒ }r„ (h5j€ h6j~ h=h>h?hˆhA}r… (hC]hD]hE]hF]hI]uhKMhM]r† hXX1 construct dobj = DataObject(ID, sysmeta, objdata)r‡ …rˆ }r‰ (h5j€ h6jƒ ubaubah?h ubht)rŠ }r‹ (h5XC follow step 1.3 above to get remainder of data objects in package
hA}rŒ (hC]hD]hE]hF]hI]uh6j2 hM]r hy)rŽ }r (h5XA follow step 1.3 above to get remainder of data objects in packager h6jŠ h=h>h?hˆhA}r‘ (hC]hD]hE]hF]hI]uhKMhM]r’ hXXA follow step 1.3 above to get remainder of data objects in packager“ …r” }r• (h5j h6jŽ ubaubah?h ubeh?jf ubah?j‰ ubeubah?jI ubah?h ubeh?jf ubah?j‰ ubeubah?jI ubaubeubeubeubh7)r– }r— (h5U h6h;h=h>h?h@hA}r˜ (hC]hD]hE]hF]r™ j× ahI]rš h auhKM hLhhM]r› (hO)rœ }r (h5jÜ h6j– h=h>h?hShA}rž (hF]hE]hC]hD]hI]hUjÖ uhKM hLhhM]rŸ hXX! Additional Packaging Technologiesr …r¡ }r¢ (h5jÜ h6jœ ubaubhy)r£ }r¤ (h5Xº A number of additional existing technologies can and have been used for
describing the linkages between science metadata, data, and system metadata.
Here we review some packaging mechanisms that are presently in use and discuss
how they are or might be used in existing systems to provide robust linkages
among the components of a data package. These packaging mechanisms were
considered but not selected, in favor of using BagIt and OAI-ORE.r¥ h6j– h=h>h?hˆhA}r¦ (hC]hD]hE]hF]hI]uhKM!hLhhM]r§ hXXº A number of additional existing technologies can and have been used for
describing the linkages between science metadata, data, and system metadata.
Here we review some packaging mechanisms that are presently in use and discuss
how they are or might be used in existing systems to provide robust linkages
among the components of a data package. These packaging mechanisms were
considered but not selected, in favor of using BagIt and OAI-ORE.r¨ …r© }rª (h5j¥ h6j£ ubaubh7)r« }r¬ (h5U h6j– h=h>h?h@hA}r (hC]hD]hE]hF]r® jî ahI]r¯ hauhKM*hLhhM]r° (hO)r± }r² (h5jó h6j« h=h>h?hShA}r³ (hF]hE]hC]hD]hI]hUjí uhKM*hLhhM]r´ hXX" Ecological Metadata Language (EML)rµ …r¶ }r· (h5jó h6j± ubaubhy)r¸ }r¹ (h5Xà The Ecological Metadata Language (EML) [EML-2010]_ is a science metadata
specification that specifically is modeled around the idea of a 'data package'
that consists of science metadata that is encoded in the EML document and one
or more data objects that can be either referenced in the the document via
external references or can be included inline in the EML document directly.
Both mechanisms are in widespread use in the ecological and environmental
science communities that use EML, although the mechanism of external
references is far more prevalent at this time (2010). EML documents are
serialized as XML documents but can include data inline if properly encoded.
Each EML document defines a top-level 'packageId' which contains the globally
unique identifier for the data package. Each EML document also describes zero
or more data entities that are drawn from a simple data model that includes
data tables, spatial raster, spatial vector, and other generic entity data
types. Each entity type in EML includes a distribution section that can be
used to include the data inline or reference an external source for the data.
External references to data are found in the 'online/url' field of the
document, and can consist of URLs, URNs, and other URIs. Within the Knowledge
Network for Biocomplexity, it is common to find references to web URLs and to
indirect digital identifiers such as DOIs and ecogrid URIs. The 'url' field
also includes an attribute that allows providers to declare the external
reference as either a 'download' url, which when resolved and dereferenced
should provide the exact byte stream of the digital object, or an
'information' url, which when resolved and dereferenced provides additional
information about the object but not the exact bytes of the object. This
latter informational type of URL often leads to an HTML description of the
object, a site-specific registration or authentication page, or some other
site-specific gateway that may provide indirect access to the data.h6j« h=h>h?hˆhA}rº (hC]hD]hE]hF]hI]uhKM,hLhhM]r» (hXX' The Ecological Metadata Language (EML) r¼ …r½ }r¾ (h5X' The Ecological Metadata Language (EML) h6j¸ ubj. )r¿ }rÀ (h5X EML-2010rÁ h6j¸ h=h>h?j2 hA}r (Ureftypej# UrefwarnˆU reftargetjÁ U refdomainj$ hF]rà Uid4rÄ ahE]hC]hD]hI]uhKM,hLhhM]rÅ hXX
[EML-2010]rÆ …rÇ }rÈ (h5U h6j¿ ubaubhXX® is a science metadata
specification that specifically is modeled around the idea of a 'data package'
that consists of science metadata that is encoded in the EML document and one
or more data objects that can be either referenced in the the document via
external references or can be included inline in the EML document directly.
Both mechanisms are in widespread use in the ecological and environmental
science communities that use EML, although the mechanism of external
references is far more prevalent at this time (2010). EML documents are
serialized as XML documents but can include data inline if properly encoded.
Each EML document defines a top-level 'packageId' which contains the globally
unique identifier for the data package. Each EML document also describes zero
or more data entities that are drawn from a simple data model that includes
data tables, spatial raster, spatial vector, and other generic entity data
types. Each entity type in EML includes a distribution section that can be
used to include the data inline or reference an external source for the data.
External references to data are found in the 'online/url' field of the
document, and can consist of URLs, URNs, and other URIs. Within the Knowledge
Network for Biocomplexity, it is common to find references to web URLs and to
indirect digital identifiers such as DOIs and ecogrid URIs. The 'url' field
also includes an attribute that allows providers to declare the external
reference as either a 'download' url, which when resolved and dereferenced
should provide the exact byte stream of the digital object, or an
'information' url, which when resolved and dereferenced provides additional
information about the object but not the exact bytes of the object. This
latter informational type of URL often leads to an HTML description of the
object, a site-specific registration or authentication page, or some other
site-specific gateway that may provide indirect access to the data.rÉ …rÊ }rË (h5X® is a science metadata
specification that specifically is modeled around the idea of a 'data package'
that consists of science metadata that is encoded in the EML document and one
or more data objects that can be either referenced in the the document via
external references or can be included inline in the EML document directly.
Both mechanisms are in widespread use in the ecological and environmental
science communities that use EML, although the mechanism of external
references is far more prevalent at this time (2010). EML documents are
serialized as XML documents but can include data inline if properly encoded.
Each EML document defines a top-level 'packageId' which contains the globally
unique identifier for the data package. Each EML document also describes zero
or more data entities that are drawn from a simple data model that includes
data tables, spatial raster, spatial vector, and other generic entity data
types. Each entity type in EML includes a distribution section that can be
used to include the data inline or reference an external source for the data.
External references to data are found in the 'online/url' field of the
document, and can consist of URLs, URNs, and other URIs. Within the Knowledge
Network for Biocomplexity, it is common to find references to web URLs and to
indirect digital identifiers such as DOIs and ecogrid URIs. The 'url' field
also includes an attribute that allows providers to declare the external
reference as either a 'download' url, which when resolved and dereferenced
should provide the exact byte stream of the digital object, or an
'information' url, which when resolved and dereferenced provides additional
information about the object but not the exact bytes of the object. This
latter informational type of URL often leads to an HTML description of the
object, a site-specific registration or authentication page, or some other
site-specific gateway that may provide indirect access to the data.h6j¸ ubeubjF )rÌ }rÍ (h5U h6j« h=Nh?jI hA}rÎ (hC]hD]hE]hF]hI]uhKNhLhhM]rÏ (jL )rÐ }rÑ (h5X3 Beneficial features
* Simple data model covering common science object types, can be extended
* Library support through XML parsers on multiple platforms
* Highly structured metadata with good validation model
* Similarity to other science metadata models allows relatively simple and
complete crosswalks
h6jÌ h=h>h?jO hA}rÒ (hC]hD]hE]hF]hI]uhKMMhM]rÓ (jR )rÔ }rÕ (h5X Beneficial featuresrÖ h6jÐ h=h>h?jV hA}r× (hC]hD]hE]hF]hI]uhKMMhM]rØ hXX Beneficial featuresrÙ …rÚ }rÛ (h5jÖ h6jÔ ubaubj\ )rÜ }rÝ (h5U hA}rÞ (hC]hD]hE]hF]hI]uh6jÐ hM]rß hn)rà }rá (h5U hA}râ (jc X *hF]hE]hC]hD]hI]uh6jÜ hM]rã (ht)rä }rå (h5XG Simple data model covering common science object types, can be extendedræ hA}rç (hC]hD]hE]hF]hI]uh6jà hM]rè hy)ré }rê (h5jæ h6jä h=h>h?hˆhA}rë (hC]hD]hE]hF]hI]uhKMIhM]rì hXXG Simple data model covering common science object types, can be extendedrí …rî }rï (h5jæ h6jé ubaubah?h ubht)rð }rñ (h5X9 Library support through XML parsers on multiple platformsrò hA}ró (hC]hD]hE]hF]hI]uh6jà hM]rô hy)rõ }rö (h5jò h6jð h=h>h?hˆhA}r÷ (hC]hD]hE]hF]hI]uhKMJhM]rø hXX9 Library support through XML parsers on multiple platformsrù …rú }rû (h5jò h6jõ ubaubah?h ubht)rü }rý (h5X5 Highly structured metadata with good validation modelrþ hA}rÿ (hC]hD]hE]hF]hI]uh6jà hM]r hy)r }r (h5jþ h6jü h=h>h?hˆhA}r (hC]hD]hE]hF]hI]uhKMKhM]r hXX5 Highly structured metadata with good validation modelr …r }r (h5jþ h6j ubaubah?h ubht)r }r (h5X] Similarity to other science metadata models allows relatively simple and
complete crosswalks
hA}r
(hC]hD]hE]hF]hI]uh6jà hM]r hy)r }r
(h5X\ Similarity to other science metadata models allows relatively simple and
complete crosswalksr h6j h=h>h?hˆhA}r (hC]hD]hE]hF]hI]uhKMLhM]r hXX\ Similarity to other science metadata models allows relatively simple and
complete crosswalksr …r }r (h5j h6j ubaubah?h ubeh?hqubah?j‰ ubeubjL )r }r (h5Xj Issues
* Large data access is inefficient (XML parsing)
* External data references are unconstrained URIs
h6jÌ h=h>h?jO hA}r (hC]hD]hE]hF]hI]uhKMQhLhhM]r (jR )r }r (h5X Issuesr h6j h=h>h?jV hA}r (hC]hD]hE]hF]hI]uhKMQhM]r hXX Issuesr …r }r (h5j h6j ubaubj\ )r }r! (h5U hA}r" (hC]hD]hE]hF]hI]uh6j hM]r# hn)r$ }r% (h5U hA}r& (jc X *hF]hE]hC]hD]hI]uh6j hM]r' (ht)r( }r) (h5X. Large data access is inefficient (XML parsing)r* hA}r+ (hC]hD]hE]hF]hI]uh6j$ hM]r, hy)r- }r. (h5j* h6j( h=h>h?hˆhA}r/ (hC]hD]hE]hF]hI]uhKMPhM]r0 hXX. Large data access is inefficient (XML parsing)r1 …r2 }r3 (h5j* h6j- ubaubah?h ubht)r4 }r5 (h5X0 External data references are unconstrained URIs
hA}r6 (hC]hD]hE]hF]hI]uh6j$ hM]r7 hy)r8 }r9 (h5X/ External data references are unconstrained URIsr: h6j4 h=h>h?hˆhA}r; (hC]hD]hE]hF]hI]uhKMQhM]r< hXX/ External data references are unconstrained URIsr= …r> }r? (h5j: h6j8 ubaubah?h ubeh?hqubah?j‰ ubeubjL )r@ }rA (h5X½ Questions
* Does the EML 'packageId' field suffice as an identifier for a DataONE data
package per se, and if so, is the EML document the equivalent of a
serialization of the package?
h6jÌ h=h>h?jO hA}rB (hC]hD]hE]hF]hI]uhKMWhLhhM]rC (jR )rD }rE (h5X QuestionsrF h6j@ h=h>h?jV hA}rG (hC]hD]hE]hF]hI]uhKMWhM]rH hXX QuestionsrI …rJ }rK (h5jF h6jD ubaubj\ )rL }rM (h5U hA}rN (hC]hD]hE]hF]hI]uh6j@ hM]rO hn)rP }rQ (h5U hA}rR (jc X *hF]hE]hC]hD]hI]uh6jL hM]rS ht)rT }rU (h5X Does the EML 'packageId' field suffice as an identifier for a DataONE data
package per se, and if so, is the EML document the equivalent of a
serialization of the package?
hA}rV (hC]hD]hE]hF]hI]uh6jP hM]rW hy)rX }rY (h5X« Does the EML 'packageId' field suffice as an identifier for a DataONE data
package per se, and if so, is the EML document the equivalent of a
serialization of the package?rZ h6jT h=h>h?hˆhA}r[ (hC]hD]hE]hF]hI]uhKMThM]r\ hXX« Does the EML 'packageId' field suffice as an identifier for a DataONE data
package per se, and if so, is the EML document the equivalent of a
serialization of the package?r] …r^ }r_ (h5jZ h6jX ubaubah?h ubah?hqubah?j‰ ubeubeubeubh7)r` }ra (h5U h6j– h=h>h?h@hA}rb (hC]hD]hE]hF]rc j ahI]rd h auhKMZhLhhM]re (hO)rf }rg (h5j h6j` h=h>h?hShA}rh (hF]hE]hC]hD]hI]hUj uhKMZhLhhM]ri hXX NetCDFrj …rk }rl (h5j h6jf ubaubhy)rm }rn (h5Xù "NetCDF is an abstraction that supports a view of data as a collection of
self-describing, portable objects that can be accessed through a simple
interface. Array values may be accessed directly, without knowing details of
how the data are stored. Auxiliary information about the data, such as what
units are used, may be stored with the data. Generic utilities and application
programs can access netCDF datasets and transform, combine, analyze, or
display specified fields of the data." (NetCDF User's Guide, 2010, section
1.1, [NETCDF-2010]_) NetCDF is a self-describing data representation format
developed by Unidata that is commonly used in the atmospheric and
oceanographic communities. This data model is very similar to other existing
data models such as the OPeNDAP model and the Hierarchical Data Format (HDF).
NetCDF is self-describing in that it provides a mechanism for including
metadata about the included data directly in the serialized representation.
Many users of the format have standardized upon the use of CF (Climate Format)
metadata attributes for the representation of science metadata, although this
is not strictly required by NetCDF and many other ad-hoc approaches to
metadata provision are commonly employed by users in the community as well.h6j` h=h>h?hˆhA}ro (hC]hD]hE]hF]hI]uhKM\hLhhM]rp (hXX "NetCDF is an abstraction that supports a view of data as a collection of
self-describing, portable objects that can be accessed through a simple
interface. Array values may be accessed directly, without knowing details of
how the data are stored. Auxiliary information about the data, such as what
units are used, may be stored with the data. Generic utilities and application
programs can access netCDF datasets and transform, combine, analyze, or
display specified fields of the data." (NetCDF User's Guide, 2010, section
1.1, rq …rr }rs (h5X "NetCDF is an abstraction that supports a view of data as a collection of
self-describing, portable objects that can be accessed through a simple
interface. Array values may be accessed directly, without knowing details of
how the data are stored. Auxiliary information about the data, such as what
units are used, may be stored with the data. Generic utilities and application
programs can access netCDF datasets and transform, combine, analyze, or
display specified fields of the data." (NetCDF User's Guide, 2010, section
1.1, h6jm ubj. )rt }ru (h5X NETCDF-2010rv h6jm h=h>h?j2 hA}rw (Ureftypej# UrefwarnˆU reftargetjv U refdomainj$ hF]rx Uid5ry ahE]hC]hD]hI]uhKM\hLhhM]rz hXX
[NETCDF-2010]r{ …r| }r} (h5U h6jt ubaubhXXÙ ) NetCDF is a self-describing data representation format
developed by Unidata that is commonly used in the atmospheric and
oceanographic communities. This data model is very similar to other existing
data models such as the OPeNDAP model and the Hierarchical Data Format (HDF).
NetCDF is self-describing in that it provides a mechanism for including
metadata about the included data directly in the serialized representation.
Many users of the format have standardized upon the use of CF (Climate Format)
metadata attributes for the representation of science metadata, although this
is not strictly required by NetCDF and many other ad-hoc approaches to
metadata provision are commonly employed by users in the community as well.r~ …r }r€ (h5XÙ ) NetCDF is a self-describing data representation format
developed by Unidata that is commonly used in the atmospheric and
oceanographic communities. This data model is very similar to other existing
data models such as the OPeNDAP model and the Hierarchical Data Format (HDF).
NetCDF is self-describing in that it provides a mechanism for including
metadata about the included data directly in the serialized representation.
Many users of the format have standardized upon the use of CF (Climate Format)
metadata attributes for the representation of science metadata, although this
is not strictly required by NetCDF and many other ad-hoc approaches to
metadata provision are commonly employed by users in the community as well.h6jm ubeubjF )r }r‚ (h5U h6j` h=Nh?jI hA}rƒ (hC]hD]hE]hF]hI]uhKNhLhhM]r„ (jL )r… }r† (h5X» Beneficial features
* Rich data model
* Efficient (random) access to large data contents
* Extensive library support, including for parallel systems
* Efficient storage via binary format
h6j h=h>h?jO hA}r‡ (hC]hD]hE]hF]hI]uhKMrhM]rˆ (jR )r‰ }rŠ (h5X Beneficial featuresr‹ h6j… h=h>h?jV hA}rŒ (hC]hD]hE]hF]hI]uhKMrhM]r hXX Beneficial featuresrŽ …r }r (h5j‹ h6j‰ ubaubj\ )r‘ }r’ (h5U hA}r“ (hC]hD]hE]hF]hI]uh6j… hM]r” hn)r• }r– (h5U hA}r— (jc X *hF]hE]hC]hD]hI]uh6j‘ hM]r˜ (ht)r™ }rš (h5X Rich data modelr› hA}rœ (hC]hD]hE]hF]hI]uh6j• hM]r hy)rž }rŸ (h5j› h6j™ h=h>h?hˆhA}r (hC]hD]hE]hF]hI]uhKMohM]r¡ hXX Rich data modelr¢ …r£ }r¤ (h5j› h6jž ubaubah?h ubht)r¥ }r¦ (h5X0 Efficient (random) access to large data contentsr§ hA}r¨ (hC]hD]hE]hF]hI]uh6j• hM]r© hy)rª }r« (h5j§ h6j¥ h=h>h?hˆhA}r¬ (hC]hD]hE]hF]hI]uhKMphM]r hXX0 Efficient (random) access to large data contentsr® …r¯ }r° (h5j§ h6jª ubaubah?h ubht)r± }r² (h5X9 Extensive library support, including for parallel systemsr³ hA}r´ (hC]hD]hE]hF]hI]uh6j• hM]rµ hy)r¶ }r· (h5j³ h6j± h=h>h?hˆhA}r¸ (hC]hD]hE]hF]hI]uhKMqhM]r¹ hXX9 Extensive library support, including for parallel systemsrº …r» }r¼ (h5j³ h6j¶ ubaubah?h ubht)r½ }r¾ (h5X$ Efficient storage via binary format
hA}r¿ (hC]hD]hE]hF]hI]uh6j• hM]rÀ hy)rÁ }r (h5X# Efficient storage via binary formatrà h6j½ h=h>h?hˆhA}rÄ (hC]hD]hE]hF]hI]uhKMrhM]rÅ hXX# Efficient storage via binary formatrÆ …rÇ }rÈ (h5jà h6jÁ ubaubah?h ubeh?hqubah?j‰ ubeubjL )rÉ }rÊ (h5X5 Issues
* Opaque binary format reduces long-term effectiveness for preservation
* Unspecified science metadata requirements (ad hoc community adoption)
* NetCDF actually represents multiple data models and multiple file formats,
all of which are called NetCDF even though they are different binary
formats
h6j h=h>h?jO hA}rË (hC]hD]hE]hF]hI]uhKMyhLhhM]rÌ (jR )rÍ }rÎ (h5X IssuesrÏ h6jÉ h=h>h?jV hA}rÐ (hC]hD]hE]hF]hI]uhKMyhM]rÑ hXX IssuesrÒ …rÓ }rÔ (h5jÏ h6jÍ ubaubj\ )rÕ }rÖ (h5U hA}r× (hC]hD]hE]hF]hI]uh6jÉ hM]rØ hn)rÙ }rÚ (h5U hA}rÛ (jc X *hF]hE]hC]hD]hI]uh6jÕ hM]rÜ (ht)rÝ }rÞ (h5XE Opaque binary format reduces long-term effectiveness for preservationrß hA}rà (hC]hD]hE]hF]hI]uh6jÙ hM]rá hy)râ }rã (h5jß h6jÝ h=h>h?hˆhA}rä (hC]hD]hE]hF]hI]uhKMuhM]rå hXXE Opaque binary format reduces long-term effectiveness for preservationræ …rç }rè (h5jß h6jâ ubaubah?h ubht)ré }rê (h5XE Unspecified science metadata requirements (ad hoc community adoption)rë hA}rì (hC]hD]hE]hF]hI]uh6jÙ hM]rí hy)rî }rï (h5jë h6jé h=h>h?hˆhA}rð (hC]hD]hE]hF]hI]uhKMvhM]rñ hXXE Unspecified science metadata requirements (ad hoc community adoption)rò …ró }rô (h5jë h6jî ubaubah?h ubht)rõ }rö (h5X˜ NetCDF actually represents multiple data models and multiple file formats,
all of which are called NetCDF even though they are different binary
formats
hA}r÷ (hC]hD]hE]hF]hI]uh6jÙ hM]rø hy)rù }rú (h5X— NetCDF actually represents multiple data models and multiple file formats,
all of which are called NetCDF even though they are different binary
formatsrû h6jõ h=h>h?hˆhA}rü (hC]hD]hE]hF]hI]uhKMwhM]rý hXX— NetCDF actually represents multiple data models and multiple file formats,
all of which are called NetCDF even though they are different binary
formatsrþ …rÿ }r (h5jû h6jù ubaubah?h ubeh?hqubah?j‰ ubeubjL )r }r (h5X# Questions
* Does the spec allow for externally referenced data objects?
* What mechanisms are available for providing identifiers that are used to
reference all of the components of the data package?
* What are the proper namespace names for the various NetCDF models and file
formats?
h6j h=h>h?jO hA}r (hC]hD]hE]hF]hI]uhKMhLhhM]r (jR )r }r (h5X Questionsr h6j h=h>h?jV hA}r (hC]hD]hE]hF]hI]uhKMhM]r hXX Questionsr
…r }r (h5j h6j ubaubj\ )r
}r (h5U hA}r (hC]hD]hE]hF]hI]uh6j hM]r hn)r }r (h5U hA}r (jc X *hF]hE]hC]hD]hI]uh6j
hM]r (ht)r }r (h5X; Does the spec allow for externally referenced data objects?r hA}r (hC]hD]hE]hF]hI]uh6j hM]r hy)r }r (h5j h6j h=h>h?hˆhA}r (hC]hD]hE]hF]hI]uhKM|hM]r hXX; Does the spec allow for externally referenced data objects?r …r }r (h5j h6j ubaubah?h ubht)r! }r" (h5X} What mechanisms are available for providing identifiers that are used to
reference all of the components of the data package?hA}r# (hC]hD]hE]hF]hI]uh6j hM]r$ hy)r% }r& (h5X} What mechanisms are available for providing identifiers that are used to
reference all of the components of the data package?r' h6j! h=h>h?hˆhA}r( (hC]hD]hE]hF]hI]uhKM}hM]r) hXX} What mechanisms are available for providing identifiers that are used to
reference all of the components of the data package?r* …r+ }r, (h5j' h6j% ubaubah?h ubht)r- }r. (h5XU What are the proper namespace names for the various NetCDF models and file
formats?
hA}r/ (hC]hD]hE]hF]hI]uh6j hM]r0 hy)r1 }r2 (h5XS What are the proper namespace names for the various NetCDF models and file
formats?r3 h6j- h=h>h?hˆhA}r4 (hC]hD]hE]hF]hI]uhKMhM]r5 hXXS What are the proper namespace names for the various NetCDF models and file
formats?r6 …r7 }r8 (h5j3 h6j1 ubaubah?h ubeh?hqubah?j‰ ubeubeubeubeubh8eubh=h>h?h@hA}r9 (hC]r: X
referencesr; ahD]hE]hF]r< j ahI]uhKM„hLhhM]r= (hO)r> }r? (h5j h6h8h=h>h?hShA}r@ (hF]hE]hC]hD]hI]hUj uhKM„hLhhM]rA hXX
ReferencesrB …rC }rD (h5j h6j> ubaubcdocutils.nodes
citation
rE )rF }rG (h5XÆ Boyko, A., Kunze, J., Littman, J., Madden, L., Vargas, B. (2009). The BagIt File
Packaging Format (V0.96). Retrieved April 2, 2010, from
http://www.ietf.org/Internet-drafts/draft-kunze-bagit-04.txt
jˆ Kh6h8h=h>h?j# hA}rH (hC]hD]hE]rI j0 ahF]rJ U
boyko-2009rK ahI]rL hauhKM†hLhhM]rM (cdocutils.nodes
label
rN )rO }rP (h5X
Boyko-2009hA}rQ (hC]hD]hE]hF]hI]uh6jF hM]rR hXX
Boyko-2009rS …rT }rU (h5U h6jO ubah?UlabelrV ubhy)rW }rX (h5XÅ Boyko, A., Kunze, J., Littman, J., Madden, L., Vargas, B. (2009). The BagIt File
Packaging Format (V0.96). Retrieved April 2, 2010, from
http://www.ietf.org/Internet-drafts/draft-kunze-bagit-04.txth6jF h=h>h?hˆhA}rY (hC]hD]hE]hF]hI]uhKM†hM]rZ (hXX‰ Boyko, A., Kunze, J., Littman, J., Madden, L., Vargas, B. (2009). The BagIt File
Packaging Format (V0.96). Retrieved April 2, 2010, from
r[ …r\ }r] (h5X‰ Boyko, A., Kunze, J., Littman, J., Madden, L., Vargas, B. (2009). The BagIt File
Packaging Format (V0.96). Retrieved April 2, 2010, from
h6jW ubh~)r^ }r_ (h5X< http://www.ietf.org/Internet-drafts/draft-kunze-bagit-04.txtr` hA}ra (Urefurij` hF]hE]hC]hD]hI]uh6jW hM]rb hXX< http://www.ietf.org/Internet-drafts/draft-kunze-bagit-04.txtrc …rd }re (h5U h6j^ ubah?h‡ubeubeubjE )rf }rg (h5Xs ___________. (2010). Ecological Metadata Language (EML) Specification.
http://knb.ecoinformatics.org/software/eml/
jˆ Kh6h8h=h>h?j# hA}rh (hC]hD]hE]ri jÄ ahF]rj Ueml-2010rk ahI]rl h&auhKMŠhLhhM]rm (jN )rn }ro (h5X EML-2010hA}rp (hC]hD]hE]hF]hI]uh6jf hM]rq hXX EML-2010rr …rs }rt (h5U h6jn ubah?jV ubhy)ru }rv (h5Xr ___________. (2010). Ecological Metadata Language (EML) Specification.
http://knb.ecoinformatics.org/software/eml/h6jf h=h>h?hˆhA}rw (hC]hD]hE]hF]hI]uhKMŠhM]rx (hXXG ___________. (2010). Ecological Metadata Language (EML) Specification.
ry …rz }r{ (h5XG ___________. (2010). Ecological Metadata Language (EML) Specification.
h6ju ubh~)r| }r} (h5X+ http://knb.ecoinformatics.org/software/eml/r~ hA}r (Urefurij~ hF]hE]hC]hD]hI]uh6ju hM]r€ hXX+ http://knb.ecoinformatics.org/software/eml/r …r‚ }rƒ (h5U h6j| ubah?h‡ubeubeubjE )r„ }r… (h5Xõ Lagoze, C., Van de Sompel, H., Johnston, P., Nelson,
M., Sanderson, R., Warner, S. (2008). Open Archives Initiative Object Reuse
and Exchange: ORE User Guide - Primer. Retrieved November 1, 2010, from
http://www.openarchives.org/ore/1.0/primer.
jˆ Kh6h8h=h>h?j# hA}r† (hC]hD]hE]r‡ j& ahF]rˆ U lagoze-2008r‰ ahI]rŠ h auhKMhLhhM]r‹ (jN )rŒ }r (h5X Lagoze-2008hA}rŽ (hC]hD]hE]hF]hI]uh6j„ hM]r hXX Lagoze-2008r …r‘ }r’ (h5U h6jŒ ubah?jV ubhy)r“ }r” (h5Xô Lagoze, C., Van de Sompel, H., Johnston, P., Nelson,
M., Sanderson, R., Warner, S. (2008). Open Archives Initiative Object Reuse
and Exchange: ORE User Guide - Primer. Retrieved November 1, 2010, from
http://www.openarchives.org/ore/1.0/primer.h6j„ h=h>h?hˆhA}r• (hC]hD]hE]hF]hI]uhKMhM]r– (hXXÉ Lagoze, C., Van de Sompel, H., Johnston, P., Nelson,
M., Sanderson, R., Warner, S. (2008). Open Archives Initiative Object Reuse
and Exchange: ORE User Guide - Primer. Retrieved November 1, 2010, from
r— …r˜ }r™ (h5XÉ Lagoze, C., Van de Sompel, H., Johnston, P., Nelson,
M., Sanderson, R., Warner, S. (2008). Open Archives Initiative Object Reuse
and Exchange: ORE User Guide - Primer. Retrieved November 1, 2010, from
h6j“ ubh~)rš }r› (h5X* http://www.openarchives.org/ore/1.0/primerrœ hA}r (Urefurijœ hF]hE]hC]hD]hI]uh6j“ hM]rž hXX* http://www.openarchives.org/ore/1.0/primerrŸ …r }r¡ (h5U h6jš ubah?h‡ubhXX .…r¢ }r£ (h5X .h6j“ ubeubeubjE )r¤ }r¥ (h5Xd ____________. (2010). NetCDF Users' Guide.
http://www.unidata.ucar.edu/software/netcdf/docs/netcdf/
jˆ Kh6h8h=h>h?j# hA}r¦ (hC]hD]hE]r§ jy ahF]r¨ U netcdf-2010r© ahI]rª h-auhKM’hLhhM]r« (jN )r¬ }r (h5X NETCDF-2010hA}r® (hC]hD]hE]hF]hI]uh6j¤ hM]r¯ hXX NETCDF-2010r° …r± }r² (h5U h6j¬ ubah?jV ubhy)r³ }r´ (h5Xc ____________. (2010). NetCDF Users' Guide.
http://www.unidata.ucar.edu/software/netcdf/docs/netcdf/h6j¤ h=h>h?hˆhA}rµ (hC]hD]hE]hF]hI]uhKM’hM]r¶ (hXX+ ____________. (2010). NetCDF Users' Guide.
r· …r¸ }r¹ (h5X+ ____________. (2010). NetCDF Users' Guide.
h6j³ ubh~)rº }r» (h5X8 http://www.unidata.ucar.edu/software/netcdf/docs/netcdf/r¼ hA}r½ (Urefurij¼ hF]hE]hC]hD]hI]uh6j³ hM]r¾ hXX8 http://www.unidata.ucar.edu/software/netcdf/docs/netcdf/r¿ …rÀ }rÁ (h5U h6jº ubah?h‡ubeubeubjE )r }rà (h5X Sauermann, L, Cyganiak, R. (2008). Cool URIs for the Semantic Web. W3C Interest Group Note 03
December 2008. http://www.w3.org/TR/cooluris/
jˆ Kh6h8h=h>h?j# hA}rÄ (hC]hD]hE]rÅ j> ahF]rÆ Usauermann-cyganiak-2008rÇ ahI]rÈ h auhKM•hLhhM]rÉ (jN )rÊ }rË (h5X Sauermann_Cyganiak-2008hA}rÌ (hC]hD]hE]hF]hI]uh6j hM]rÍ hXX Sauermann_Cyganiak-2008rÎ …rÏ }rÐ (h5U h6jÊ ubah?jV ubhy)rÑ }rÒ (h5XŒ Sauermann, L, Cyganiak, R. (2008). Cool URIs for the Semantic Web. W3C Interest Group Note 03
December 2008. http://www.w3.org/TR/cooluris/h6j h=h>h?hˆhA}rÓ (hC]hD]hE]hF]hI]uhKM•hM]rÔ (hXXn Sauermann, L, Cyganiak, R. (2008). Cool URIs for the Semantic Web. W3C Interest Group Note 03
December 2008. rÕ …rÖ }r× (h5Xn Sauermann, L, Cyganiak, R. (2008). Cool URIs for the Semantic Web. W3C Interest Group Note 03
December 2008. h6jÑ ubh~)rØ }rÙ (h5X http://www.w3.org/TR/cooluris/rÚ hA}rÛ (UrefurijÚ hF]hE]hC]hD]hI]uh6jÑ hM]rÜ hXX http://www.w3.org/TR/cooluris/rÝ …rÞ }rß (h5U h6jØ ubah?h‡ubeubeubjÓ )rà }rá (h5XY .. _Foresite python library: http://code.google.com/p/foresite-toolkit/wiki/PythonLibraryh:Kh6h8h=h>h?jÖ hA}râ (jŠ j
hF]rã Uforesite-python-libraryrä ahE]hC]hD]hI]rå h#auhKM˜hLhhM]ubjÓ )ræ }rç (h5X- .. _Cool URIs: http://www.w3.org/TR/cooluris/h:Kh6h8h=h>h?jÖ hA}rè (jŠ j1 hF]ré U cool-urisrê ahE]hC]hD]hI]rë hauhKMšhLhhM]ubeubh=h>h?Usystem_messagerì hA}rí (hC]UlevelKhF]hE]rî j aUsourceh>hD]hI]UlineM„UtypeUINFOrï uhKM„hLhhM]rð hy)rñ }rò (h5X- Duplicate implicit target name: "references".hA}ró (hC]hD]hE]hF]hI]uh6h3hM]rô hXX- Duplicate implicit target name: "references".rõ …rö }r÷ (h5U h6jñ ubah?hˆubaubaUcurrent_sourcerø NU
decorationrù NUautofootnote_startrú KUnameidsrû }rü (hjê hj( hhHh jñ
h
jt h j‰ h j× h
hdhj‡ hhþhhØhj hj; hjß hjî hj hj± hjÄ hjß
hh®hj hjK h jý
h jÇ h hÅh j h jš h!jå
h"jÙ h#jä h$jN h%hšh&jk h'ja h(jë
h)hëh*j h+j÷
h,j h-j© uhM]rý h;ah5U U transformerrþ NU
footnote_refsrÿ }r Urefnamesr }r (X eml-2010r ]r cdocutils.nodes
citation_reference
r )r }r (h5X [EML-2010]_jˆ Kh6j¸ h?Ucitation_referencer hA}r (hF]r
jÄ ahE]hC]hD]hI]hUjk uhM]r hXX EML-2010r …r
}r (h5U h6j ubaubaX oai-ore]r j† aj ]r j aX foresite python library]r jŠ
aX cool uris]r (j. jò ejð ]r jí ajN ]r jK aX isrequiredby]r jù aX netcdf-2010r ]r j )r }r (h5X [NETCDF-2010]_jˆ Kh6jm h?j hA}r (hF]r jy ahE]hC]hD]hI]hUj© uhM]r hXX NETCDF-2010r …r }r (h5U h6j ubaubaX ore vocabulary document]r jÉ ajÙ ]r! jÖ aX
boyko-2009r" ]r# j )r$ }r% (h5X
[Boyko-2009]_jˆ Kh6j$ h?j hA}r& (hF]r' j0 ahE]hC]hD]hI]hUjK uhM]r( hXX
Boyko-2009r) …r* }r+ (h5U h6j$ ubaubaX cito]r, (j! jj eX isreferencedby]r- jâ ajü ]r. (jù jN
eX lagoze-2008r/ ]r0 j )r1 }r2 (h5X [Lagoze-2008]_jˆ Kh6j h?j hA}r3 (hF]r4 j& ahE]hC]hD]hI]hUj‰ uhM]r5 hXX Lagoze-2008r6 …r7 }r8 (h5U h6j1 ubaubaX sauermann_cyganiak-2008r9 ]r: j )r; }r< (h5X [Sauermann_Cyganiak-2008]_jˆ Kh6j h?j hA}r= (hF]r> j> ahE]hC]hD]hI]hUjÇ uhM]r? hXX Sauermann_Cyganiak-2008r@ …rA }rB (h5U h6j; ubaubaX datacite2rdf]rC j auUsymbol_footnotesrD ]rE Uautofootnote_refsrF ]rG Usymbol_footnote_refsrH ]rI U citationsrJ ]rK (jF jf j„ j¤ j ehLhU current_linerL NUtransform_messagesrM ]rN h2)rO }rP (h5U hA}rQ (hC]UlevelKhF]hE]Usourceh>hD]hI]UlineMPUtypejï uhM]rR hy)rS }rT (h5U hA}rU (hC]hD]hE]hF]hI]uh6jO hM]rV hXX0 Hyperlink target "conformsto" is not referenced.rW …rX }rY (h5U h6jS ubah?hˆubah?jì ubaUreporterrZ NUid_startr[ K U
autofootnotesr\ ]r] U
citation_refsr^ }r_ (j" ]r` j$ aj/ ]ra j1 aj ]rb j aj9 ]rc j; aj ]rd j auUindirect_targetsre ]rf Usettingsrg (cdocutils.frontend
Values
rh ori }rj (Ufootnote_backlinksrk KUrecord_dependenciesrl NU rfc_base_urlrm U https://tools.ietf.org/html/rn U tracebackro ˆUpep_referencesrp NUstrip_commentsrq NU
toc_backlinksrr jw U
language_coders Uenrt U datestampru NU report_levelrv KU _destinationrw NU
halt_levelrx KU
strip_classesry NhSNU error_encoding_error_handlerrz Ubackslashreplacer{ Udebugr| NUembed_stylesheetr} ‰U output_encoding_error_handlerr~ Ustrictr U
sectnum_xformr€ KUdump_transformsr NU
docinfo_xformr‚ KUwarning_streamrƒ NUpep_file_url_templater„ Upep-%04dr… Uexit_status_levelr† KUconfigr‡ NUstrict_visitorrˆ NUcloak_email_addressesr‰ ˆU trim_footnote_reference_spacerŠ ‰Uenvr‹ NUdump_pseudo_xmlrŒ NUexpose_internalsr NUsectsubtitle_xformrŽ ‰U source_linkr NUrfc_referencesr NUoutput_encodingr‘ Uutf-8r’ U
source_urlr“ NUinput_encodingr” U utf-8-sigr• U_disable_configr– NU id_prefixr— U U tab_widthr˜ KUerror_encodingr™ UUTF-8rš U_sourcer› h>Ugettext_compactrœ ˆU generatorr NUdump_internalsrž NU smart_quotesrŸ ‰U pep_base_urlr U https://www.python.org/dev/peps/r¡ Usyntax_highlightr¢ Ulongr£ U input_encoding_error_handlerr¤ j Uauto_id_prefixr¥ Uidr¦ Udoctitle_xformr§ ‰Ustrip_elements_with_classesr¨ NU
_config_filesr© ]Ufile_insertion_enabledrª ˆU raw_enabledr« KU
dump_settingsr¬ NubUsymbol_footnote_startr K Uidsr® }r¯ (j( jB hHh;j‡ j j; jS jÇ j jë
jç
jt jv
hÅjï jš j j™ j• j‰ j„ hdh]jM jI j j h®jú j h8j jý jÄ j jy j j> j; j0 j$ j& j1 hVhh™h•hh©hÄhÀh×hÓhêhæhýhùj j j' j# j: j6 jÖ jÒ j× j– j j jß
jÛ
j j jK jF j j jý
jù
j j5 jÄ j@ jê jæ jN j jà j¿ ja jŠ jî j« j j` j° j¬ jå
já
jÙ jÔ js jo hëj8 j÷
jó
jÆ
jÂ
j± j/ j jü jí jé hšj jk jf jß jÛ jä jà j` j\ jñ
jí
j† j‚ j j hþj hØj j jÿ
j© j¤ uUsubstitution_namesr° }r± h?hLhA}r² (hC]hF]hE]Usourceh>hD]hI]uU footnotesr³ ]r´ Urefidsrµ }r¶ ub.