Add attribution section to CWL best practices

Author: MarkRobbo

src/main/resources/templates/about.html

@@ -44,7 +44,7 @@ <h1>About</h1>
                 understanding and discovery as well as encouraging best practices when writing workflows and their
                 tooling.</p>
 
-            <p>Cite as: <code><a href="https://doi.org/10.5281/zenodo.823534">10.5281/zenodo.823534</a></code></p>
+            <p>Cite as: <code><a href="https://doi.org/10.7490/f1000research.1114375.1">10.7490/f1000research.1114375.1</a></code></p>
 
             <p>A <a href="https://doi.org/10.5281/zenodo.823535">Technical Report for this project can be viewed here</a>.</p>
 
@@ -133,16 +133,38 @@ <h2>Use of Subworkflows</h2>
             <p class="use">Subworkflows are simplified in the visualisations and are linked as a different workflow in the
             <code>Step</code> tables on each workflow page</p>
 
+            <h2>Attribution</h2>
+            <p class="recommendation">Include attribution information in your workflow and tool descriptions</p>
+            <p class="recommendation_more">
+                For example, to attribute a person as the creator of a workflow or tool with name, email and
+                ORCID information, include the following statements at the top level:<br />
+<pre>
+$namespaces: { s: "http://schema.org/" }
+s:creator:
+- class: s:Person
+  s:name: Mark Robinson
+  s:email: mailto:[email protected]
+  s:sameAs:
+  - id: http://orcid.org/0000-0002-8184-7507
+</pre>
+            </p>
+            <p class="why">Attribution information allows your workflows and tooling to be used by others while
+            recognising your contributions. The inclusion of an <a href="https://orcid.org/">ORCID</a> allows you to
+            be uniquely identified from other researchers</p>
+            <p class="use">CWLViewer parses attribution information for inclusion in the Research Object Manifest from
+            both the Git commit logs and from the CWL descriptions themselves when expressed in the
+            <a href="http://schema.org/creator">http://schema.org/creator</a> format as above</p>
+
             <h2>Licensing</h2>
             <p class="recommendation">Include a <a href="https://opensource.org/licenses">OSI approved open source license</a>
             in your workflow and tool descriptions</p>
             <p class="recommendation_more">
                 For example, the following two statements at the top level of a workflow or tool description licenses it
                 under the <a href="https://www.apache.org/licenses/LICENSE-2.0">Apache V2.0 License</a>:<br />
-                <code>
-                    $namespaces: { s: "http://schema.org/" }<br />
-                    s:license: "https://www.apache.org/licenses/LICENSE-2.0"
-                </code>
+<pre>
+$namespaces: { s: "http://schema.org/" }
+s:license: "https://www.apache.org/licenses/LICENSE-2.0"
+</pre>
             </p>
             <p class="why">A permissive open source license allows others to remix and use your tooling and workflows
             to prevent the community from repeating development effort, allowing everyone to benefit</p>