diff --git a/doc/bestPractices/sections/checklist-en.html b/doc/bestPractices/sections/checklist-en.html index faab43e3..6791d360 100644 --- a/doc/bestPractices/sections/checklist-en.html +++ b/doc/bestPractices/sections/checklist-en.html @@ -23,7 +23,7 @@
Example:
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . @prefix vann: <http://purl.org/vocab/vann/> . <https://w3id.org/example> rdf:type owl:Ontology ; - vann:preferredNamespaceUri "https://w3id.org/example" . + vann:preferredNamespaceUri <https://w3id.org/example#> .

Prefix [RECOMMENDED]

@@ -593,6 +593,24 @@
Example:
rdfs:seeAlso <http://www.wikipathways.org/> . +

Code repository (vocabulary maintenance) [OPTIONAL]

+

+Property used to indicate if there is a public code repository where the vocabulary is maintained. This information may be helpful to the adopter of your vocabulary, in order to raise issues and see current discussions. +

+ + + +
Example:
+
+@prefix owl: <http://www.w3.org/2002/07/owl#> .
+@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
+<http://vocabularies.wikipathways.org/wpTypes#> a owl:Ontology ;
+    schema:codeRepository "https://github.com/user/repo"^^xsd:anyURI; .
+
+

Term checklist of metadata properties back to ToC

These metadata terms are targeted towards describing the classes, properties and data properties of the ontology. Adding them as part of the ontology is crucial for potential reusers: @@ -698,7 +716,7 @@
Example:

Status [OPTIONAL]

-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 registry vocabulary 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 registry vocabulary proposes a hierarchy of status that may be used to represent terms as well (reg:statusAccepted, reg:statusValid, reg:statusDeprecated, etc.).