added and adpated annotations

data/JTEI/10_2016-19/jtei-10-haaf-source.xml

@@ -213,7 +213,7 @@
             correction and annotation</ref><note rend="inside.parenthesis">See <bibl><title
                 level="a"><ptr type="software" xml:id="R3"
                   target="#dtaq"/><rs type="soft.name" ref="R3">DTAQ: Kollaborative Qualitätssicherung im Deutschen Textarchiv</rs></title>
-              (Collaborative Quality Assurance within the DTA), accessed January 28, 2017, <rs type="url" ref="#R3"><ptr
+              (Collaborative Quality Assurance within the DTA), accessed January 28, 2017, <rs type="soft.url" ref="#R3"><ptr
                 target="http://www.deutschestextarchiv.de/dtaq/about"/></rs></bibl>. On the process of
             quality assurance in the DTA, see, for example, <ref target="#haaf13" type="bibl">Haaf,
               Wiegand, and Geyken 2013</ref>.</note>) is a matter of supporting scholarly projects

data/JTEI/10_2016-19/jtei-10-romary-source.xml

@@ -1487,8 +1487,8 @@
           processes. In order to do this, it is necessary to make use of one or more ontologies,
           which could be locally defined within a project, and of external linked open data sources
           such as <ptr type="software" xml:id="R4"
-            target="#dbpedia"/><rs type="soft.name url" ref="#R4"><ref target="http://wiki.dbpedia.org/">DBpedia</ref></rs> and <ptr type="software" xml:id="R5"
-              target="#wikidata"/><rs type="soft.name url" ref="#R5"><ref
+            target="#dbpedia"/><rs type="soft.name soft.url" ref="#R4"><ref target="http://wiki.dbpedia.org/">DBpedia</ref></rs> and <ptr type="software" xml:id="R5"
+              target="#wikidata"/><rs type="soft.name soft.url" ref="#R5"><ref
                   target="https://www.wikidata.org/">Wikidata</ref></rs>, or some combination thereof. Within
           TEI dictionary markup, URIs for existing ontological entries can be referenced in the
             <gi>sense</gi>, <gi>usg</gi>, and <gi>ref</gi> elements as the value of the attribute

data/JTEI/11_2019-20/jtei-cc-ra-bermudez-sabel-137-source.xml

@@ -546,13 +546,13 @@
           in terms of both the specific tools that have been created for this method and the number
           of projects that apply it.<note>Tools include <ptr
                 type="software" xml:id="R6" target="#versioningmachine"/><rs
-                  type="soft.name url" ref="#R6"><ref target="http://v-machine.org/">Versioning Machine</ref></rs>, <ptr type="software" xml:id="R7"
-                    target="#collatex"/><rs type="soft.name url" ref="#R7"><ref
+                  type="soft.name soft.url" ref="#R6"><ref target="http://v-machine.org/">Versioning Machine</ref></rs>, <ptr type="software" xml:id="R7"
+                    target="#collatex"/><rs type="soft.name soft.url" ref="#R7"><ref
               target="https://collatex.net/">CollateX</ref></rs> (both
             the <ptr type="software" xml:id="R8" target="#java"/><rs type="soft.name" ref="#R8"
               >Java</rs> and <ptr type="software" xml:id="R9" target="#python"/><rs
               type="soft.name" ref="#R9">Python</rs> versions), and <ptr type="software" xml:id="R10"
-                target="#juxta"/><rs type="soft.name url" ref="#R10"><ref
+                target="#juxta"/><rs type="soft.name soft.url" ref="#R10"><ref
               target="http://www.juxtasoftware.org/">Juxta</ref></rs>. For
             representative projects using the parallel segmentation method see <ref
               target="http://scholarlyediting.org/2015/editions/lowelledition_wit-Courier.html"

data/JTEI/11_2019-20/jtei-cc-ra-hannessschlaeger-164-source.xml

@@ -122,8 +122,7 @@
           data set that has been published not only on <ptr type="software" xml:id="R1"
             target="#github"/><rs type="soft.name" ref="#R1">GitHub</rs>, but also in an
           <ptr type="software" xml:id="R4"
-            target="#existdb"/><ptr type="software" xml:id="R5"
-              target=""/><rs type="soft.name" ref="#R4">eXistdb</rs>-powered web application. This is by any standard a wonderful development for a
+            target="#existdb"/><rs type="soft.name" ref="#R4">eXistdb</rs>-powered web application. This is by any standard a wonderful development for a
           collection of textual data—and one that would not have been possible had the abstracts not
           been published under an open license, especially since their authors come from fourteen
           different countries.</p>
@@ -447,9 +446,9 @@
         <div xml:id="submission">
           <head>Submission of the Abstracts and <q>the joys of ConfTool</q></head>
           <p>As it is every year, the conference management software <ptr type="software" xml:id="R6"
-            target="#conftool"/><rs type="soft.name url" ref="#R6"><ref
+            target="#conftool"/><rs type="soft.name soft.url" ref="#R6"><ref
                 target="http://www.conftool.net/">ConfTool Pro</ref></rs><note>ConfTool Conference
-              Management Software, ConfTool GmbH, accessed August 23, 2019, <rs type="url" ref="#R6"><ptr
+                  Management Software, ConfTool GmbH, accessed August 23, 2019, <rs type="soft.url" ref="#R6"><ptr
                 target="http://www.conftool.net/"/></rs>.</note> was used for the submission of the
             abstracts of the 2016 TEI conference. When the Vienna team received access to the
             ConfTool system, the instance for the 2016 conference had been equipped with default
@@ -551,7 +550,7 @@
             abstracts inspired Peter Andorfer, a colleague of the editors at the Austrian Centre for
             Digital Humanities, to use this text collection to built an <ptr type="software" xml:id="R12"
               target="#existdbpoweredwebapplication"/><rs type="soft.name" ref="#R12">eXistdb-powered web
-                application</rs> (<rs type="soft.ref" ref="#R12"><ref type="bibl" target="#andorfer17">Andorfer and Hannesschläger
+                application</rs> (<rs type="soft.bib.ref" ref="#R12"><ref type="bibl" target="#andorfer17">Andorfer and Hannesschläger
                   2017</ref></rs>). In the context of licensing issues, it is important to mention that
             Andorfer was never approached by the editors or explicitly asked to process the TEI
             files, and he only informed the editors about the web application that he was building