Built site for gh-pages

Quarto GHA Workflow Runner · Quarto GHA Workflow Runner · commit 21548cc4bb01 · 2024-05-03T20:05:54.000Z
diff --git a/.nojekyll b/.nojekyll
@@ -1 +1 @@
-e70332a0
+3959c84b
diff --git a/_tex/index.tex b/_tex/index.tex
@@ -366,6 +366,48 @@ \section{Recommendations}\label{recommendations}
   descriptions of cross-cutting best-practices. These can be used as a
   basis of the analysis or assessment of an existing standard, or as
   guidelines to develop new standards.
+\item
+  Recommend pathways or lifecycles for successful data standards.
+  Include process, creators, affiliations, grants, and adoption
+  journeys. Make this documentation step integral to the work of
+  standards creators and granting agencies.
+\item
+  Retrocactively document \#3 for standards such as CF(climate science),
+  NASA genelab (space omics), OpenGIS (geospatial), DICOM (medical
+  imaging), GA4GH (genomics), FITS (astronomy), Zarr (domain agnostic
+  n-dimensional arrays)\ldots{} ?
+\item
+  Create ontology for standards process such as top down vs bottom up,
+  minimum number of datasets, community size. Examine schema.org (w3c),
+  PEP (Python), CDISC (FDA).
+\item
+  Amplify formalization/guidelines on how to create standards (example
+  metadata schema specifications using https://linkml.io).
+\item
+  Make data standards machine readable, and software creation an
+  integral part of establishing a standard's schema e.g.~identifiers for
+  a person using CFF in citations. cffconvert software makes the CFF
+  standard usable and useful.
+\item
+  Survey and document failure of current standards for a specific
+  dataset / domain before establishing a new one. Use resources such as
+  Fairsharing.org or Digital Curation Center
+  https://www.dcc.ac.uk/guidance/standards.
+\item
+  Funding agencies and science communities need to establish governance
+  for standards creation and adoption (cite
+  https://www.theopensourceway.org/the\_open\_source\_way-guidebook-2.0.html\#\_project\_and\_community\_governance).
+\item
+  Cross sector alliances such as industry - academia need closer
+  coordination and algnment of pace through strong program management
+  (for instance via OSPO efforts).
+\item
+  Multi company partnerships should include strategic initiatives for
+  standard establishment (example
+  https://www.pistoiaalliance.org/news/press-release-pistoia-alliance-launches-idmp-1-0/).
+\item
+  Stakeholder organizations should invest in training grants to
+  establish curriculum for data and metadata standards education.
 \end{enumerate}
 
 
diff --git a/index.html b/index.html
@@ -2,7 +2,7 @@
 <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head>
 
 <meta charset="utf-8">
-<meta name="generator" content="quarto-1.4.553">
+<meta name="generator" content="quarto-1.4.554">
 
 <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes">
 
@@ -122,7 +122,7 @@ <h2 id="toc-title">Table of contents</h2>
   </ul></li>
   <li><a href="#recommendations" id="toc-recommendations" class="nav-link" data-scroll-target="#recommendations"><span class="header-section-number">5</span> Recommendations</a></li>
   </ul>
-<div class="quarto-alternate-notebooks"><h2>Notebooks</h2><ul><li><a href="sections/02-challenges-preview.html"><i class="bi bi-journal-code"></i>Challenges for open source data and metadata standards, and some solutions</a></li><li><a href="sections/01-introduction-preview.html"><i class="bi bi-journal-code"></i>Introduction</a></li><li><a href="sections/xx-recommendations-preview.html"><i class="bi bi-journal-code"></i>Recommendations</a></li></ul></div></nav>
+<div class="quarto-alternate-notebooks"><h2>Notebooks</h2><ul><li><a href="sections/02-challenges-preview.html"><i class="bi bi-journal-code"></i>Challenges for open source data and metadata standards, and some solutions</a></li><li><a href="sections/01-introduction-preview.html"><i class="bi bi-journal-code"></i>Introduction</a></li><li><a href="sections/03-recommendations-preview.html"><i class="bi bi-journal-code"></i>Recommendations</a></li></ul></div></nav>
 </div>
 <div id="quarto-margin-sidebar" class="sidebar margin-sidebar">
 </div>
@@ -182,6 +182,16 @@ <h1 data-number="5"><span class="header-section-number">5</span> Recommendations
 <ol type="1">
 <li>Training for data stewards and career paths that encourage this role.</li>
 <li>Development of meta-standards or standards-of-standards. These are descriptions of cross-cutting best-practices. These can be used as a basis of the analysis or assessment of an existing standard, or as guidelines to develop new standards.</li>
+<li>Recommend pathways or lifecycles for successful data standards. Include process, creators, affiliations, grants, and adoption journeys. Make this documentation step integral to the work of standards creators and granting agencies.</li>
+<li>Retrocactively document #3 for standards such as CF(climate science), NASA genelab (space omics), OpenGIS (geospatial), DICOM (medical imaging), GA4GH (genomics), FITS (astronomy), Zarr (domain agnostic n-dimensional arrays)… ?</li>
+<li>Create ontology for standards process such as top down vs bottom up, minimum number of datasets, community size. Examine schema.org (w3c), PEP (Python), CDISC (FDA).</li>
+<li>Amplify formalization/guidelines on how to create standards (example metadata schema specifications using https://linkml.io).</li>
+<li>Make data standards machine readable, and software creation an integral part of establishing a standard’s schema e.g.&nbsp;identifiers for a person using CFF in citations. cffconvert software makes the CFF standard usable and useful.</li>
+<li>Survey and document failure of current standards for a specific dataset / domain before establishing a new one. Use resources such as Fairsharing.org or Digital Curation Center https://www.dcc.ac.uk/guidance/standards.</li>
+<li>Funding agencies and science communities need to establish governance for standards creation and adoption (cite https://www.theopensourceway.org/the_open_source_way-guidebook-2.0.html#_project_and_community_governance).</li>
+<li>Cross sector alliances such as industry - academia need closer coordination and algnment of pace through strong program management (for instance via OSPO efforts).</li>
+<li>Multi company partnerships should include strategic initiatives for standard establishment (example https://www.pistoiaalliance.org/news/press-release-pistoia-alliance-launches-idmp-1-0/).</li>
+<li>Stakeholder organizations should invest in training grants to establish curriculum for data and metadata standards education.</li>
 </ol>
 </section>
 
diff --git a/index.pdf b/index.pdf
diff --git a/sections/01-introduction-preview.html b/sections/01-introduction-preview.html
@@ -1,7 +1,7 @@
 <!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head>
     <meta charset="utf-8">
-    <meta name="generator" content="quarto-1.4.553">
+    <meta name="generator" content="quarto-1.4.554">
 
     <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes">
 
diff --git a/sections/01-introduction.embed.ipynb b/sections/01-introduction.embed.ipynb
@@ -20,7 +20,7 @@
     "\n",
     "It was also within the Python community that an orderly process for community-guided evolution of an open-source software project emerged, through the Python Enhancement Proposal (PEP) mechanism , which lays out how major changes to the software should be proposed, advocated for, and eventually decided on. While these tools, ideas, and practices evolved in developing software, they are readily translated to other domains. For example, OSS notions surrounding IP have given rise to the Creative Commons movement that has expanded these notions to apply to a much wider range of human creative endeavours. Similarly OSS notions regarding collaborative structures have pervaded the current era of open science and team science ."
    ],
-   "id": "841b18f3-408f-48f3-89e5-4fa0d7ca164a"
+   "id": "7ba6c6e6-06ae-4916-bf42-00e5560056ce"
   }
  ],
  "nbformat": 4,
diff --git a/sections/01-introduction.out.ipynb b/sections/01-introduction.out.ipynb
@@ -20,7 +20,7 @@
     "\n",
     "It was also within the Python community that an orderly process for community-guided evolution of an open-source software project emerged, through the Python Enhancement Proposal (PEP) mechanism , which lays out how major changes to the software should be proposed, advocated for, and eventually decided on. While these tools, ideas, and practices evolved in developing software, they are readily translated to other domains. For example, OSS notions surrounding IP have given rise to the Creative Commons movement that has expanded these notions to apply to a much wider range of human creative endeavours. Similarly OSS notions regarding collaborative structures have pervaded the current era of open science and team science ."
    ],
-   "id": "b8e0a8f8-4bb5-4324-8928-b2160ba0945c"
+   "id": "2770c237-8017-4871-b026-b2e1cb2174df"
   }
  ],
  "nbformat": 4,
