Normalized authors block

content/docs/extensions/camtrap-data-package.md

@@ -4,7 +4,7 @@ title: Camera Trap Data Package
 
 <table>
   <tr>
-    <th>Author(s)</th>
+    <th>Authors</th>
     <td>Peter Desmet, Jakub W. Bubnicki, Camtrap DP Development Team</td>
   </tr>
 </table>

content/docs/extensions/fiscal-data-package.md

@@ -4,7 +4,7 @@ title: Fiscal Data Package
 
 <table>
   <tr>
-    <th>Author(s)</th>
+    <th>Authors</th>
     <td>Paul Walsh, Rufus Pollock, Tryggvi Björgvinsson, Steve Bennett, Adam Kariv, Dan Fowler</td>
   </tr>
 </table>

content/docs/extensions/tabular-data-package.md

@@ -4,7 +4,7 @@ title: Tabular Data Package
 
 <table>
   <tr>
-    <th>Author(s)</th>
+    <th>Authors</th>
     <td>Paul Walsh, Rufus Pollock, Martin Keegan</td>
   </tr>
 </table>

content/docs/extensions/tabular-data-resource.md

@@ -4,7 +4,7 @@ title: Tabular Data Resource
 
 <table>
   <tr>
-    <th>Author(s)</th>
+    <th>Authors</th>
     <td>Paul Walsh, Rufus Pollock</td>
   </tr>
 </table>

content/docs/recipes/caching-of-resources.md

@@ -2,6 +2,13 @@
 title: Caching of Resources
 ---
 
+<table>
+  <tr>
+    <th>Authors</th>
+    <td>TODO</td>
+  </tr>
+</table>
+
 All Frictionless Data specifications allow for referencing resources via http or a local filesystem.
 
 In the case of remote resources via http, there is always the possibility that the remote server will be unavailable, or, that the resource itself will be temporarily or permanently removed.

content/docs/recipes/compression-of-resources.md

@@ -2,6 +2,13 @@
 title: Compression of Resources
 ---
 
+<table>
+  <tr>
+    <th>Authors</th>
+    <td>TODO</td>
+  </tr>
+</table>
+
 It can be argued that applying compression to data resources can make data package publishing more cost-effective and sustainable. Compressing data resources gives publishers the benefit of reduced storage and bandwidth costs and gives consumers the benefit of shorter download times.
 
 ## Implementations

content/docs/recipes/data-catalog.md

@@ -2,6 +2,13 @@
 title: Data Catalog
 ---
 
+<table>
+  <tr>
+    <th>Authors</th>
+    <td>TODO</td>
+  </tr>
+</table>
+
 There are scenarios where one needs to describe a collection of data packages, such as when building an online registry, or when building a pipeline that ingests multiple datasets.
 
 In these scenarios, the collection can be described using a "Catalog", where each dataset is represented as a single resource which has:

content/docs/recipes/data-dependencies.md

@@ -2,6 +2,13 @@
 title: Data Dependencies
 ---
 
+<table>
+  <tr>
+    <th>Authors</th>
+    <td>TODO</td>
+  </tr>
+</table>
+
 Consider a situation where data packages are part of a tool chain that, say, loads all of the data into an SQL db. You can then imagine a situation where one requires package A which requires package B + C.
 
 In this case you want to specify that A depends on B and C -- and that "installing" A should install B and C. This is the purpose of `dataDependencies` property.

content/docs/recipes/data-package-version.md

@@ -2,6 +2,13 @@
 title: Data Package Version
 ---
 
