Äcdocutils.nodes
document
q
)Åq}q(U	nametypesq}q(X���roadmapqNX���version numberingqNX���implementation roadmapqNX���year 1q	NX	���years 3-5q
NX���year 2qNuUsubstitution_defsq}q
Uparse_messagesq]qUcurrent_sourceqNU
decorationqNUautofootnote_startqK
Unameidsq}q(hUroadmapqhUversion-numberingqhUimplementation-roadmapqh	Uyear-1qh
U	years-3-5qhUyear-2quUchildrenq]qcdocutils.nodes
section
q)Åq}q(U	rawsourceq U�Uparentq!hUsourceq"Xk���/var/lib/jenkins/jobs/API_Documentation_trunk/workspace/api-documentation/source/implementation/roadmap.txtq#Utagnameq$Usectionq%U
attributesq&}q'(Udupnamesq(]Uclassesq)]Ubackrefsq*]Uidsq+]q,haUnamesq-]q.hauUlineq/KUdocumentq0hh]q1(cdocutils.nodes
title
q2)Åq3}q4(h X���Implementation Roadmapq5h!hh"h#h$Utitleq6h&}q7(h(]h)]h*]h+]h-]uh/Kh0hh]q8cdocutils.nodes
Text
q9X���Implementation Roadmapq:ÖÅq;}q<(h h5h!h3ubaubcdocutils.nodes
paragraph
q=)Åq>}q?(h Xç���The DataONE project has an initial lifetime of five years, starting August
2009. Over this time development will occur in three major phases:q@h!hh"h#h$U	paragraphqAh&}qB(h(]h)]h*]h+]h-]uh/Kh0hh]qCh9X��The DataONE project has an initial lifetime of five years, starting August
2009. Over this time development will occur in three major phases:qDÖÅqE}qF(h h@h!h>ubaubcdocutils.nodes
field_list
qG)ÅqH}qI(h U�h!hh"h#h$U
field_listqJh&}qK(h(]h)]h*]h+]h-]uh/Kh0hh]qL(cdocutils.nodes
field
qM)ÅqN}qO(h U�h!hHh"h#h$UfieldqPh&}qQ(h(]h)]h*]h+]h-]uh/Kh0hh]qR(cdocutils.nodes
field_name
qS)ÅqT}qU(h X���PrototypingqVh!hNh"h#h$U
field_nameqWh&}qX(h(]h)]h*]h+]h-]uh/K�h]qYh9X���PrototypingqZÖÅq[}q\(h hVh!hTubaubcdocutils.nodes
field_body
q])Åq^}q_(h X%
��August 2009 - July 2010. Prototyping activity occurred during the first year
of the project and was used to evaluate fundamental infrastructure design
decisions. Although the prototype period has passed, some prototyping
activity will continue as a mechanism for evaluating new functionality.
h&}q`(h(]h)]h*]h+]h-]uh!hNh]qah=)Åqb}qc(h X$
��August 2009 - July 2010. Prototyping activity occurred during the first year
of the project and was used to evaluate fundamental infrastructure design
decisions. Although the prototype period has passed, some prototyping
activity will continue as a mechanism for evaluating new functionality.qdh!h^h"h#h$hAh&}qe(h(]h)]h*]h+]h-]uh/K	h]qfh9X$
��August 2009 - July 2010. Prototyping activity occurred during the first year
of the project and was used to evaluate fundamental infrastructure design
decisions. Although the prototype period has passed, some prototyping
activity will continue as a mechanism for evaluating new functionality.qgÖÅqh}qi(h hdh!hbubaubah$U
field_bodyqjubeubhM)Åqk}ql(h U�h!hHh"h#h$hPh&}qm(h(]h)]h*]h+]h-]uh/Kh0hh]qn(hS)Åqo}qp(h X
���First releaseqqh!hkh"h#h$hWh&}qr(h(]h)]h*]h+]h-]uh/K�h]qsh9X
���First releaseqtÖÅqu}qv(h hqh!houbaubh])Åqw}qx(h X¯���Targeted for the end of 2011, the first public release of the infrastructure
will be labelled "version 1.0" and will support the core DataONE
functionality including replication, identifier resolution, search and
discovery, and federated identity.
h&}qy(h(]h)]h*]h+]h-]uh!hkh]qzh=)Åq{}q|(h X˜���Targeted for the end of 2011, the first public release of the infrastructure
will be labelled "version 1.0" and will support the core DataONE
functionality including replication, identifier resolution, search and
discovery, and federated identity.q}h!hwh"h#h$hAh&}q~(h(]h)]h*]h+]h-]uh/Kh]qh9X˜���Targeted for the end of 2011, the first public release of the infrastructure
will be labelled "version 1.0" and will support the core DataONE
functionality including replication, identifier resolution, search and
discovery, and federated identity.qÄÖÅqÅ}qÇ(h h}h!h{ubaubah$hjubeubhM)ÅqÉ}qÑ(h U�h!hHh"h#h$hPh&}qÖ(h(]h)]h*]h+]h-]uh/Kh0hh]qÜ(hS)Åqá}qà(h X���Second releaseqâh!hÉh"h#h$hWh&}qä(h(]h)]h*]h+]h-]uh/K�h]qãh9X���Second releaseqåÖÅqç}qé(h hâh!háubaubh])Åqè}qê(h X
��Subsequent to the first public release will be a series of minor releases
that progressively add functionality to the core infrastructure. It is
anticipated that a streamlining and refactoring process will lead to another
major release (version 2.0) towards the end of 2013.

h&}që(h(]h)]h*]h+]h-]uh!hÉh]qíh=)Åqì}qî(h X
��Subsequent to the first public release will be a series of minor releases
that progressively add functionality to the core infrastructure. It is
anticipated that a streamlining and refactoring process will lead to another
major release (version 2.0) towards the end of 2013.qïh!hèh"h#h$hAh&}qñ(h(]h)]h*]h+]h-]uh/Kh]qóh9X
��Subsequent to the first public release will be a series of minor releases
that progressively add functionality to the core infrastructure. It is
anticipated that a streamlining and refactoring process will lead to another
major release (version 2.0) towards the end of 2013.qòÖÅqô}qö(h hïh!hìubaubah$hjubeubeubh)Åqõ}qú(h U�h!hh"h#h$h%h&}qù(h(]h)]h*]h+]qûhah-]qühauh/Kh0hh]q†(h2)Åq°}q¢(h X���Version Numberingq£h!hõh"h#h$h6h&}q§(h(]h)]h*]h+]h-]uh/Kh0hh]q•h9X���Version Numberingq¶ÖÅqß}q®(h h£h!h°ubaubh=)Åq©}q™(h X
��There are many discrete products that together form the DataONE
cyberinfrastructure. Each of these products may follow their own version
steps, however the version of the infrastructure being matched should be
indicated using the DataONE cyberinfrastructure version identifier.q´h!hõh"h#h$hAh&}q¨(h(]h)]h*]h+]h-]uh/K h0hh]q≠h9X
��There are many discrete products that together form the DataONE
cyberinfrastructure. Each of these products may follow their own version
steps, however the version of the infrastructure being matched should be
indicated using the DataONE cyberinfrastructure version identifier.qÆÖÅqØ}q∞(h h´h!h©ubaubh=)Åq±}q≤(h Xw���Version numbers are expressed in three parts: Major.Minor.Revision to reflect
official releases of the software, where:q≥h!hõh"h#h$hAh&}q¥(h(]h)]h*]h+]h-]uh/K%h0hh]qµh9Xw���Version numbers are expressed in three parts: Major.Minor.Revision to reflect
official releases of the software, where:q∂ÖÅq∑}q∏(h h≥h!h±ubaubhG)Åqπ}q∫(h U�h!hõh"h#h$hJh&}qª(h(]h)]h*]h+]h-]uh/K(h0hh]qº(hM)ÅqΩ}qæ(h U�h!hπh"h#h$hPh&}qø(h(]h)]h*]h+]h-]uh/K(h0hh]q¿(hS)Åq¡}q¬(h X���Majorq√h!hΩh"h#h$hWh&}qƒ(h(]h)]h*]h+]h-]uh/K�h]q≈h9X���Majorq∆ÖÅq«}q»(h h√h!h¡ubaubh])Åq…}q (h X…���Is a significantly different release from the previous version number, may
provide significant additional features and may implement functionality that
is not backwards compatible with prior releases.
h&}qÀ(h(]h)]h*]h+]h-]uh!hΩh]qÃh=)ÅqÕ}qŒ(h X»���Is a significantly different release from the previous version number, may
provide significant additional features and may implement functionality that
is not backwards compatible with prior releases.qœh!h…h"h#h$hAh&}q–(h(]h)]h*]h+]h-]uh/K*h]q—h9X»���Is a significantly different release from the previous version number, may
provide significant additional features and may implement functionality that
is not backwards compatible with prior releases.q“ÖÅq”}q‘(h hœh!hÕubaubah$hjubeubhM)Åq’}q÷(h U�h!hπh"h#h$hPh&}q◊(h(]h)]h*]h+]h-]uh/K.h0hh]qÿ(hS)ÅqŸ}q⁄(h X���Minorq€h!h’h"h#h$hWh&}q‹(h(]h)]h*]h+]h-]uh/K�h]q›h9X���MinorqfiÖÅqfl}q‡(h h€h!hŸubaubh])Åq·}q‚(h Xn���Adds additional features to an existing release and maintains compatibility
within the current major version.
h&}q„(h(]h)]h*]h+]h-]uh!h’h]q‰h=)ÅqÂ}qÊ(h Xm���Adds additional features to an existing release and maintains compatibility
within the current major version.qÁh!h·h"h#h$hAh&}qË(h(]h)]h*]h+]h-]uh/K0h]qÈh9Xm���Adds additional features to an existing release and maintains compatibility
within the current major version.qÍÖÅqÎ}qÏ(h hÁh!hÂubaubah$hjubeubhM)ÅqÌ}qÓ(h U�h!hπh"h#h$hPh&}qÔ(h(]h)]h*]h+]h-]uh/K3h0hh]q(hS)ÅqÒ}qÚ(h X���RevisionqÛh!hÌh"h#h$hWh&}qÙ(h(]h)]h*]h+]h-]uh/K�h]qıh9X���RevisionqˆÖÅq˜}q¯(h hÛh!hÒubaubh])Åq˘}q˙(h Xè���Indicates a minor change from the current version, typically used to provide
bug fix releases. Will not usually add additional functionality.

h&}q˚(h(]h)]h*]h+]h-]uh!hÌh]q¸h=)Åq˝}q˛(h Xç���Indicates a minor change from the current version, typically used to provide
bug fix releases. Will not usually add additional functionality.qˇh!h˘h"h#h$hAh&}r�
��(h(]h)]h*]h+]h-]uh/K5h]r

��h9X��Indicates a minor change from the current version, typically used to provide
bug fix releases. Will not usually add additional functionality.r
��ÖÅr
��}r
��(h hˇh!h˝ubaubah$hjubeubeubeubh)År
��}r
��(h U�h!hh"h#h$h%h&}r
��(h(]h)]h*]h+]r
��hah-]r	
��hauh/K:h0hh]r

��(h2)År
��}r
��(h X���Roadmapr

��h!j
��h"h#h$h6h&}r
��(h(]h)]h*]h+]h-]uh/K:h0hh]r
��h9X���Roadmapr
��ÖÅr
��}r
��(h j

��h!j
��ubaubcdocutils.nodes
image
r
��)År
��}r
��(h X'���.. image:: images/general_schedule.png
h!j
��h"h#h$Uimager
��h&}r
��(UuriX*���implementation/images/general_schedule.pngr
��h+]h*]h(]h)]U
candidatesr
��}r
��U
*j
��sh-]uh/K=h0hh]ubh=)År
��}r
��(h XÂ
��*Figure 1.* Generalized plan for cyberinfrastructure development activities
over the first five years of DataONE, indicating a gradual shift from design
and significant blocks of implementation activity to adding value through
expansion of services (e.g., semantic mediation services) and addition of
content (e.g., new Member Nodes) and features such as the integration of new
tools in the Investigator Toolkit. Shaded bars indicate emphasis of activity;
diamonds indicate milestones.h!j
��h"h#h$hAh&}r
��(h(]h)]h*]h+]h-]uh/K>h0hh]r
��(cdocutils.nodes
emphasis
r
��)År 
��}r!
��(h X���*Figure 1.*h&}r"
��(h(]h)]h*]h+]h-]uh!j
��h]r#
��h9X	���Figure 1.r$
��ÖÅr%
��}r&
��(h U�h!j 
��ubah$Uemphasisr'
��ubh9X⁄
�� Generalized plan for cyberinfrastructure development activities
over the first five years of DataONE, indicating a gradual shift from design
and significant blocks of implementation activity to adding value through
expansion of services (e.g., semantic mediation services) and addition of
content (e.g., new Member Nodes) and features such as the integration of new
tools in the Investigator Toolkit. Shaded bars indicate emphasis of activity;
diamonds indicate milestones.r(
��ÖÅr)
��}r*
��(h X⁄
�� Generalized plan for cyberinfrastructure development activities
over the first five years of DataONE, indicating a gradual shift from design
and significant blocks of implementation activity to adding value through
expansion of services (e.g., semantic mediation services) and addition of
content (e.g., new Member Nodes) and features such as the integration of new
tools in the Investigator Toolkit. Shaded bars indicate emphasis of activity;
diamonds indicate milestones.h!j
��ubeubh)År+
��}r,
��(h U�h!j
��h"h#h$h%h&}r-
��(h(]h)]h*]h+]r.
��hah-]r/
��h	auh/KHh0hh]r0
��(h2)År1
��}r2
��(h X���Year 1r3
��h!j+
��h"h#h$h6h&}r4
��(h(]h)]h*]h+]h-]uh/KHh0hh]r5
��h9X���Year 1r6
��ÖÅr7
��}r8
��(h j3
��h!j1
��ubaubcdocutils.nodes
bullet_list
r9
��)År:
��}r;
��(h U�h!j+
��h"h#h$Ubullet_listr<
��h&}r=
��(Ubulletr>
��X
���-h+]h*]h(]h)]h-]uh/KJh0hh]r?
��(cdocutils.nodes
list_item
r@
��)ÅrA
��}rB
��(h X���Initial design and prototyping.rC
��h!j:
��h"h#h$U	list_itemrD
��h&}rE
��(h(]h)]h*]h+]h-]uh/Nh0hh]rF
��h=)ÅrG
��}rH
��(h jC
��h!jA
��h"h#h$hAh&}rI
��(h(]h)]h*]h+]h-]uh/KJh]rJ
��h9X���Initial design and prototyping.rK
��ÖÅrL
��}rM
��(h jC
��h!jG
��ubaubaubj@
��)ÅrN
��}rO
��(h X%���Review of architecture and prototype
h!j:
��h"h#h$jD
��h&}rP
��(h(]h)]h*]h+]h-]uh/Nh0hh]rQ
��h=)ÅrR
��}rS
��(h X$���Review of architecture and prototyperT
��h!jN
��h"h#h$hAh&}rU
��(h(]h)]h*]h+]h-]uh/KKh]rV
��h9X$���Review of architecture and prototyperW
��ÖÅrX
��}rY
��(h jT
��h!jR
��ubaubaubeubeubh)ÅrZ
��}r[
��(h U�h!j
��h"h#h$h%h&}r\
��(h(]h)]h*]h+]r]
��hah-]r^
��hauh/KNh0hh]r_
��(h2)År`
��}ra
��(h X���Year 2rb
��h!jZ
��h"h#h$h6h&}rc
��(h(]h)]h*]h+]h-]uh/KNh0hh]rd
��h9X���Year 2re
��ÖÅrf
��}rg
��(h jb
��h!j`
��ubaubh=)Årh
��}ri
��(h X%
��Major activities scheduled for the remainder of year 2 include continued
evaluation of the prototype and infrastructure re-engineering as necessary to
produce a reliable core infrastructure suitable for public release
(infrastructure version 1.x) in the fall of 2011. Specific actions include:rj
��h!jZ
��h"h#h$hAh&}rk
��(h(]h)]h*]h+]h-]uh/KPh0hh]rl
��h9X%
��Major activities scheduled for the remainder of year 2 include continued
evaluation of the prototype and infrastructure re-engineering as necessary to
produce a reliable core infrastructure suitable for public release
(infrastructure version 1.x) in the fall of 2011. Specific actions include:rm
��ÖÅrn
��}ro
��(h jj
��h!jh
��ubaubj9
��)Årp
��}rq
��(h U�h!jZ
��h"h#h$j<
��h&}rr
��(j>
��X
���-h+]h*]h(]h)]h-]uh/KUh0hh]rs
��(j@
��)Årt
��}ru
��(h X%���Revision of prototype implementation
h!jp
��h"h#h$jD
��h&}rv
��(h(]h)]h*]h+]h-]uh/Nh0hh]rw
��h=)Årx
��}ry
��(h X$���Revision of prototype implementationrz
��h!jt
��h"h#h$hAh&}r{
��(h(]h)]h*]h+]h-]uh/KUh]r|
��h9X$���Revision of prototype implementationr}
��ÖÅr~
��}r
��(h jz
��h!jx
��ubaubaubj@
��)ÅrÄ
��}rÅ
��(h X®���Public release of DataONE cyberinfrastructure. Implementation of the revised
infrastructure with particular emphasis on scalable, stable, and secure core
functionality
h!jp
��h"h#h$jD
��h&}rÇ
��(h(]h)]h*]h+]h-]uh/Nh0hh]rÉ
��h=)ÅrÑ
��}rÖ
��(h X���Public release of DataONE cyberinfrastructure. Implementation of the revised
infrastructure with particular emphasis on scalable, stable, and secure core
functionalityrÜ
��h!jÄ
��h"h#h$hAh&}rá
��(h(]h)]h*]h+]h-]uh/KWh]rà
��h9X���Public release of DataONE cyberinfrastructure. Implementation of the revised
infrastructure with particular emphasis on scalable, stable, and secure core
functionalityrâ
��ÖÅrä
��}rã
��(h jÜ
��h!jÑ
��ubaubaubj@
��)Årå
��}rç
��(h XY���User documentation. Development of technical user educational materials and
ITK examples
h!jp
��h"h#h$jD
��h&}ré
��(h(]h)]h*]h+]h-]uh/Nh0hh]rè
��h=)Årê
��}rë
��(h XX���User documentation. Development of technical user educational materials and
ITK examplesrí
��h!jå
��h"h#h$hAh&}rì
��(h(]h)]h*]h+]h-]uh/K[h]rî
��h9XX���User documentation. Development of technical user educational materials and
ITK examplesrï
��ÖÅrñ
��}ró
��(h jí
��h!jê
��ubaubaubj@
��)Årò
��}rô
��(h X5
��Member Node addition. Selection of and deployment of three additional MNs,
most likely to include the National Biological Information Infrastructure
(NBII), the Consortium of Universities for the Advancement of Hydrologic
Science Hydrologic Information System (CUAHSI-HIS), and the Merritt
Repository Service
h!jp
��h"h#h$jD
��h&}rö
��(h(]h)]h*]h+]h-]uh/Nh0hh]rõ
��h=)Årú
��}rù
��(h X4
��Member Node addition. Selection of and deployment of three additional MNs,
most likely to include the National Biological Information Infrastructure
(NBII), the Consortium of Universities for the Advancement of Hydrologic
Science Hydrologic Information System (CUAHSI-HIS), and the Merritt
Repository Servicerû
��h!jò
��h"h#h$hAh&}rü
��(h(]h)]h*]h+]h-]uh/K^h]r†
��h9X4
��Member Node addition. Selection of and deployment of three additional MNs,
most likely to include the National Biological Information Infrastructure
(NBII), the Consortium of Universities for the Advancement of Hydrologic
Science Hydrologic Information System (CUAHSI-HIS), and the Merritt
Repository Servicer°
��ÖÅr¢
��}r£
��(h jû
��h!jú
��ubaubaubj@
��)År§
��}r•
��(h X3���First implementation phases of federated identity.
h!jp
��h"h#h$jD
��h&}r¶
��(h(]h)]h*]h+]h-]uh/Nh0hh]rß
��h=)År®
��}r©
��(h X2���First implementation phases of federated identity.r™
��h!j§
��h"h#h$hAh&}r´
��(h(]h)]h*]h+]h-]uh/Kdh]r¨
��h9X2���First implementation phases of federated identity.r≠
��ÖÅrÆ
��}rØ
��(h j™
��h!j®
��ubaubaubj@
��)År∞
��}r±
��(h X‹���Design specifications for specialized Member Node participation. Such nodes
would be utilized to support experimenters requiring significant
computational power, or specialized rendering or data processing
capabilities.
h!jp
��h"h#h$jD
��h&}r≤
��(h(]h)]h*]h+]h-]uh/Nh0hh]r≥
��h=)År¥
��}rµ
��(h X€���Design specifications for specialized Member Node participation. Such nodes
would be utilized to support experimenters requiring significant
computational power, or specialized rendering or data processing
capabilities.r∂
��h!j∞
��h"h#h$hAh&}r∑
��(h(]h)]h*]h+]h-]uh/Kfh]r∏
��h9X€���Design specifications for specialized Member Node participation. Such nodes
would be utilized to support experimenters requiring significant
computational power, or specialized rendering or data processing
capabilities.rπ
��ÖÅr∫
��}rª
��(h j∂
��h!j¥
��ubaubaubj@
��)Årº
��}rΩ
��(h X��Further progress on key aspects of semantic search, semantic integration and
workflow support through activities of the respective working groups.

h!jp
��h"h#h$jD
��h&}ræ
��(h(]h)]h*]h+]h-]uh/Nh0hh]rø
��h=)År¿
��}r¡
��(h X��Further progress on key aspects of semantic search, semantic integration and
workflow support through activities of the respective working groups.r¬
��h!jº
��h"h#h$hAh&}r√
��(h(]h)]h*]h+]h-]uh/Kkh]rƒ
��h9X��Further progress on key aspects of semantic search, semantic integration and
workflow support through activities of the respective working groups.r≈
��ÖÅr∆
��}r«
��(h j¬
��h!j¿
��ubaubaubeubeubh)År»
��}r…
��(h U�h!j
��h"h#h$h%h&}r 
��(h(]h)]h*]h+]r��hah-]rÃ
��h
auh/Kph0hh]rÕ
��(h2)ÅrŒ
��}rœ
��(h X	���Years 3-5r–
��h!j»
��h"h#h$h6h&}r—
��(h(]h)]h*]h+]h-]uh/Kph0hh]r“
��h9X	���Years 3-5r”
��ÖÅr‘
��}r’
��(h j–
��h!jŒ
��ubaubh=)År÷
��}r◊
��(h X@��Development activities enter a phase of incremental enhancement
(infrastructure version 2.x) following the full public release of
infrastructure, with suggestions from the DataONE Users Group (DUG) and
working groups such as the Usability and Assessment Working Group. Features
will be being assessed, prioritized, and incorporated into the infrastructure
as appropriate. This approach will ensure ongoing progression of value-added
cyberinfrastructure features for the lifetime of the project, and will also
guarantee that the implementation remains well aligned with the overall
requirements and expectations of the community as represented by the various
working groups and the DUG. Major activities expected for the version 2.x
series of infrastructure implementation (starting approximately 24 months into
the project) include:rÿ
��h!j»
��h"h#h$hAh&}rŸ
��(h(]h)]h*]h+]h-]uh/Krh0hh]r⁄
��h9X@��Development activities enter a phase of incremental enhancement
(infrastructure version 2.x) following the full public release of
infrastructure, with suggestions from the DataONE Users Group (DUG) and
working groups such as the Usability and Assessment Working Group. Features
will be being assessed, prioritized, and incorporated into the infrastructure
as appropriate. This approach will ensure ongoing progression of value-added
cyberinfrastructure features for the lifetime of the project, and will also
guarantee that the implementation remains well aligned with the overall
requirements and expectations of the community as represented by the various
working groups and the DUG. Major activities expected for the version 2.x
series of infrastructure implementation (starting approximately 24 months into
the project) include:r€
��ÖÅr‹
��}r›
��(h jÿ
��h!j÷
��ubaubj9
��)Årfi
��}rfl
��(h U�h!j»
��h"h#h$j<
��h&}r‡
��(j>
��X
���-h+]h*]h(]h)]h-]uh/Kh0hh]r·
��(j@
��)År‚
��}r„
��(h X˚���Evaluation, testing and refinement. Evaluation of the infrastructure from
computational, stability, and usability perspectives; documentation and
prioritization of changes that need to be made; enhancement and performance
tuning of core functionality
h!jfi
��h"h#h$jD
��h&}r‰
��(h(]h)]h*]h+]h-]uh/Nh0hh]rÂ
��h=)ÅrÊ
��}rÁ
��(h X˙���Evaluation, testing and refinement. Evaluation of the infrastructure from
computational, stability, and usability perspectives; documentation and
prioritization of changes that need to be made; enhancement and performance
tuning of core functionalityrË
��h!j‚
��h"h#h$hAh&}rÈ
��(h(]h)]h*]h+]h-]uh/Kh]rÍ
��h9X˙���Evaluation, testing and refinement. Evaluation of the infrastructure from
computational, stability, and usability perspectives; documentation and
prioritization of changes that need to be made; enhancement and performance
tuning of core functionalityrÎ
��ÖÅrÏ
��}rÌ
��(h jË
��h!jÊ
��ubaubaubj@
��)ÅrÓ
��}rÔ
��(h X€���Investigator Toolkit enhancement. Additions of tools to ITK to match
enhancements to core functionality and support data life cycle activities
(i.e., data collection through preservation and analysis and visualization)
h!jfi
��h"h#h$jD
��h&}r
��(h(]h)]h*]h+]h-]uh/Nh0hh]rÒ
��h=)ÅrÚ
��}rÛ
��(h X⁄���Investigator Toolkit enhancement. Additions of tools to ITK to match
enhancements to core functionality and support data life cycle activities
(i.e., data collection through preservation and analysis and visualization)rÙ
��h!jÓ
��h"h#h$hAh&}rı
��(h(]h)]h*]h+]h-]uh/KÑh]rˆ
��h9X⁄���Investigator Toolkit enhancement. Additions of tools to ITK to match
enhancements to core functionality and support data life cycle activities
(i.e., data collection through preservation and analysis and visualization)r˜
��ÖÅr¯
��}r˘
��(h jÙ
��h!jÚ
��ubaubaubj@
��)År˙
��}r˚
��(h Xû���Semantically facilitated search and discovery. Incorporation of outputs from
semantics working groups, targeting improvement of search precision and
accuracy
h!jfi
��h"h#h$jD
��h&}r¸
��(h(]h)]h*]h+]h-]uh/Nh0hh]r˝
��h=)År˛
��}rˇ
��(h Xù���Semantically facilitated search and discovery. Incorporation of outputs from
semantics working groups, targeting improvement of search precision and
accuracyr���h!j˙
��h"h#h$hAh&}r
��(h(]h)]h*]h+]h-]uh/Kàh]r��h9Xù���Semantically facilitated search and discovery. Incorporation of outputs from
semantics working groups, targeting improvement of search precision and
accuracyr��ÖÅr��}r��(h j���h!j˛
��ubaubaubj@
��)År��}r��(h XR
��Addition of specialized Member Nodes. Addition of support for specialize
node types to support operations requiring node characteristics other than
data storage. For example, computation nodes may be employed to enable
significant data processing capabilities without retrieval to the client,
therefore enabling processing close to data.
h!jfi
��h"h#h$jD
��h&}r��(h(]h)]h*]h+]h-]uh/Nh0hh]r	��h=)År
��}r��(h XQ
��Addition of specialized Member Nodes. Addition of support for specialize
node types to support operations requiring node characteristics other than
data storage. For example, computation nodes may be employed to enable
significant data processing capabilities without retrieval to the client,
therefore enabling processing close to data.r��h!j��h"h#h$hAh&}r
��(h(]h)]h*]h+]h-]uh/Kåh]r��h9XQ
��Addition of specialized Member Nodes. Addition of support for specialize
node types to support operations requiring node characteristics other than
data storage. For example, computation nodes may be employed to enable
significant data processing capabilities without retrieval to the client,
therefore enabling processing close to data.r��ÖÅr��}r��(h j��h!j
��ubaubaubj@
��)År��}r��(h Xï���New user services. Addition of data sub-setting, visualization, and
integration services, to be closely aligned with deployment of specialized
nodes
h!jfi
��h"h#h$jD
��h&}r��(h(]h)]h*]h+]h-]uh/Nh0hh]r��h=)År��}r��(h Xî���New user services. Addition of data sub-setting, visualization, and
integration services, to be closely aligned with deployment of specialized
nodesr��h!j��h"h#h$hAh&}r��(h(]h)]h*]h+]h-]uh/Kíh]r��h9Xî���New user services. Addition of data sub-setting, visualization, and
integration services, to be closely aligned with deployment of specialized
nodesr��ÖÅr��}r��(h j��h!j��ubaubaubj@
��)År��}r��(h Xñ���Global deployment of Member Nodes and Coordinating Nodes. Ongoing global
deployment of all node types, including additional CNs in Europe and Oceania
h!jfi
��h"h#h$jD
��h&}r ��(h(]h)]h*]h+]h-]uh/Nh0hh]r!��h=)År"��}r#��(h Xï���Global deployment of Member Nodes and Coordinating Nodes. Ongoing global
deployment of all node types, including additional CNs in Europe and Oceaniar$��h!j��h"h#h$hAh&}r%��(h(]h)]h*]h+]h-]uh/Kñh]r&��h9Xï���Global deployment of Member Nodes and Coordinating Nodes. Ongoing global
deployment of all node types, including additional CNs in Europe and Oceaniar'��ÖÅr(��}r)��(h j$��h!j"��ubaubaubeubeubeubeubah U�Utransformerr*��NU
footnote_refsr+��}r,��Urefnamesr-��}r.��Usymbol_footnotesr/��]r0��Uautofootnote_refsr1��]r2��Usymbol_footnote_refsr3��]r4��U	citationsr5��]r6��h0hUcurrent_liner7��NUtransform_messagesr8��]r9��Ureporterr:��NUid_startr;��K
U
autofootnotesr<��]r=��U
citation_refsr>��}r?��Uindirect_targetsr@��]rA��UsettingsrB��(cdocutils.frontend
Values
rC��orD��}rE��(Ufootnote_backlinksrF��K
Urecord_dependenciesrG��NUrfc_base_urlrH��Uhttps://tools.ietf.org/html/rI��U	tracebackrJ��àUpep_referencesrK��NUstrip_commentsrL��NU
toc_backlinksrM��UentryrN��U
language_coderO��UenrP��U	datestamprQ��NUreport_levelrR��KU_destinationrS��NU
halt_levelrT��KU
strip_classesrU��Nh6NUerror_encoding_error_handlerrV��UbackslashreplacerW��UdebugrX��NUembed_stylesheetrY��âUoutput_encoding_error_handlerrZ��Ustrictr[��U
sectnum_xformr\��K
Udump_transformsr]��NU
docinfo_xformr^��K
Uwarning_streamr_��NUpep_file_url_templater`��Upep-%04dra��Uexit_status_levelrb��KUconfigrc��NUstrict_visitorrd��NUcloak_email_addressesre��àUtrim_footnote_reference_spacerf��âUenvrg��NUdump_pseudo_xmlrh��NUexpose_internalsri��NUsectsubtitle_xformrj��âUsource_linkrk��NUrfc_referencesrl��NUoutput_encodingrm��Uutf-8rn��U
source_urlro��NUinput_encodingrp��U	utf-8-sigrq��U_disable_configrr��NU	id_prefixrs��U�U	tab_widthrt��KUerror_encodingru��UUTF-8rv��U_sourcerw��h#Ugettext_compactrx��àU	generatorry��NUdump_internalsrz��NUsmart_quotesr{��âUpep_base_urlr|��U https://www.python.org/dev/peps/r}��Usyntax_highlightr~��Ulongr��Uinput_encoding_error_handlerrÄ��j[��Uauto_id_prefixrÅ��UidrÇ��Udoctitle_xformrÉ��âUstrip_elements_with_classesrÑ��NU
_config_filesrÖ��]Ufile_insertion_enabledrÜ��àUraw_enabledrá��K
U
dump_settingsrà��NubUsymbol_footnote_startrâ��K�Uidsrä��}rã��(hj»
��hjZ
��hj+
��hj
��hhhhõuUsubstitution_namesrå��}rç��h$h0h&}ré��(h(]h+]h*]Usourceh#h)]h-]uU	footnotesrè��]rê��Urefidsrë��}rí��ub.