diff --git a/sections/02-challenges-preview.html b/sections/02-challenges-preview.html
@@ -1,7 +1,7 @@
 <!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head>
     <meta charset="utf-8">
-    <meta name="generator" content="quarto-1.4.553">
+    <meta name="generator" content="quarto-1.4.554">
 
     <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes">
 
diff --git a/sections/02-challenges.embed.ipynb b/sections/02-challenges.embed.ipynb
@@ -32,7 +32,7 @@
     "\n",
     "[1] So old in fact that an oft-cited [XKCD comic](https://xkcd.com/927/) has been devoted to it."
    ],
-   "id": "869a056c-99d4-49a5-bd45-98468a35c23b"
+   "id": "64c66881-4189-407c-8b8f-8f1c6c0af7cb"
   }
  ],
  "nbformat": 4,
diff --git a/sections/02-challenges.out.ipynb b/sections/02-challenges.out.ipynb
@@ -32,7 +32,7 @@
     "\n",
     "[1] So old in fact that an oft-cited [XKCD comic](https://xkcd.com/927/) has been devoted to it."
    ],
-   "id": "8f59a89b-6e28-4180-96ca-fb9f37bcccb1"
+   "id": "d3519e39-561c-4c7d-ba97-f65b2b57b3cd"
   }
  ],
  "nbformat": 4,