+<table>
+  <tr>
+    <th>Authors</th>
+    <td>TODO</td>
+  </tr>
+</table>
+
 ## Specification
 
 The Data Package version format follows the [Semantic Versioning](http://semver.org) specification format: MAJOR.MINOR.PATCH

content/docs/recipes/enum-labels-and-ordering.md

@@ -2,6 +2,13 @@
 title: Enum Labels and Ordering
 ---
 
+<table>
+  <tr>
+    <th>Authors</th>
+    <td>TODO</td>
+  </tr>
+</table>
+
 ## Overview
 
 Many software packages for manipulating and analyzing tabular data have special

content/docs/recipes/external-foreign-keys.md

@@ -2,6 +2,13 @@
 title: External Foreign Keys
 ---
 
+<table>
+  <tr>
+    <th>Authors</th>
+    <td>TODO</td>
+  </tr>
+</table>
+
 A foreign key is a reference where values in a field (or fields) in a Tabular Data Resource link to values in a field (or fields) in a Tabular Data Resource in the same or in another Tabular Data Package.
 
 This pattern allows users to link values in a field (or fields) in a Tabular Data Resource to values in a field (or fields) in a Tabular Data Resource in a different Tabular Data Package.

content/docs/recipes/json-data-resources.md

@@ -2,6 +2,13 @@
 title: JSON Data Resources
 ---
 
+<table>
+  <tr>
+    <th>Authors</th>
+    <td>TODO</td>
+  </tr>
+</table>
+
 A simple format to describe a single structured JSON data resource. It includes support both for metadata such as author and title and a [schema](https://json-schema.org/) to describe the data.
 
 ## Introduction

content/docs/recipes/language-support.md

@@ -2,6 +2,13 @@
 title: Language Support
 ---
 
+<table>
+  <tr>
+    <th>Authors</th>
+    <td>TODO</td>
+  </tr>
+</table>
+
 Language support is a different concern to translation support. Language support deals with declaring the default language of a descriptor and the data it contains in the resources array. Language support makes no claim about the presence of translations when one or more languages are supported in a descriptor or in data. Via the introduction of a `languages` array to any descriptor, we can declare the default language, and any other languages that `SHOULD` be found in the descriptor and the data.
 
 ## Implementations

content/docs/recipes/metadata-in-table-schema.md

@@ -2,6 +2,13 @@
 title: Metadata in Table Schema
 ---
 
+<table>
+  <tr>
+    <th>Authors</th>
+    <td>TODO</td>
+  </tr>
+</table>
+
 ## Overview
 
 Table Schemas need their own metadata to be stand-alone and interpreted without relying on other contextual information (Data Package metadata for example). Adding metadata to describe schemas in a structured way would help users to understand them and would increase their sharing and reuse.

content/docs/recipes/nested-resources.md

@@ -2,6 +2,13 @@
 title: Nested Resources
 ---
 
+<table>
+  <tr>
+    <th>Authors</th>
+    <td>TODO</td>
+  </tr>
+</table>
+
 Some datasets need to contain a Zip file (or tar, other formats) containing a
 set of files.
 

content/docs/recipes/private-properties.md

@@ -2,8 +2,12 @@
 title: Private Properties
 ---
 
-[issues]: https://github.com/frictionlessdata/specs/issues
-[repo]: https://github.com/frictionlessdata/specs
+<table>
+  <tr>
+    <th>Authors</th>
+    <td>TODO</td>
+  </tr>
+</table>
 
 Some software that implements the Frictionless Data specifications may need to store additional information on the various Frictionless Data descriptors.
 

content/docs/recipes/translation-support.md

@@ -2,6 +2,13 @@
 title: Translation Support
 ---
 
+<table>
+  <tr>
+    <th>Authors</th>
+    <td>TODO</td>
+  </tr>
+</table>
+
 Following on from a general pattern for language support, and the explicit support of metadata translations in Frictionless Data descriptors, it would be desirable to support translations in source data.
 
 We currently have two patterns for this in discussion. Both patterns arise from real-world implementations that are not specifically tied to Frictionless Data.

content/docs/specifications/data-package.md

@@ -6,7 +6,7 @@ sidebar:
 
 <table>
   <tr>
-    <th>Author(s)</th>
+    <th>Authors</th>
     <td>Paul Walsh, Rufus Pollock</td>
   </tr>
   <tr>

content/docs/specifications/data-resource.md

@@ -6,7 +6,7 @@ sidebar:
 
 <table>
   <tr>
-    <th>Author(s)</th>
+    <th>Authors</th>
     <td>Paul Walsh, Rufus Pollock</td>
   </tr>
   <tr>

content/docs/specifications/extensions.md

@@ -1,6 +1,7 @@
 ---
 title: Extensions
 sidebar:
+  hidden: true
   order: 5
 ---
 

content/docs/specifications/glossary.md

@@ -1,9 +1,17 @@
 ---
 title: Glossary
 sidebar:
+  hidden: true
   order: 6
 ---
 
+<table>
+  <tr>
+    <th>Authors</th>
+    <td>Paul Walsh, Rufus Pollock</td>
+  </tr>
+</table>
+
 A dictionary of special terms for the Data Package Standard.
 
 ## Language

content/docs/specifications/security.md

@@ -6,7 +6,7 @@ sidebar:
 
 <table>
   <tr>
-    <th>Author(s)</th>
+    <th>Authors</th>
     <td>Johannes Jander</td>
   </tr>
 </table>

content/docs/specifications/table-dialect.md

@@ -6,7 +6,7 @@ sidebar:
 
 <table>
   <tr>
-    <th>Author(s)</th>
+    <th>Authors</th>
     <td>Rufus Pollock</td>
   </tr>
   <tr>

content/docs/specifications/table-schema.md

@@ -6,7 +6,7 @@ sidebar:
 
 <table>
   <tr>
-    <th>Author(s)</th>
+    <th>Authors</th>
     <td>Paul Walsh, Rufus Pollock</td>
   </tr>
   <tr>