adding HTML documentation for publication

Author: clams-bot

CHANGELOG.md

@@ -1,4 +1,16 @@
 
+## releasing 1.3.0 (2024-07-22)
+### Overview
+This version added two universal runtime parameters that make some aspects of the runtime environment are recorded in the views' metadata. 
+
+
+### Additions
+- `hwFetch` universal parameter will record CPU architecture and CUDA devices in `view.metadata.appRunningHardware` 
+- `runningTime` universal parameter will record app's running time in `view.metadata.appRunningTime`
+- See https://github.com/clamsproject/clams-python/issues/236 for rationale behind 
+
+
+
 ## releasing 1.2.6 (2024-07-15)
 ### Overview
 Patch release to update mmif SDK version, and minor improvements

docs/.doctrees/appmetadata.doctree

@@ -91,7 +91,7 @@ input specification can be as simple as the following:
       # and more app metadata fields, 
     }
     
-In the above example, the developer is declaring the app is expecting ``Token``annotation objects, with a ``posTagSet`` 
+In the above example, the developer is declaring the app is expecting ``Token`` annotation objects, with a ``posTagSet`` 
 property of which value is the URL of the Penn Treebank POS tag set, *verbatim*, in the input MMIF, and all other 
 existing annotation types in the input MMIF will be ignored during processing. There are some *grammar* of how this 
 ``input`` list can be written. 

docs/.doctrees/autodoc/clams.app.doctree

@@ -6,3 +6,15 @@ Module contents
 
 .. autoclass:: clams.appmetadata.AppMetadata
    :members:
+
+.. autoclass:: clams.appmetadata.Input
+   :members:
+   :inherited-members:
+
+.. autoclass:: clams.appmetadata.Output
+   :members:
+   :inherited-members:
+
+.. autoclass:: clams.appmetadata.RuntimeParameter
+   :members:
+   :inherited-members:

docs/.doctrees/autodoc/clams.appmetadata.doctree

@@ -37,7 +37,7 @@
             clams-python
           </a>
               <div class="version">
-                1.2.6
+                1.3.0
               </div>
 <div role="search">
   <form id="rtd-search-form" class="wy-form" action="search.html" method="get">

docs/.doctrees/environment.pickle

@@ -37,7 +37,7 @@
             clams-python
           </a>
               <div class="version">
-                1.2.6
+                1.3.0
               </div>
 <div role="search">
   <form id="rtd-search-form" class="wy-form" action="search.html" method="get">
@@ -182,7 +182,7 @@ <h5>Simple case - using types as defined in the vocabularies<a class="headerlink
 <span class="p">}</span>
 </pre></div>
 </div>
-<p>In the above example, the developer is declaring the app is expecting <code class="docutils literal notranslate"><span class="pre">Token``annotation</span> <span class="pre">objects,</span> <span class="pre">with</span> <span class="pre">a</span> <span class="pre">``posTagSet</span></code>
+<p>In the above example, the developer is declaring the app is expecting <code class="docutils literal notranslate"><span class="pre">Token</span></code> annotation objects, with a <code class="docutils literal notranslate"><span class="pre">posTagSet</span></code>
 property of which value is the URL of the Penn Treebank POS tag set, <em>verbatim</em>, in the input MMIF, and all other
 existing annotation types in the input MMIF will be ignored during processing. There are some <em>grammar</em> of how this
 <code class="docutils literal notranslate"><span class="pre">input</span></code> list can be written.</p>