diff --git a/sections/03-recommendations-preview.html b/sections/03-recommendations-preview.html
@@ -1,12 +1,12 @@
 <!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head>
     <meta charset="utf-8">
-    <meta name="generator" content="quarto-1.4.553">
+    <meta name="generator" content="quarto-1.4.554">
 
     <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes">
 
 
-    <title>xx-recommendations</title>
+    <title>recommendations</title>
     <style>
       code{white-space: pre-wrap;}
       span.smallcaps{font-variant: small-caps;}
@@ -136,7 +136,7 @@
       <a onclick="window.quartoBackToArticle(); return false;" class="btn btn-primary quarto-back-link" href=""><i class="bi bi-caret-left"></i> Back to Article</a>
       <h6><i class="bi bi-journal-code"></i> Recommendations</h6>
 
-            <a href="../sections/xx-recommendations.qmd" class="btn btn-primary quarto-download-embed" download="xx-recommendations.qmd">Download Source</a>
+            <a href="../sections/03-recommendations.qmd" class="btn btn-primary quarto-download-embed" download="03-recommendations.qmd">Download Source</a>
           </div>
 
      <div id="quarto-content" class="page-columns page-rows-contents page-layout-article toc-left">
@@ -157,6 +157,16 @@ <h1>Recommendations</h1>
 <ol type="1">
 <li>Training for data stewards and career paths that encourage this role.</li>
 <li>Development of meta-standards or standards-of-standards. These are descriptions of cross-cutting best-practices. These can be used as a basis of the analysis or assessment of an existing standard, or as guidelines to develop new standards.</li>
