Apply suggestions from code review

typos, clarify, move files

.github/ISSUE_TEMPLATE/petab-extensions.md

@@ -9,7 +9,7 @@ assignees: ''
 ---
 
 **Name of the Extension**
-Please make sure that the extension name matches the regular expression `^[a-zA-Z_][\w-]*$`.
+Please make sure that the extension name matches the regular expression `^[a-zA-Z_][A-Za-z0-9_-]*$`.
 
 **Which problem would you like to address?**
 A clear and concise description of which use case you want to address and, if applicable, why the current specifications do not fulfill your requirements.
@@ -21,7 +21,7 @@ A clear and concise description of the changes you want to propose. Please descr
 A clear and concise description in what way the proposed changes introduce features that are orthogonal to the PEtab core specification.
 
 **List the extension library that implements validation checks**
-A link to the website or github repository that accompanies the proposed extension.
+A link to the website or GitHub repository that accompanies the proposed extension.
 
 **List the toolboxes that support the proposed standard**
-A link to the website or github repository that contains the software that implements support for the standard.
+A link to the website or GitHub repository that contains the software that implements support for the standard.

README.md

@@ -23,7 +23,7 @@ for example:
 
   - Specifying multiple simulation conditions with potentially shared parameters
 
-![PEtab files](doc/gfx/petab_files.png)
+![PEtab files](doc/v1/gfx/petab_files.png)
 
 ## Documentation
 

doc/development.rst

@@ -211,14 +211,16 @@ Requirements for new extensions:
   can ease or refine format restrictions imposed by PEtab core.
 * PEtab extensions should extend PEtab core with new orthogonal features or
   tasks, i.e., they should not make trivial changes to PEtab core.
-* PEtab extensions must be named according to ^[a-zA-Z][\w\-]*$.
+* PEtab extensions must be named according to ``^[a-zA-Z][a-zA-Z0-9_\-]*$``.
 * PEtab extensions must be versioned using semantic versioning.
 * If a PEtab extension changes the mathematical interpretation of a problem,
     it must appear in the PEtab YAML file.
 * There is at least one tool that supports the proposed extension.
 * The authors provide a library that provides test cases and implements
   validation checks for the proposed format.
 
+It is encouraged that (potential) extensions are informally discussed with the
+community as early as possible.
 Developers are free to develop any PEtab extension. To become an official
 PEtab extension, it needs to go through the following process.
 

doc/tutorial.rst

@@ -33,7 +33,7 @@ illustration purposes we slightly modified the SBML model and shortened
 some parts of the PEtab files. The full PEtab problem introduced in this
 tutorial is available `online <https://github.com/PEtab-dev/PEtab/tree/b50d000a5fb4cf37bf62315686acd2694e29e5fc/doc/tutorial>`_.
 
-.. figure:: gfx/tutorial_model.png
+.. figure:: tutorial/gfx/tutorial_model.png
    :width: 4.9846in
    :height: 5.5634in
 
@@ -65,7 +65,7 @@ phosphorylation levels of STAT5A and STAT5B as well as relative STAT5A
 abundance for different timepoints between 0 - 240 minutes after
 stimulation with erythropoietin (Epo):
 
-.. figure:: gfx/tutorial_data.png
+.. figure:: tutorial/gfx/tutorial_data.png
    :width: 6.2681in
    :height: 2.0835in
 
@@ -384,7 +384,7 @@ PEtab. The easiest tool to get started with is probably COPASI which comes
 with a graphical user interface
 (see https://github.com/copasi/python-petab-importer for further instructions).
 
-.. figure:: gfx/copasi_simulation.png
+.. figure:: tutorial/gfx/copasi_simulation.png
    :width: 4.9846in
    :height: 5.5634in
 

doc/v1/documentation_data_format.rst

@@ -31,7 +31,7 @@ least redundant way. Furthermore, we wanted to establish an intuitive, modular,
 machine- and human-readable and -writable format that makes use of existing
 standards.
 
-.. figure:: ../gfx/petab_scope_and_files.png
+.. figure:: gfx/petab_scope_and_files.png
    :alt: A common setup for data-based modeling studies and its representation in PEtab.
    :scale: 80%
 
@@ -64,7 +64,7 @@ and
 - (optional) A visualization file, which contains specifications how the data
   and/or simulations should be plotted by the visualization routines [TSV]
 
-.. figure:: ../gfx/petab_files.png
+.. figure:: gfx/petab_files.png
    :alt: Files constituting a PEtab problem
 
    **Figure 2: Files constituting a PEtab problem.**

doc/v2/documentation_data_format.rst

@@ -35,7 +35,7 @@ least redundant way. Furthermore, we wanted to establish an intuitive, modular,
 machine- and human-readable and -writable format that makes use of existing
 standards.
 
-.. figure:: ../gfx/petab_scope_and_files.png
+.. figure:: ../v1/gfx/petab_scope_and_files.png
    :alt: A common setup for data-based modeling studies and its representation in PEtab.
    :scale: 80%
 
@@ -73,7 +73,7 @@ of text-based files (
 - (optional) A mapping file, which allows mapping PEtab entity IDs to entity
   IDs in the model, which might not have valid PEtab IDs themselves [TSV]
 
-.. figure:: ../gfx/petab_files.png
+.. figure:: ../v1/gfx/petab_files.png
    :alt: Files constituting a PEtab problem
 
    **Figure 2: Files constituting a PEtab problem.**