Built site for gh-pages

uwescience · Apr 10, 2024 · b3d9288 · b3d9288
1 parent e983dee
commit b3d9288
Show file tree

Hide file tree

Showing 12 changed files with 28 additions and 12 deletions.
diff --git a/.nojekyll b/.nojekyll
@@ -1 +1 @@
-7415d552
+3c48ecb7
diff --git a/_tex/index.tex b/_tex/index.tex
@@ -307,7 +307,15 @@ \subsection{Too much flexibility, or too
   it.}.
 
 Another failure is the mismatch between developers of the standard and
-users.
+users. There is an iherent gap in both interest and ability to engage
+with the technical details undergirding standards and their development
+between the developers of the standard and their users. In extreme
+cases, these interests may be at odds, as developers implement
+sophisticated mechanisms to automate the creation of the standard or
+advocate for more technically advanced mechanisms for evolving the
+standard, leaving potential users sidelined in the development of the
+standard, and limiting their ability to provide feedback about the
+practical implications of changes to the standards.
 
 \subsection{Sustainability}\label{sustainability}
 

diff --git a/index.html b/index.html
@@ -143,7 +143,7 @@ <h1 data-number="4"><span class="header-section-number">4</span> Challenges for
 <section id="too-much-flexibility-or-too-little" class="level2" data-number="4.1">
 <h2 data-number="4.1" class="anchored" data-anchor-id="too-much-flexibility-or-too-little"><span class="header-section-number">4.1</span> Too much flexibility, or too little</h2>
 <p>It’s a story as old as time (or at least as old as standards): users fail to consider existing standards, or perceive an existing standard as not offering enough flexibility to cover some use case, and they embark on the development of a new standard <a href="#fn1" class="footnote-ref" id="fnref1" role="doc-noteref"><sup>1</sup></a>.</p>
-<p>Another failure is the mismatch between developers of the standard and users.</p>
+<p>Another failure is the mismatch between developers of the standard and users. There is an iherent gap in both interest and ability to engage with the technical details undergirding standards and their development between the developers of the standard and their users. In extreme cases, these interests may be at odds, as developers implement sophisticated mechanisms to automate the creation of the standard or advocate for more technically advanced mechanisms for evolving the standard, leaving potential users sidelined in the development of the standard, and limiting their ability to provide feedback about the practical implications of changes to the standards.</p>
 </section>
 <section id="sustainability" class="level2" data-number="4.2">
 <h2 data-number="4.2" class="anchored" data-anchor-id="sustainability"><span class="header-section-number">4.2</span> Sustainability</h2>

diff --git a/index.pdf b/index.pdf
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": "ded2924f-f5a9-4e7f-98e2-ef30148ca01a"
+   "id": "20bf0692-61c6-4a81-a9c8-051ac054e10c"
   }
  ],
  "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": "567f66db-abe2-44de-85c2-4592029a03b8"
+   "id": "34ba4e85-d9cf-4a02-a2ba-bf052d2acf7f"
   }
  ],
  "nbformat": 4,

diff --git a/sections/02-challenges-preview.html b/sections/02-challenges-preview.html
@@ -161,7 +161,7 @@ <h1>Challenges for open source data and metadata standards, and some solutions</
 <section id="too-much-flexibility-or-too-little" class="level2">
 <h2 class="anchored" data-anchor-id="too-much-flexibility-or-too-little">Too much flexibility, or too little</h2>
 <p>It’s a story as old as time (or at least as old as standards): users fail to consider existing standards, or perceive an existing standard as not offering enough flexibility to cover some use case, and they embark on the development of a new standard <a href="#fn1" class="footnote-ref" id="fnref1" role="doc-noteref"><sup>1</sup></a>.</p>
-<p>Another failure is the mismatch between developers of the standard and users.</p>
+<p>Another failure is the mismatch between developers of the standard and users. There is an iherent gap in both interest and ability to engage with the technical details undergirding standards and their development between the developers of the standard and their users. In extreme cases, these interests may be at odds, as developers implement sophisticated mechanisms to automate the creation of the standard or advocate for more technically advanced mechanisms for evolving the standard, leaving potential users sidelined in the development of the standard, and limiting their ability to provide feedback about the practical implications of changes to the standards.</p>
 </section>
 <section id="sustainability" class="level2">
 <h2 class="anchored" data-anchor-id="sustainability">Sustainability</h2>

