Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation: preferredNamespaceUri as a literal also in the examples #656

Merged
merged 4 commits into from
Dec 12, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions doc/bestPractices/sections/checklist-en.html
Original file line number Diff line number Diff line change
Expand Up @@ -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>
Expand Down Expand Up @@ -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>:
Expand Down
4 changes: 2 additions & 2 deletions doc/metadataGuide/guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -129,7 +129,7 @@ The following `Turtle` code block shows sample annotations for each of the metad
dct:creator "Daniel Garijo"@en ,"Maria Poveda-Villalon"@en ;
dct:license <http://creativecommons.org/licenses/by/2.0/> ;
vann:preferredNamespacePrefix "exo"@en ;
vann:preferredNamespaceUri> "https://w3id.org/example" ;
vann:preferredNamespaceUri "https://w3id.org/example" ;
schema:citation "Cite this vocabulary as: Garijo, D. and Poveda-Villalón, M. The example ontology 1.0.1."@en ;
rdfs:comment "An example vocabulary designed to illustrate how to publish vocabularies on the Web following the FAIR principles. This vocabulary describes three simple classes with 3 properties and a data property."@en ;
rdfs:label "Example" ;
Expand All @@ -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.
```
Expand Down