cdocutils.nodes document q)q}q(U nametypesq}q(XroadmapqNXversion numberingqNXimplementation roadmapqNXyear 1q NX years 3-5q NXyear 2q NuUsubstitution_defsq }q Uparse_messagesq]qUcurrent_sourceqNU decorationqNUautofootnote_startqKUnameidsq}q(hUroadmapqhUversion-numberingqhUimplementation-roadmapqh Uyear-1qh U years-3-5qh Uyear-2quUchildrenq]qcdocutils.nodes section q)q}q(U rawsourceq UUparentq!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 XImplementation Roadmapq5h!hh"h#h$Utitleq6h&}q7(h(]h)]h*]h+]h-]uh/Kh0hh]q8cdocutils.nodes Text q9XImplementation Roadmapq:q;}q<(h h5h!h3ubaubcdocutils.nodes paragraph q=)q>}q?(h XThe 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]qCh9XThe DataONE project has an initial lifetime of five years, starting August 2009. Over this time development will occur in three major phases:qDqE}qF(h h@h!h>ubaubcdocutils.nodes field_list qG)qH}qI(h Uh!hh"h#h$U field_listqJh&}qK(h(]h)]h*]h+]h-]uh/Kh0hh]qL(cdocutils.nodes field qM)qN}qO(h Uh!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/Kh]qYh9X PrototypingqZq[}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.qgqh}qi(h hdh!hbubaubah$U field_bodyqjubeubhM)qk}ql(h Uh!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/Kh]qsh9X First releaseqtqu}qv(h hqh!houbaubh])qw}qx(h XTargeted 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 XTargeted 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]qh9XTargeted 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.qq}q(h h}h!h{ubaubah$hjubeubhM)q}q(h Uh!hHh"h#h$hPh&}q(h(]h)]h*]h+]h-]uh/Kh0hh]q(hS)q}q(h XSecond releaseqh!hh"h#h$hWh&}q(h(]h)]h*]h+]h-]uh/Kh]qh9XSecond releaseqq}q(h hh!hubaubh])q}q(h XSubsequent 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!hh]qh=)q}q(h XSubsequent 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.qh!hh"h#h$hAh&}q(h(]h)]h*]h+]h-]uh/Kh]qh9XSubsequent 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.qq}q(h hh!hubaubah$hjubeubeubh)q}q(h Uh!hh"h#h$h%h&}q(h(]h)]h*]h+]qhah-]qhauh/Kh0hh]q(h2)q}q(h XVersion Numberingqh!hh"h#h$h6h&}q(h(]h)]h*]h+]h-]uh/Kh0hh]qh9XVersion Numberingqq}q(h hh!hubaubh=)q}q(h XThere 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.qh!hh"h#h$hAh&}q(h(]h)]h*]h+]h-]uh/K h0hh]qh9XThere 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.qq}q(h hh!hubaubh=)q}q(h XwVersion numbers are expressed in three parts: Major.Minor.Revision to reflect official releases of the software, where:qh!hh"h#h$hAh&}q(h(]h)]h*]h+]h-]uh/K%h0hh]qh9XwVersion numbers are expressed in three parts: Major.Minor.Revision to reflect official releases of the software, where:qq}q(h hh!hubaubhG)q}q(h Uh!hh"h#h$hJh&}q(h(]h)]h*]h+]h-]uh/K(h0hh]q(hM)q}q(h Uh!hh"h#h$hPh&}q(h(]h)]h*]h+]h-]uh/K(h0hh]q(hS)q}q(h XMajorqh!hh"h#h$hWh&}q(h(]h)]h*]h+]h-]uh/Kh]qh9XMajorqƅq}q(h hh!hubaubh])q}q(h XIs 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!hh]qh=)q}q(h XIs 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.qh!hh"h#h$hAh&}q(h(]h)]h*]h+]h-]uh/K*h]qh9XIs 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 hh!hubaubah$hjubeubhM)q}q(h Uh!hh"h#h$hPh&}q(h(]h)]h*]h+]h-]uh/K.h0hh]q(hS)q}q(h XMinorqh!hh"h#h$hWh&}q(h(]h)]h*]h+]h-]uh/Kh]qh9XMinorqޅq}q(h hh!hubaubh])q}q(h XnAdds additional features to an existing release and maintains compatibility within the current major version. h&}q(h(]h)]h*]h+]h-]uh!hh]qh=)q}q(h XmAdds additional features to an existing release and maintains compatibility within the current major version.qh!hh"h#h$hAh&}q(h(]h)]h*]h+]h-]uh/K0h]qh9XmAdds additional features to an existing release and maintains compatibility within the current major version.qꅁq}q(h hh!hubaubah$hjubeubhM)q}q(h Uh!hh"h#h$hPh&}q(h(]h)]h*]h+]h-]uh/K3h0hh]q(hS)q}q(h XRevisionqh!hh"h#h$hWh&}q(h(]h)]h*]h+]h-]uh/Kh]qh9XRevisionqq}q(h hh!hubaubh])q}q(h XIndicates 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!hh]qh=)q}q(h XIndicates a minor change from the current version, typically used to provide bug fix releases. Will not usually add additional functionality.qh!hh"h#h$hAh&}r(h(]h)]h*]h+]h-]uh/K5h]rh9XIndicates a minor change from the current version, typically used to provide bug fix releases. Will not usually add additional functionality.rr}r(h hh!hubaubah$hjubeubeubeubh)r}r(h Uh!hh"h#h$h%h&}r(h(]h)]h*]h+]rhah-]r hauh/K:h0hh]r (h2)r }r (h XRoadmapr h!jh"h#h$h6h&}r(h(]h)]h*]h+]h-]uh/K:h0hh]rh9XRoadmaprr}r(h j h!j ubaubcdocutils.nodes image r)r}r(h X'.. image:: images/general_schedule.png h!jh"h#h$Uimagerh&}r(UuriX*implementation/images/general_schedule.pngrh+]h*]h(]h)]U candidatesr}rU*jsh-]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!jh"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!jh]r#h9X Figure 1.r$r%}r&(h Uh!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!jubeubh)r+}r,(h Uh!jh"h#h$h%h&}r-(h(]h)]h*]h+]r.hah-]r/h auh/KHh0hh]r0(h2)r1}r2(h XYear 1r3h!j+h"h#h$h6h&}r4(h(]h)]h*]h+]h-]uh/KHh0hh]r5h9XYear 1r6r7}r8(h j3h!j1ubaubcdocutils.nodes bullet_list r9)r:}r;(h Uh!j+h"h#h$U bullet_listr<h&}r=(Ubulletr>X-h+]h*]h(]h)]h-]uh/KJh0hh]r?(cdocutils.nodes list_item r@)rA}rB(h XInitial design and prototyping.rCh!j:h"h#h$U list_itemrDh&}rE(h(]h)]h*]h+]h-]uh/Nh0hh]rFh=)rG}rH(h jCh!jAh"h#h$hAh&}rI(h(]h)]h*]h+]h-]uh/KJh]rJh9XInitial design and prototyping.rKrL}rM(h jCh!jGubaubaubj@)rN}rO(h X%Review of architecture and prototype h!j:h"h#h$jDh&}rP(h(]h)]h*]h+]h-]uh/Nh0hh]rQh=)rR}rS(h X$Review of architecture and prototyperTh!jNh"h#h$hAh&}rU(h(]h)]h*]h+]h-]uh/KKh]rVh9X$Review of architecture and prototyperWrX}rY(h jTh!jRubaubaubeubeubh)rZ}r[(h Uh!jh"h#h$h%h&}r\(h(]h)]h*]h+]r]hah-]r^h auh/KNh0hh]r_(h2)r`}ra(h XYear 2rbh!jZh"h#h$h6h&}rc(h(]h)]h*]h+]h-]uh/KNh0hh]rdh9XYear 2rerf}rg(h jbh!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:rjh!jZh"h#h$hAh&}rk(h(]h)]h*]h+]h-]uh/KPh0hh]rlh9X%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:rmrn}ro(h jjh!jhubaubj9)rp}rq(h Uh!jZh"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!jph"h#h$jDh&}rv(h(]h)]h*]h+]h-]uh/Nh0hh]rwh=)rx}ry(h X$Revision of prototype implementationrzh!jth"h#h$hAh&}r{(h(]h)]h*]h+]h-]uh/KUh]r|h9X$Revision of prototype implementationr}r~}r(h jzh!jxubaubaubj@)r}r(h XPublic release of DataONE cyberinfrastructure. Implementation of the revised infrastructure with particular emphasis on scalable, stable, and secure core functionality h!jph"h#h$jDh&}r(h(]h)]h*]h+]h-]uh/Nh0hh]rh=)r}r(h XPublic release of DataONE cyberinfrastructure. Implementation of the revised infrastructure with particular emphasis on scalable, stable, and secure core functionalityrh!jh"h#h$hAh&}r(h(]h)]h*]h+]h-]uh/KWh]rh9XPublic release of DataONE cyberinfrastructure. Implementation of the revised infrastructure with particular emphasis on scalable, stable, and secure core functionalityrr}r(h jh!jubaubaubj@)r}r(h XYUser documentation. Development of technical user educational materials and ITK examples h!jph"h#h$jDh&}r(h(]h)]h*]h+]h-]uh/Nh0hh]rh=)r}r(h XXUser documentation. Development of technical user educational materials and ITK examplesrh!jh"h#h$hAh&}r(h(]h)]h*]h+]h-]uh/K[h]rh9XXUser documentation. Development of technical user educational materials and ITK examplesrr}r(h jh!jubaubaubj@)r}r(h X5Member 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!jph"h#h$jDh&}r(h(]h)]h*]h+]h-]uh/Nh0hh]rh=)r}r(h X4Member 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 Servicerh!jh"h#h$hAh&}r(h(]h)]h*]h+]h-]uh/K^h]rh9X4Member 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 Servicerr}r(h jh!jubaubaubj@)r}r(h X3First implementation phases of federated identity. h!jph"h#h$jDh&}r(h(]h)]h*]h+]h-]uh/Nh0hh]rh=)r}r(h X2First implementation phases of federated identity.rh!jh"h#h$hAh&}r(h(]h)]h*]h+]h-]uh/Kdh]rh9X2First implementation phases of federated identity.rr}r(h jh!jubaubaubj@)r}r(h XDesign 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!jph"h#h$jDh&}r(h(]h)]h*]h+]h-]uh/Nh0hh]rh=)r}r(h XDesign 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.rh!jh"h#h$hAh&}r(h(]h)]h*]h+]h-]uh/Kfh]rh9XDesign 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.rr}r(h jh!jubaubaubj@)r}r(h XFurther progress on key aspects of semantic search, semantic integration and workflow support through activities of the respective working groups. h!jph"h#h$jDh&}r(h(]h)]h*]h+]h-]uh/Nh0hh]rh=)r}r(h XFurther progress on key aspects of semantic search, semantic integration and workflow support through activities of the respective working groups.rh!jh"h#h$hAh&}r(h(]h)]h*]h+]h-]uh/Kkh]rh9XFurther progress on key aspects of semantic search, semantic integration and workflow support through activities of the respective working groups.rr}r(h jh!jubaubaubeubeubh)r}r(h Uh!jh"h#h$h%h&}r(h(]h)]h*]h+]rhah-]rh auh/Kph0hh]r(h2)r}r(h X Years 3-5rh!jh"h#h$h6h&}r(h(]h)]h*]h+]h-]uh/Kph0hh]rh9X Years 3-5rr}r(h jh!jubaubh=)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:rh!jh"h#h$hAh&}r(h(]h)]h*]h+]h-]uh/Krh0hh]rh9X@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:rr}r(h jh!jubaubj9)r}r(h Uh!jh"h#h$j<h&}r(j>X-h+]h*]h(]h)]h-]uh/Kh0hh]r(j@)r}r(h XEvaluation, 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!jh"h#h$jDh&}r(h(]h)]h*]h+]h-]uh/Nh0hh]rh=)r}r(h XEvaluation, 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 functionalityrh!jh"h#h$hAh&}r(h(]h)]h*]h+]h-]uh/Kh]rh9XEvaluation, 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 functionalityrr}r(h jh!jubaubaubj@)r}r(h XInvestigator 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!jh"h#h$jDh&}r(h(]h)]h*]h+]h-]uh/Nh0hh]rh=)r}r(h XInvestigator 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)rh!jh"h#h$hAh&}r(h(]h)]h*]h+]h-]uh/Kh]rh9XInvestigator 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)rr}r(h jh!jubaubaubj@)r}r(h XSemantically facilitated search and discovery. Incorporation of outputs from semantics working groups, targeting improvement of search precision and accuracy h!jh"h#h$jDh&}r(h(]h)]h*]h+]h-]uh/Nh0hh]rh=)r}r(h XSemantically facilitated search and discovery. Incorporation of outputs from semantics working groups, targeting improvement of search precision and accuracyrh!jh"h#h$hAh&}r(h(]h)]h*]h+]h-]uh/Kh]rh9XSemantically facilitated search and discovery. Incorporation of outputs from semantics working groups, targeting improvement of search precision and accuracyrr}r(h jh!jubaubaubj@)r}r(h XRAddition 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!jh"h#h$jDh&}r(h(]h)]h*]h+]h-]uh/Nh0hh]r h=)r }r (h XQAddition 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!jh"h#h$hAh&}r (h(]h)]h*]h+]h-]uh/Kh]rh9XQAddition 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.rr}r(h j h!j ubaubaubj@)r}r(h XNew user services. Addition of data sub-setting, visualization, and integration services, to be closely aligned with deployment of specialized nodes h!jh"h#h$jDh&}r(h(]h)]h*]h+]h-]uh/Nh0hh]rh=)r}r(h XNew user services. Addition of data sub-setting, visualization, and integration services, to be closely aligned with deployment of specialized nodesrh!jh"h#h$hAh&}r(h(]h)]h*]h+]h-]uh/Kh]rh9XNew user services. Addition of data sub-setting, visualization, and integration services, to be closely aligned with deployment of specialized nodesrr}r(h jh!jubaubaubj@)r}r(h XGlobal deployment of Member Nodes and Coordinating Nodes. Ongoing global deployment of all node types, including additional CNs in Europe and Oceania h!jh"h#h$jDh&}r (h(]h)]h*]h+]h-]uh/Nh0hh]r!h=)r"}r#(h XGlobal deployment of Member Nodes and Coordinating Nodes. Ongoing global deployment of all node types, including additional CNs in Europe and Oceaniar$h!jh"h#h$hAh&}r%(h(]h)]h*]h+]h-]uh/Kh]r&h9XGlobal 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 UU transformerr*NU footnote_refsr+}r,Urefnamesr-}r.Usymbol_footnotesr/]r0Uautofootnote_refsr1]r2Usymbol_footnote_refsr3]r4U citationsr5]r6h0hU current_liner7NUtransform_messagesr8]r9Ureporterr:NUid_startr;KU autofootnotesr<]r=U citation_refsr>}r?Uindirect_targetsr@]rAUsettingsrB(cdocutils.frontend Values rCorD}rE(Ufootnote_backlinksrFKUrecord_dependenciesrGNU rfc_base_urlrHUhttps://tools.ietf.org/html/rIU tracebackrJUpep_referencesrKNUstrip_commentsrLNU toc_backlinksrMUentryrNU language_coderOUenrPU datestamprQNU report_levelrRKU _destinationrSNU halt_levelrTKU strip_classesrUNh6NUerror_encoding_error_handlerrVUbackslashreplacerWUdebugrXNUembed_stylesheetrYUoutput_encoding_error_handlerrZUstrictr[U sectnum_xformr\KUdump_transformsr]NU docinfo_xformr^KUwarning_streamr_NUpep_file_url_templater`Upep-%04draUexit_status_levelrbKUconfigrcNUstrict_visitorrdNUcloak_email_addressesreUtrim_footnote_reference_spacerfUenvrgNUdump_pseudo_xmlrhNUexpose_internalsriNUsectsubtitle_xformrjU source_linkrkNUrfc_referencesrlNUoutput_encodingrmUutf-8rnU source_urlroNUinput_encodingrpU utf-8-sigrqU_disable_configrrNU id_prefixrsUU tab_widthrtKUerror_encodingruUUTF-8rvU_sourcerwh#Ugettext_compactrxU generatorryNUdump_internalsrzNU smart_quotesr{U pep_base_urlr|U https://www.python.org/dev/peps/r}Usyntax_highlightr~UlongrUinput_encoding_error_handlerrj[Uauto_id_prefixrUidrUdoctitle_xformrUstrip_elements_with_classesrNU _config_filesr]Ufile_insertion_enabledrU raw_enabledrKU dump_settingsrNubUsymbol_footnote_startrKUidsr}r(hjhjZhj+hjhhhhuUsubstitution_namesr}rh$h0h&}r(h(]h+]h*]Usourceh#h)]h-]uU footnotesr]rUrefidsr}rub.