diff --git a/sections/02-challenges.embed.ipynb b/sections/02-challenges.embed.ipynb
@@ -12,15 +12,15 @@
     "\n",
     "It’s a story as old as time (or at least as old as standards): users fail to consider existing standards, or perceive an existing standard as not offering enough flexibility to cover some use case, and they embark on the development of a new standard [1].\n",
     "\n",
-    "Another failure is the mismatch between developers of the standard and users.\n",
+    "Another failure is the mismatch between developers of the standard and users. There is an iherent gap in both interest and ability to engage with the technical details undergirding standards and their development between the developers of the standard and their users. In extreme cases, these interests may be at odds, as developers implement sophisticated mechanisms to automate the creation of the standard or advocate for more technically advanced mechanisms for evolving the standard, leaving potential users sidelined in the development of the standard, and limiting their ability to provide feedback about the practical implications of changes to the standards.\n",
     "\n",
     "## Sustainability\n",
     "\n",
     "## The importance of automated validation\n",
     "\n",
     "[1] So old in fact that an oft-cited [XKCD comic](https://xkcd.com/927/) has been devoted to it."
    ],
-   "id": "fc5d07c5-466b-45ea-aa78-95bb67e95739"
+   "id": "29db7548-0b6c-4389-ad72-1e14d4609465"
   }
  ],
  "nbformat": 4,

diff --git a/sections/02-challenges.out.ipynb b/sections/02-challenges.out.ipynb
@@ -12,15 +12,15 @@
     "\n",
     "It’s a story as old as time (or at least as old as standards): users fail to consider existing standards, or perceive an existing standard as not offering enough flexibility to cover some use case, and they embark on the development of a new standard [1].\n",
     "\n",
-    "Another failure is the mismatch between developers of the standard and users.\n",
+    "Another failure is the mismatch between developers of the standard and users. There is an iherent gap in both interest and ability to engage with the technical details undergirding standards and their development between the developers of the standard and their users. In extreme cases, these interests may be at odds, as developers implement sophisticated mechanisms to automate the creation of the standard or advocate for more technically advanced mechanisms for evolving the standard, leaving potential users sidelined in the development of the standard, and limiting their ability to provide feedback about the practical implications of changes to the standards.\n",
     "\n",
     "## Sustainability\n",
     "\n",
     "## The importance of automated validation\n",
     "\n",
     "[1] So old in fact that an oft-cited [XKCD comic](https://xkcd.com/927/) has been devoted to it."
    ],
-   "id": "6798b8ab-3824-4505-b40e-a7669bc88fd4"
+   "id": "75b29011-8298-4412-b78a-59c5bd92a5e6"
   }
  ],
  "nbformat": 4,

diff --git a/sections/02-challenges.qmd b/sections/02-challenges.qmd
@@ -11,6 +11,14 @@ of a new standard [^1].
 been devoted to it.
 
 Another failure is the mismatch between developers of the standard and users.
+There is an iherent gap in both interest and ability to engage with the
+technical details undergirding standards and their development between the
+developers of the standard and their users. In extreme cases, these interests
+may be at odds, as developers implement sophisticated mechanisms to automate
+the creation of the standard or advocate for more technically advanced
+mechanisms for evolving the standard, leaving potential users sidelined in the
+development of the standard, and limiting their ability to provide feedback
+about the practical implications of changes to the standards.
 
 ## Sustainability
 

diff --git a/sections/xx-recommendations.embed.ipynb b/sections/xx-recommendations.embed.ipynb
@@ -13,7 +13,7 @@
     "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."
    ],
-   "id": "27488e4f-ea5e-4c68-9fde-1f997b13dbff"
+   "id": "cdcdbd2e-54fe-496e-8f6e-960a06ce4258"
   }
  ],
  "nbformat": 4,

diff --git a/sections/xx-recommendations.out.ipynb b/sections/xx-recommendations.out.ipynb
@@ -13,7 +13,7 @@
     "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."
    ],
-   "id": "c9436500-c7d3-4262-8bde-0832320d9e2d"
+   "id": "27417bdf-c4ae-4be9-b5e9-ae63f190a459"
   }
  ],
  "nbformat": 4,