Merge pull request #656 from Zack-83/master

Documentation: preferredNamespaceUri as a literal also in the examples
dgarijo · Dec 12, 2023 · cbc2097 · cbc2097
2 parents 395d061 + 4f8af35
commit cbc2097
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/doc/bestPractices/sections/checklist-en.html b/doc/bestPractices/sections/checklist-en.html
@@ -23,7 +23,7 @@ <h5>Example:</h5>
 @prefix rdf: &lt;http://www.w3.org/1999/02/22-rdf-syntax-ns#&gt; .
 @prefix vann: &lt;http://purl.org/vocab/vann/&gt; .
 &lt;https://w3id.org/example&gt; rdf:type owl:Ontology ;
-	vann:preferredNamespaceUri &lt;https://w3id.org/example#&gt; .
+	vann:preferredNamespaceUri "https://w3id.org/example" .
 </pre>
 
 <h4 class="list" id="prefix">Prefix [<em class="rfc2119" title="RECOMMENDED">RECOMMENDED</em>]</h4>
@@ -698,7 +698,7 @@ <h5>Example:</h5>
 
 <h4 class="list" id="status1">Status [<em class="rfc2119" title="OPTIONAL">OPTIONAL</em>]</h4>
 <p>
-Property indicating the usage status of the term. For example, whether the term is mature enough, whether it has been deprecated, curated, etc. Note that some of the properties proposed below, such as obo:IAO_0000114, have as range a set of fixed values. The <a href="https://github.com/UKGovLD/registry-core/wiki/Principles-and-concepts#status-and-life-cycle">registry vocabulary</a> proposes a hierarchy of status that may be used to represent terms as well (reg:statusAccepted, reg:statusValid, reg:statusDeprecated, etc.). 
+Property indicating the usage status of the term. For example, whether the term is mature enough, whether it has been deprecated, curated, etc. Note that some of the properties proposed below, such as obo:IAO_0000114, have as range a set of fixed values. The <a href="https://github.com/UKGovLD/registry-core/wiki/Principles-and-concepts#status-and-life-cycle">registry vocabulary</a> proposes a hierarchy of status that may be used to represent terms as well (reg:statusAccepted, reg:statusValid, reg:statusDeprecated, etc.).
 </p>
 
 <ul class="hlist"><strong>Properties you may use</strong>:

diff --git a/doc/metadataGuide/guide.md b/doc/metadataGuide/guide.md
@@ -141,7 +141,7 @@ The following `Turtle` code block shows sample annotations for each of the metad
     foaf:fundedBy <https://example.org/fundingOrganization> ;
     schema:funding <https://example.org/fundingGrant> ;
     widoco:introduction "A paragraph with the introduction section of the documentation about your resource"@en ;
-    widoco:rdfxmlSerialization "https://example.org/serialization/ontology.xml"^^xsd:anyURI ; 
+    widoco:rdfxmlSerialization "https://example.org/serialization/ontology.xml"^^xsd:anyURI ;
     owl:versionInfo "1.0.1" .
     #If content negotiation is enabled, the widoco:rdfxmlSerialization annotation may not be needed.
 ```