+<li>Recommend pathways or lifecycles for successful data standards. Include process, creators, affiliations, grants, and adoption journeys. Make this documentation step integral to the work of standards creators and granting agencies.</li>
+<li>Retrocactively document #3 for standards such as CF(climate science), NASA genelab (space omics), OpenGIS (geospatial), DICOM (medical imaging), GA4GH (genomics), FITS (astronomy), Zarr (domain agnostic n-dimensional arrays)… ?</li>
+<li>Create ontology for standards process such as top down vs bottom up, minimum number of datasets, community size. Examine schema.org (w3c), PEP (Python), CDISC (FDA).</li>
+<li>Amplify formalization/guidelines on how to create standards (example metadata schema specifications using https://linkml.io).</li>
+<li>Make data standards machine readable, and software creation an integral part of establishing a standard’s schema e.g.&nbsp;identifiers for a person using CFF in citations. cffconvert software makes the CFF standard usable and useful.</li>
+<li>Survey and document failure of current standards for a specific dataset / domain before establishing a new one. Use resources such as Fairsharing.org or Digital Curation Center https://www.dcc.ac.uk/guidance/standards.</li>
+<li>Funding agencies and science communities need to establish governance for standards creation and adoption (cite https://www.theopensourceway.org/the_open_source_way-guidebook-2.0.html#_project_and_community_governance).</li>
+<li>Cross sector alliances such as industry - academia need closer coordination and algnment of pace through strong program management (for instance via OSPO efforts).</li>
+<li>Multi company partnerships should include strategic initiatives for standard establishment (example https://www.pistoiaalliance.org/news/press-release-pistoia-alliance-launches-idmp-1-0/).</li>
+<li>Stakeholder organizations should invest in training grants to establish curriculum for data and metadata standards education.</li>
 </ol>
 </section>
      </main>
diff --git a/sections/03-recommendations.embed.ipynb b/sections/03-recommendations.embed.ipynb
@@ -0,0 +1,32 @@
+{
+ "cells": [
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "# \n",
+    "\n",
+    "# Recommendations\n",
+    "\n",
+    "We make the following recommendations:\n",
+    "\n",
+    "1.  Training for data stewards and career paths that encourage this role.\n",
+    "2.  Development of meta-standards or standards-of-standards. These are descriptions of cross-cutting best-practices. These can be used as a basis of the analysis or assessment of an existing standard, or as guidelines to develop new standards.\n",
+    "3.  Recommend pathways or lifecycles for successful data standards. Include process, creators, affiliations, grants, and adoption journeys. Make this documentation step integral to the work of standards creators and granting agencies.\n",
+    "4.  Retrocactively document #3 for standards such as CF(climate science), NASA genelab (space omics), OpenGIS (geospatial), DICOM (medical imaging), GA4GH (genomics), FITS (astronomy), Zarr (domain agnostic n-dimensional arrays)… ?\n",
+    "5.  Create ontology for standards process such as top down vs bottom up, minimum number of datasets, community size. Examine schema.org (w3c), PEP (Python), CDISC (FDA).\n",
+    "6.  Amplify formalization/guidelines on how to create standards (example metadata schema specifications using https://linkml.io).\n",
+    "7.  Make data standards machine readable, and software creation an integral part of establishing a standard’s schema e.g. identifiers for a person using CFF in citations. cffconvert software makes the CFF standard usable and useful.\n",
+    "8.  Survey and document failure of current standards for a specific dataset / domain before establishing a new one. Use resources such as Fairsharing.org or Digital Curation Center https://www.dcc.ac.uk/guidance/standards.\n",
+    "9.  Funding agencies and science communities need to establish governance for standards creation and adoption (cite https://www.theopensourceway.org/the_open_source_way-guidebook-2.0.html#\\_project_and_community_governance).\n",
+    "10. Cross sector alliances such as industry - academia need closer coordination and algnment of pace through strong program management (for instance via OSPO efforts).\n",
+    "11. Multi company partnerships should include strategic initiatives for standard establishment (example https://www.pistoiaalliance.org/news/press-release-pistoia-alliance-launches-idmp-1-0/).\n",
+    "12. Stakeholder organizations should invest in training grants to establish curriculum for data and metadata standards education."
+   ],
+   "id": "53b03ee4-7f69-4832-83ed-9bd5c1c1db35"
+  }
+ ],
+ "nbformat": 4,
+ "nbformat_minor": 5,
+ "metadata": {}
+}
diff --git a/sections/03-recommendations.out.ipynb b/sections/03-recommendations.out.ipynb
@@ -0,0 +1,32 @@
+{
+ "cells": [
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "# \n",
+    "\n",
+    "# Recommendations\n",
+    "\n",
+    "We make the following recommendations:\n",
+    "\n",
+    "1.  Training for data stewards and career paths that encourage this role.\n",
+    "2.  Development of meta-standards or standards-of-standards. These are descriptions of cross-cutting best-practices. These can be used as a basis of the analysis or assessment of an existing standard, or as guidelines to develop new standards.\n",
+    "3.  Recommend pathways or lifecycles for successful data standards. Include process, creators, affiliations, grants, and adoption journeys. Make this documentation step integral to the work of standards creators and granting agencies.\n",
+    "4.  Retrocactively document #3 for standards such as CF(climate science), NASA genelab (space omics), OpenGIS (geospatial), DICOM (medical imaging), GA4GH (genomics), FITS (astronomy), Zarr (domain agnostic n-dimensional arrays)… ?\n",
+    "5.  Create ontology for standards process such as top down vs bottom up, minimum number of datasets, community size. Examine schema.org (w3c), PEP (Python), CDISC (FDA).\n",
+    "6.  Amplify formalization/guidelines on how to create standards (example metadata schema specifications using https://linkml.io).\n",
+    "7.  Make data standards machine readable, and software creation an integral part of establishing a standard’s schema e.g. identifiers for a person using CFF in citations. cffconvert software makes the CFF standard usable and useful.\n",
+    "8.  Survey and document failure of current standards for a specific dataset / domain before establishing a new one. Use resources such as Fairsharing.org or Digital Curation Center https://www.dcc.ac.uk/guidance/standards.\n",
+    "9.  Funding agencies and science communities need to establish governance for standards creation and adoption (cite https://www.theopensourceway.org/the_open_source_way-guidebook-2.0.html#\\_project_and_community_governance).\n",
+    "10. Cross sector alliances such as industry - academia need closer coordination and algnment of pace through strong program management (for instance via OSPO efforts).\n",
+    "11. Multi company partnerships should include strategic initiatives for standard establishment (example https://www.pistoiaalliance.org/news/press-release-pistoia-alliance-launches-idmp-1-0/).\n",
+    "12. Stakeholder organizations should invest in training grants to establish curriculum for data and metadata standards education."
+   ],
+   "id": "bea9edf1-f026-4fea-b5a9-97810dac6d74"
+  }
+ ],
+ "nbformat": 4,
+ "nbformat_minor": 5,
+ "metadata": {}
+}
diff --git a/sections/03-recommendations.qmd b/sections/03-recommendations.qmd
diff --git a/sections/xx-recommendations.embed.ipynb b/sections/xx-recommendations.embed.ipynb
diff --git a/sections/xx-recommendations.out.ipynb b/sections/xx-recommendations.out.ipynb
diff --git a/sections/xx-recommendations.qmd b/sections/xx-recommendations.qmd

Original file line number	Diff line number	Diff line change
`@@ -20,7 +20,7 @@`
`20`	`20`	`"\n",`
`21`	`21`	"It was also within the Python community that an orderly process for community-guided evolution of an open-source software project emerged, through the Python Enhancement Proposal (PEP) mechanism , which lays out how major changes to the software should be proposed, advocated for, and eventually decided on. While these tools, ideas, and practices evolved in developing software, they are readily translated to other domains. For example, OSS notions surrounding IP have given rise to the Creative Commons movement that has expanded these notions to apply to a much wider range of human creative endeavours. Similarly OSS notions regarding collaborative structures have pervaded the current era of open science and team science ."
`22`	`22`	`],`
`23`		`- "id": "841b18f3-408f-48f3-89e5-4fa0d7ca164a"`
	`23`	`+ "id": "7ba6c6e6-06ae-4916-bf42-00e5560056ce"`
`24`	`24`	`}`
`25`	`25`	`],`
`26`	`26`	`"nbformat": 4,`
Original file line number	Diff line number	Diff line change
`@@ -32,7 +32,7 @@`
`32`	`32`	`"\n",`
`33`	`33`	`"[1] So old in fact that an oft-cited [XKCD comic](https://xkcd.com/927/) has been devoted to it."`
`34`	`34`	`],`
`35`		`- "id": "869a056c-99d4-49a5-bd45-98468a35c23b"`
	`35`	`+ "id": "64c66881-4189-407c-8b8f-8f1c6c0af7cb"`
`36`	`36`	`}`
`37`	`37`	`],`
`38`	`38`	`"nbformat": 4,`