diff --git a/DummyOntoPASSES.ttl b/DummyOntoPASSES.ttl index 8842453..c0ef71b 100644 --- a/DummyOntoPASSES.ttl +++ b/DummyOntoPASSES.ttl @@ -46,7 +46,7 @@ "active"@en ; doap:repository ; ; - ; + ; dcterms:isReferencedBy ; dcterms:bibliographicCitation "TIB (2023): DummyOntoPASSES. An ontology demonstrating rich ontology metadata. PURL: https://www.purl.org/ontologymetadata/DummyOntoPASSES."@en ; pav:derivedFrom ; diff --git a/MetadataGuide.html b/MetadataGuide.html index 3bf9615..34add2b 100644 --- a/MetadataGuide.html +++ b/MetadataGuide.html @@ -1045,7 +1045,7 @@

4.11 Ontology distributions/ produc

4.12 Application example

How to use an ontology is often helpfully demonstrated by application examples and visualizations that give a glimpse about how the ontology can be used to structure actual data. If you have such application examples, these might be better found, if you link to them from the ontology. These application examples could be part of the ontology documentation, formal serializations applying the ontology or even technical applications that make use of the ontology.

-

Recommended property: https://vocab.org/vann/example

+

Recommended property: http://purl.org/vocab/vann/example

Example (text/turtle):

<http://www.w3.org/ns/dcat> rdf:type owl:Ontology ;
     vann:example <https://www.w3.org/TR/vocab-dcat-2/#collection-of-examples> .
@@ -1100,7 +1100,7 @@ 
4.15 Ontology sources (derived from)<
 
  • sh:nodeKind sh:IRI
    • 
 
 
    4.16 Ontology root classes
    
-
    You should explicitly declare the ontology's preferred root classes. Display tools like the TIB Terminology Service and other OLS-based services [9], [10] can pick specific, user-defined classes for rendering the ontology class hierarchy. This is especially helpful, when an ontology imports a lot of classes from other ontologies. The repsective classes need to be provided via their identifier.
    
+
    You should explicitly declare the ontology's preferred root classes. Display tools like the TIB Terminology Service and other OLS-based services [9], [10] can pick specific, user-defined classes for rendering the ontology class hierarchy. This is especially helpful, when an ontology imports a lot of classes from other ontologies. The respective classes need to be provided via their identifier.
    
 
    Recommended property: http://purl.obolibrary.org/obo/IAO_0000700
    
 
    Example (text/turtle):
    
 
    <https://www.purl.org/SomeOntology> rdf:type owl:Ontology ;
@@ -1539,7 +1539,7 @@ 
    5.24 Version notes
    
 
    
 
    Alternative properties:
    
 
 
    SHACL validation rules:
    
 
      
@@ -1744,7 +1744,7 @@ 
      6 Tabular overview
      
 
 4.12
 Application example
-https://vocab.org/vann/example
+http://purl.org/vocab/vann/example
 
 x
 
diff --git a/MetadataGuide.md b/MetadataGuide.md
index 78247fa..79c0b6f 100644
--- a/MetadataGuide.md
+++ b/MetadataGuide.md
@@ -758,7 +758,7 @@ SHACL validation rules:
 
 How to use an ontology is often helpfully demonstrated by application examples and visualizations that give a glimpse about how the ontology can be used to structure actual data. If you have such application examples, these might be better found, if you link to them from the ontology. These application examples could be part of the ontology documentation, formal serializations applying the ontology or even technical applications that make use of the ontology.
 
-Recommended property: 
+Recommended property: 
 
 Example (text/turtle):
 
@@ -1487,7 +1487,7 @@ Example (text/turtle):
 
 Alternative properties:
 
-* 
+* 
 
 SHACL validation rules:
 
@@ -1520,7 +1520,7 @@ SHACL validation rules:
 | 4.9     | Status                                           |                                         |           | x           |          | 0...1       |
 | 4.10    | Code repository                                  |                                      |           | x           |          | 0...1       |
 | 4.11    | Distributions/ products                          |                                       |           | x           |          | 0…*         |
-| 4.12    | Application example                              |                                               |           | x           |          | 0…*         |
+| 4.12    | Application example                              |                                               |           | x           |          | 0…*         |
 | 4.13    | Related resource(s)                              |                                          |           | x           |          | 0…*         |
 | 4.14    | Citation suggestion                              |                               |           | x           |          | 0…*         |
 | 4.15    | Ontology sources (derived from)                  |                                              |           | x           |          | 0…*         |
diff --git a/MetadataGuide.pdf b/MetadataGuide.pdf
index e0fc91b..b209248 100644
Binary files a/MetadataGuide.pdf and b/MetadataGuide.pdf differ
diff --git a/OntoMetadataShape.ttl b/OntoMetadataShape.ttl
index fa6fdcd..50ce74d 100644
--- a/OntoMetadataShape.ttl
+++ b/OntoMetadataShape.ttl
@@ -47,7 +47,7 @@ ontometa: rdf:type owl:Ontology ;
      "RDF(S), OWL, SHACL"@en ;
     dcterms:bibliographicCitation "Arndt, S., Ganske, A., Hauschke, C., Strömert, P., & Vogt, L. (2024). Terminology Metadata Recommendations by TIB. Zenodo. https://doi.org/10.5281/zenodo.11103070 (latest version)";
       ,  ;
-     
+     
 .
 
 # Start of the Ontology Metadata Shape
@@ -62,7 +62,6 @@ ontometa:OntologyMetadataShape a sh:NodeShape ;
         sh:path [sh:alternativePath (rdfs:label skos:prefLabel dc:title dcterms:title schema:name schema:headline) ] ; 
         sh:severity sh:Warning ;
         sh:minCount 1 ;
-        # sh:message """The ontology does not include its own title. Please provide it if known."""@en ; # optimized message for current TIB TS implementation
         sh:message """You must add an ontology title or label. The title should be an rdf:langString.\nRecommended property: .\nExample statement (text/turtle):  dcterms:title \"Some Ontology\"@en .\nNeed help? Learn more about SHACL: https://www.w3.org/TR/2017/REC-shacl-20170720/"""@en ;
         sh:description "This shape checks whether the ontology has a title or label. It produces a warning message if the title is missing. The ontology title is mandatory."@en ;
         sh:name "Ontology title"@en ;
@@ -85,7 +84,6 @@ ontometa:OntologyMetadataShape a sh:NodeShape ;
         sh:severity sh:Warning;
         sh:minCount 1 ;
         sh:maxCount 1 ;
-        # sh:message """The ontology does not declare its preferred prefix. Please provide it if known."""@en ; # optimized message for current TIB TS implementation
         sh:message """You must declare at most one preferred namespace prefix or acronym for the ontology.\nIt must not contain hyphens or other special characters and should be written in lowercase.\nRecommended property: \nExample statement (text/turtle):  vann:preferredNamespacePrefix \"so\"^^xsd:string .\nNeed help? Learn more about SHACL: https://www.w3.org/TR/2017/REC-shacl-20170720/"""@en ;
         sh:description "This shape checks whether the ontology declares a preferred namespace prefix. It produces a warning message if the ontology does not declare a preferred namespace prefix."@en ;
         sh:name "Preferred ontology prefix/ acronym"@en ;
@@ -181,7 +179,6 @@ ontometa:OntologyMetadataShape a sh:NodeShape ;
 
             # [sh:hasValue <> ;] 
             );
-        # sh:message """The ontology does not declare its own license. Please provide it, if known."""@en ; # optimized message for current TIB TS 
         sh:message """You must provide exactly one ontology license.\nThe license must be open (Read more about open licenses at https://opendefinition.org/licenses/).\nThe license must be given as an IRI from the following list:\n\n    - \n    - \n    - \n    - \n    - \n    - \n    - \n    - \n    - \n    - \n\nRecommended property: \nExample statement (text/turtle):  dcterms:license  .\nYou want to use a different open license? File an issue at https://gitlab.com/TIBHannover/terminology/tib-terminology-service-issue-tracker/-/issues\nNeed help? Learn more about SHACL: https://www.w3.org/TR/2017/REC-shacl-20170720/"""@en ;
         sh:description "This shape checks whether the ontology provides a license IRI from a list of accepted open licenses. It produces a warning message if not."@en ;
         sh:name "Ontology license"@en ;
@@ -224,13 +221,11 @@ ontometa:OntologyMetadataShape a sh:NodeShape ;
         sh:path  [sh:alternativePath (dc:creator dcterms:creator schema:creator pav:createdBy prov:wasAttributedTo schema:accountablePerson schema:author)];
         sh:severity sh:Warning ;
         sh:minCount 1;
-        # sh:message """The ontology does not name its creators. Please provide them if known. This information is required for licenses that require attribution. Use ORCID, ROR or comparable identifiers for people and organisations if available."""@en ; # optimized message for current TIB TS 
         sh:message """You must add the ontology creators.\nYou must list at least one person who was involved in developing the ontology.\nCreators should be referenced via PIDs, e.g. ORCIDs for persons and RORs for organisations.\nIf an ontology is developed by a larger group, it is recommended to give the organization or project identifier as the creator and list individual persons as contributors.\nRecommended property: \nExample statement 1 (text/turtle):   .  rdf:type foaf:Person .\nPlain name strings could be provided in addition (for readability).\nExample statement 2 (text/turtle):\n      \n     rdf:type foaf:Person ;  "Max" ;\n         "Muster" .\nNeed help? Learn more about SHACL: https://www.w3.org/TR/2017/REC-shacl-20170720/"""@en ;
         sh:description "This shape checks whether the ontology provides information about its creator. It produces a warning message if no creator information is present."@en ;
         sh:name "Ontology creator(s)"@en ;
     ] ;
 
-### discuss: switch to string/ literal following "FirstName LastName (ORCID)" 
     sh:property [
         sh:path  [sh:alternativePath (dc:creator dcterms:creator schema:creator pav:createdBy prov:wasAttributedTo schema:accountablePerson schema:author)];
         sh:severity sh:Info ;
@@ -249,7 +244,6 @@ ontometa:OntologyMetadataShape a sh:NodeShape ;
         sh:severity sh:Warning ;
         sh:minCount 1 ;
         sh:maxCount 1 ;
-        # sh:message """The ontology does not declare a versionIRI. Please provide it, if known."""@en ; # optimized message for current TIB TS 
         sh:message """You must add a versionIRI to the ontology.\nThe versionIRI should be stable and resolvable, i.e. a fixed version of the ontology should be retrievable from the provided IRI.\nIt is recommended to use semantic versioning (cf. https://semver.org/) or OBO style date-based versioning (http://obofoundry.org/principles/fp-004-versioning.html).\nRecommended property: \nExample statement 1 (text/turtle):   .\nExample statement 2 (text/turtle):    .\nExample statement 3 (text/turtle):    .\nNeed help? Learn more about SHACL: https://www.w3.org/TR/2017/REC-shacl-20170720/"""@en ;
         sh:description "This shape checks whether the ontology provids exactly one versionIRI. It produces a warning message if none is found."@en ;
         sh:name "Ontology version IRI"@en ;
@@ -271,7 +265,6 @@ ontometa:OntologyMetadataShape a sh:NodeShape ;
         sh:severity sh:Warning ;
         sh:minCount 1;
         sh:maxCount 1 ;
-        # sh:message """The ontology does not declare its creation date. Please provide it, if known. Use the xsd:dateTime format to do so (e.g. 2024-12-12T11:18:44)"""@en ; # optimized message for current TIB TS 
         sh:message """You must add a creation date to the ontology.\nYou must provide exactly one date in xsd:dateTime format.\nRecommended property: \nExample statement (text/turtle):  dcterms:created \"2020-11-19T00:00:00\"^^xsd:dateTime .\nNeed help? Learn more about SHACL: https://www.w3.org/TR/2017/REC-shacl-20170720/"""@en ;
         sh:description "This shape checks whether the ontology provides its creation date. It produces a warning message if not."@en ;
         sh:name "Ontology creation date"@en ;
@@ -293,7 +286,6 @@ ontometa:OntologyMetadataShape a sh:NodeShape ;
         sh:path [sh:alternativePath (dcterms:abstract )] ;
         sh:severity sh:Warning ;
         sh:minCount 1 ;
-        # sh:message """The ontology does not contain an abstract. Please provide it, if knwon."""@en ; # optimized message for current TIB TS 
         sh:message """You must provide a short abstract about the ontology and its scope.\nRecommended property: \nExample statement (text/turtle):  dcterms:abstract \"SomeOntology defines a range of classes and properties which can be applied to do stuff in a particular domain.\"@en , \"SomeOntology definiert eine Reihe von Klassen und Properties, die in einer bestimmten Domäne verwendet werden können, um etwas damit zu tun.\"@de .\nNeed help? Learn more about SHACL: https://www.w3.org/TR/2017/REC-shacl-20170720/"""@en ;
         sh:description "This shape checks whether the ontology provides an abstract. It produces an info message if not."@en ;
         sh:name "Ontology abstract"@en ;
@@ -348,7 +340,6 @@ ontometa:OntologyMetadataShape a sh:NodeShape ;
         sh:nodeKind sh:IRI ;
         sh:minCount 1 ;
         sh:maxCount 1 ;
-        # sh:message """The ontology does not contain the link to its documentation. Please provide it, if known."""@en ; # optimized message for current TIB TS
         sh:message """You must provide an IRI to the ontology documentation.\nRecommended property: \nExample statement (text/turtle):  premis:documentation  .\nNeed help? Learn more about SHACL: https://www.w3.org/TR/2017/REC-shacl-20170720/"""@en ;
         sh:description "This shape checks whether the ontology provides a link to its documentation. It produces warning message if it does not."@en ;
         sh:name "Ontology documentation"@en ; 
@@ -542,7 +533,7 @@ ontometa:OntologyMetadataShape a sh:NodeShape ;
         sh:maxCount 1;
         sh:xone (
         # tbd: not all are relevant or digestable by the TS
-        # for the TS rdf+xml, turtle and obo are confirmed
+        # for the TS rdf+xml, turtle and obo are confirmed, obo will not be supported by OLS4
         # no expected value for obo ontologies > Ontorowser mentions application/obo and text/obo, but these are specific to the service, not officially acknowledged: https://github.com/Novartis/ontobrowser/blob/master/doc/web_services.md
             # [sh:hasValue  ;] 
             # [sh:hasValue  ;] 
@@ -630,11 +621,11 @@ ontometa:OntologyMetadataShape a sh:NodeShape ;
 ## Application example
 ### status: developer and external review needed
     sh:property [
-        sh:path  ;
+        sh:path  ;
         sh:severity sh:Info ;
         sh:minCount 1 ;
         sh:nodeKind sh:IRI ;
-        sh:message """You should provide a link to an application example of the ontology.\nIdeally, the ontology provides a PID to e.g. a publication describing applications of the ontology, or directly to an application or online service that uses the ontology.\nRecommended property: \nExample statement (text/turtle):  vann:example  .\nNeed help? Learn more about SHACL: https://www.w3.org/TR/2017/REC-shacl-20170720/"""@en ;
+        sh:message """You should provide a link to an application example of the ontology.\nIdeally, the ontology provides a PID to e.g. a publication describing applications of the ontology, or directly to an application or online service that uses the ontology.\nRecommended property: \nExample statement (text/turtle):  vann:example  .\nNeed help? Learn more about SHACL: https://www.w3.org/TR/2017/REC-shacl-20170720/"""@en ;
         sh:description "This shape checks whether the ontology provides links to application examples. It produces an info message if the information is missing or not provided as an IRI."@en ;
         sh:name "Application example"@en ;
     ] ;
@@ -928,6 +919,7 @@ ontometa:OntologyMetadataShape a sh:NodeShape ;
 
 ## Ontology logo/ depiction/ related visualizations
 ### status: developer and external review needed
+### needs to be split for forms and validation? > logo should be its own datum, depictions and visualizations can go together
 
     sh:property [
         sh:path [sh:alternativePath (    )] ;
@@ -948,7 +940,7 @@ ontometa:OntologyMetadataShape a sh:NodeShape ;
         sh:nodeKind sh:IRI ;
         sh:message """You should provide the ontology's identifiers as IRIs.\nThe identifier used as the base uri of the ontology should be provided with .\nRecommended property: \nExample statement (text/turtle):  dcterms:identifier  .\nNeed help? Learn more about SHACL: https://www.w3.org/TR/2017/REC-shacl-20170720/"""@en ;
         sh:description "This shape checks whether the ontology's related identifiers are provided as IRIs. It produces an info message if they are not."@en ;
-        sh:name "Related identifiers"@en ;
+        sh:name "Alternative identifiers of the ontology"@en ;
     ];
 
 ## Development environment
@@ -1047,7 +1039,6 @@ ontometa:OntologyMetadataShape a sh:NodeShape ;
         sh:path [sh:alternativePath (owl:versionInfo pav:version)];
         sh:severity sh:Info ;
         sh:xone ( [sh:datatype xsd:string ;] [sh:datatype rdf:langString ;] );
-        #        sh:datatype xsd:string ;
         sh:message """You should provide textual information about the ontology version as an xsd:string.\nIt is recommended to use semantic versioning (cf. https://semver.org/) or OBO style date-based versioning (http://obofoundry.org/principles/fp-004-versioning.html).\nIf you need to add a larger comment in natural language, you should provide the info as an rdf:langString, i.e. with a language tag. We do not encourage this, since such statements can most likely be expressed in more granular fashion with formal statements.\nRecommended property: \nExample statement 1 (text/turtle):  owl:versionInfo \"2023-01-01\"^^xsd:string .\nExample statement 2 (text/turtle):  owl:versionInfo \"1.0.0\"^^xsd:string.\nExample statement 3:  owl:versionInfo \"Ontology version 1.0.0 of the subject classification in tabular format from Nov 2024.\"@en.\nNeed help? Learn more about SHACL: https://www.w3.org/TR/2017/REC-shacl-20170720/"""@en ;
         sh:description "This shape checks whether the ontology provides at most one textual version information as an xsd:string. It produces an info message if not."@en ;
         sh:name "Ontology version information"@en ;
diff --git a/OntoMetadataShape4Forms.ttl b/OntoMetadataShape4Forms.ttl
index f7e86dc..e2cc17f 100644
--- a/OntoMetadataShape4Forms.ttl
+++ b/OntoMetadataShape4Forms.ttl
@@ -33,7 +33,7 @@ ontometa4forms: rdf:type owl:Ontology ;
      "2025-01-01T00:00:00"^^xsd:dateTime;
     dcterms:abstract "OntoMeta4Forms provides SHACL shapes for ontology metadata. It is intended for use in form generator applications, e.g. . You may re-use (please refer back to our repo!) for your own services. Please note that adaptations might be necessary. If you have any remarks or questions get in touch with us at https://github.com/TIBHannover/terminology-metadata/issues"@en;
     dcterms:subject , ;
-    # dcterms:bibliographicCitation "Arndt, S., Ganske, A., Hauschke, C., Strömert, P., & Vogt, L. (2024). Terminology Metadata Recommendations by TIB. Zenodo. https://doi.org/10.5281/zenodo.11103070 (latest version)";
+    dcterms:bibliographicCitation "Arndt, S., Ganske, A., Hauschke, C., Strömert, P., & Vogt, L. (2024). Terminology Metadata Recommendations by TIB. Zenodo. https://doi.org/10.5281/zenodo.11103070 (latest version)";
     vann:preferredNamespacePrefix "ontometa4forms";
     dcterms:license ;
     doap:audience "Ontology engineers, ontology publishers, terminology service providers, terminology service curators"@en;
@@ -48,7 +48,8 @@ ontometa4forms: rdf:type owl:Ontology ;
     mod:hasFormalityLevel "RDF(S), OWL, SHACL"@en;
      ;
     mod:hasEquivalencesWith ;
-      , 
+      ,  ;
+    vann:example  
 .
 
 # Start of the Ontology Metadata Shape
@@ -390,7 +391,7 @@ ontometa4forms:OntologyMetadataShape a sh:NodeShape ;
 ## Application example
 ### status: developer and external review needed
     sh:property [
-        sh:path  ;
+        sh:path  ;
         sh:severity sh:Info ;
         #sh:minCount 1 ;
         sh:nodeKind sh:IRI ;
@@ -676,7 +677,7 @@ ontometa4forms:OntologyMetadataShape a sh:NodeShape ;
 
 ## Ontology logo/ depiction/ related visualizations
 ### status: developer and external review needed
-### needs to be split for forms (and validation?)
+### needs to be split for forms and validation? > logo should be its own datum, depictions and visualizations can go together
 
     sh:property [
         sh:path  ;
@@ -695,7 +696,7 @@ ontometa4forms:OntologyMetadataShape a sh:NodeShape ;
         sh:severity sh:Info ;
         sh:nodeKind sh:IRI ;
         sh:description "You can provide alternative identifiers of the ontology, e.g. a DOI, a Wikidata entry, or comparable identifiers."@en ;
-        sh:name "Related identifiers"@en ;
+        sh:name "Alternative identifiers of the ontology"@en ;
         sh:group ontometa4forms:IntrinsicGroup ;
     ];
 
diff --git a/OntoMetadataShape4TS.ttl b/OntoMetadataShape4TS.ttl
index 180f7f9..284b0e4 100644
--- a/OntoMetadataShape4TS.ttl
+++ b/OntoMetadataShape4TS.ttl
@@ -46,7 +46,8 @@ ontometa4ts: rdf:type owl:Ontology ;
       ;
      "RDF(S), OWL, SHACL"@en ;
     dcterms:bibliographicCitation "Arndt, S., Ganske, A., Hauschke, C., Strömert, P., & Vogt, L. (2024). Terminology Metadata Recommendations by TIB. Zenodo. https://doi.org/10.5281/zenodo.11103070 (latest version)";
-      , 
+      ,  ;
+     
 .
 
 # Start of the Ontology Metadata Shape
@@ -69,7 +70,6 @@ The ontology does not include its own title. Please provide it if known.
 Recommended property: http://purl.org/dc/terms/title
 
      
         """@en ;
-        # sh:message """The ontology does not include its own title. Please provide it if known.\nRecommended property: http://purl.org/dc/terms/title"""@en ;
         sh:name "Ontology title"@en ;
     ] ;
 
@@ -96,7 +96,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology title should be an rdf:langString, i.e. it should have a language tag.\nThere may be only one title per language.\nRecommended property: http://purl.org/dc/terms/title.\nExample statement (text/turtle): \"Some Ontology\"@en ."""@en ; sh:name "Ontology title - datatype"@en ; ] ; @@ -118,7 +117,6 @@ It must not contain hyphens or other special characters and should be written in Recommended property: http://purl.org/vocab/vann/preferredNamespacePrefix

    """@en ; - # sh:message """The ontology does not declare its preferred prefix. Please provide it if known.\nIt must not contain hyphens or other special characters and should be written in lowercase.\nRecommended property: http://purl.org/vocab/vann/preferredNamespacePrefix"""@en ; sh:name "Preferred ontology prefix/ acronym"@en ; ] ; @@ -141,7 +139,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should declare its preferred namespace prefix or acronym as an xsd:string.\nRecommended property: http://purl.org/vocab/vann/preferredNamespacePrefix\nExample statement (text/turtle): \"so\"^^xsd:string ."""@en ; sh:name "Preferred ontology prefix/ acronym - datatype"@en ; ] ; @@ -234,7 +231,6 @@ The ontology does not declare its own license. Please provide it, if known. Recommended property: http://purl.org/dc/terms/license

    """@en ; - # sh:message """The ontology does not declare its own license. Please provide it, if known.\nRecommended property: http://purl.org/dc/terms/license"""@en ; sh:name "Ontology license"@en ; ] ; @@ -306,7 +302,6 @@ Example statement (text/turtle): 
    <https://www.purl.org/SomeOntology> <http://purl.org/dc/terms/license> <http://creativecommons.org/licenses/by/4.0/> .

    """@en ; - # sh:message """The ontology license is not accepted at TIB Terminology Service since it is not an open license according to the Open Definition (https://opendefinition.org/licenses/).\nThe ontology must be provided with an open license in order to be added to TIB Terminology Service.\nThe license must be given as an IRI.\nThe following licenses are not accepted at TIB Terminology Service:\n - https://creativecommons.org/licenses/by-nc-nd/4.0/legalcode\n - https://creativecommons.org/licenses/by-nc-nd/4.0/legalcode\n - https://creativecommons.org/licenses/by-nc-nd/3.0/de/legalcode\n - https://creativecommons.org/licenses/by-nd/4.0/legalcode\n - https://creativecommons.org/licenses/by-nd/3.0/de/legalcode\nRecommended property: http://purl.org/dc/terms/license\nExample statement (text/turtle): ."""@en ; sh:name "Ontology license"@en ; ] ; @@ -340,7 +335,6 @@ https://ror.org/ Recommended property: http://purl.org/dc/terms/creator

    """@en ; - # sh:message """The ontology does not name its creators. Please provide them if known. This information is required for licenses that require attribution. Use ORCID, ROR or comparable identifiers for people and organisations if available.\nRecommended property: http://purl.org/dc/terms/creator"""@en ; sh:name "Ontology creator(s)"@en ; ] ; @@ -384,7 +378,6 @@ Example statement 2 (text/turtle):

    """@en ; - # sh:message """The ontology should provide its creators as IRIs, in particular persistent identifiers (PIDs) wherever possible, e.g. ORCiDs for persons and RORs for organisations.\nIf an ontology is developed by a larger group, it is recommended to give the organization or project identifier as the creator and list individual persons as contributors.\nRecommended property: http://purl.org/dc/terms/creator\nExample statement 1 (text/turtle): . rdf:type foaf:Person .\nPlain name strings could be provided in addition (for readability).\nExample statement 2 (text/turtle):\n .\n rdf:type foaf:Person ; \"Max\" ;\n \"Muster\" ."""@en ; sh:name "Ontology creator(s) - datatype"@en ; ] ; @@ -405,7 +398,6 @@ The ontology does not declare a versionIRI. Please provide it, if known. Recommended property: http://www.w3.org/2002/07/owl#versionIRI

    """@en ; - # sh:message """The ontology does not declare a versionIRI. Please provide it, if known.\nRecommended property: http://www.w3.org/2002/07/owl#versionIRI"""@en ; # optimized message for current TIB TS sh:name "Ontology version IRI"@en ; ] ; @@ -442,7 +434,6 @@ Example statement 3 (text/turtle):

    """@en ; - # sh:message """The ontology should state its versionIRI as an IRI. It should not be given as a string or literal.\nRecommended property: http://www.w3.org/2002/07/owl#versionIRI\nExample statement 1 (text/turtle): .\nExample statement 2 (text/turtle): .\nExample statement 3 (text/turtle): ."""@en ; sh:name "Ontology version IRI - datatype"@en ; ] ; @@ -464,7 +455,6 @@ Use the xsd:dateTime format to do so (e.g. 2024-12-12T11:18:44). Recommended property: http://purl.org/dc/terms/created

    """@en ; - # sh:message """The ontology does not declare its creation date. Please provide it, if known. Use the xsd:dateTime format to do so (e.g. 2024-12-12T11:18:44).\nRecommended property: http://purl.org/dc/terms/created"""@en ; # optimized message for current TIB TS sh:name "Ontology creation date"@en ; ] ; @@ -487,7 +477,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should provide its creation date in xsd:dateTime format.\nRecommended property: http://purl.org/dc/terms/created\nExample statement (text/turtle): dcterms:created \"2020-11-19T00:00:00\"^^xsd:dateTime ."""@en ; sh:name "Ontology creation date - datatype"@en ; ] ; @@ -509,7 +498,6 @@ The ontology abstract should not be longer than 500 characters. Recommended property: http://purl.org/dc/terms/abstract

    """@en ; - # sh:message """The ontology does not contain an abstract. Please provide it, if knwon. The ontology abstract should not be longer than 500 characters.\nRecommended property: http://purl.org/dc/terms/abstract"""@en ; # optimized message for current TIB TS sh:name "Ontology abstract"@en ; ] ; @@ -536,7 +524,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should provide its abstract as an rdf:langString.\nRecommended property: http://purl.org/dc/terms/abstract\nExample statement (text/turtle): dcterms:abstract \"SomeOntology defines a range of classes and properties which can be applied to do stuff in a particular domain.\"@en , \"SomeOntology definiert eine Reihe von Klassen und Properties, die in einer bestimmten Domäne verwendet werden können, um etwas damit zu tun.\"@de ."""@en ; sh:name "Ontology abstract - language"@en ; ] ; @@ -577,7 +564,6 @@ or add a reference to a related article using the property http://purl.org/dc/te

    """@en ; - # sh:message """The ontology should limit its abstract size to 500 characters maximum.\nThe TIB Terminology Service requires short ontology descriptions for a user-friendly ontology list.\nTo provide more information about the ontology, add an additional description (recommended property: http://purl.org/dc/terms/description) or add a reference to a related article (recommended property: http://purl.org/dc/terms/isReferencedBy)."""@en ; sh:name "Ontology abstract - length"@en ; ] ; @@ -597,7 +583,6 @@ The ontology does not contain the link to its issue tracker. Please provide it i Recommended property: http://usefulinc.com/ns/doap#bug-database

    """@en ; - # sh:message """The ontology does not contain the link to its issue tracker. Please provide it if available and known.\nRecommended property: http://usefulinc.com/ns/doap#bug-database"""@en ; # optimized message for current TIB TS sh:name "Ontology issue tracker"@en ; ] ; @@ -617,7 +602,6 @@ The ontology does not contain the link to its documentation. Please provide it, Recommended property: http://www.loc.gov/premis/rdf/v3/documentation

    """@en ; - # sh:message """The ontology does not contain the link to its documentation. Please provide it, if known.\nRecommended property: http://www.loc.gov/premis/rdf/v3/documentation"""@en ; sh:name "Ontology documentation"@en ; ] ; @@ -666,7 +650,6 @@ Example statement 2 (text/turtle):

    """@en ; - # sh:message """The ontology should list all its contributors.\nContributors should be referenced via PIDs, e.g. ORCiDs for persons and RORs for organisations.\nIf an ontology is developed by a larger group, it is recommended to give the organization or project identifier as the creator and list individual persons as contributors.\nRecommended property: \n\nExample statement 1 (text/turtle): . rdf:type foaf:Person .\nPlain name strings can be provided in addition (for readability).\nExample statement 2 (text/turtle):\n .\n rdf:type foaf:Person ; \"Max\" ;\n \"Muster\" ."""@en ; sh:name "Ontology contributor(s)"@en ; ] ; @@ -708,7 +691,6 @@ Example statement 2 (text/turtle):

    """@en ; - # sh:message """The ontology should provide its contributors as IRIs, in particular as persistent identifiers (PIDs) wherever possible, e.g. ORCiDs for persons and RORs for organisations.\nIf an ontology is developed by a larger group, it is recommended to give the organization or project identifier as the creator and list individual persons as contributors.\nRecommended property: \nExample statement 1 (text/turtle): . rdf:type foaf:Person .\n\nPlain name strings could be provided in addition (for readability).\nExample statement 2 (text/turtle):\n .\n rdf:type foaf:Person ; \"Max\" ;\n \"Muster\" ."""@en ; sh:name "Ontology contributor(s) - datatype"@en ; ] ; @@ -746,7 +728,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """If applicable, the ontology should reference any institutions funding the work on the ontology.\nThe funding institution(s) should be referenced by PIDs, e.g. RORs (https://ror.org/) or Crossref Funder Registry IDs (https://www.crossref.org/services/funder-registry/)).\nRecommended property: \nExample statement (text/turtle): ."""@en ; sh:name "Ontology funder"@en ; ] ; @@ -782,7 +763,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should reference any institutions funding its development via IRI.\nThe funding institution should be referenced by PIDs, e.g. RORs (https://ror.org/) or Crossref Funder Registry IDs (https://www.crossref.org/services/funder-registry/)).\nRecommended property: \nExample statement (text/turtle): ."""@en ; sh:name "Ontology funder"@en ; ] ; @@ -812,7 +792,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """If applicable, the ontology should reference the grant which funds its development.\nThe grant should be referenced by PID, e.g. Crossref Grant ID (https://www.crossref.org/documentation/research-nexus/grants/)).\nRecommended property: \nExample statement (text/turtle): ."""@en ; sh:name "Ontology funding (grant)"@en ; ] ; @@ -838,7 +817,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should reference any grants funding its development via IRI.\nThe funding grant should be referenced by PID, e.g. Crossref Grant IDs (https://www.crossref.org/documentation/research-nexus/grants/)).\nRecommended property: \nExample statement (text/turtle): ."""@en ; sh:name "Ontology funding (grant)"@en ; ] ; @@ -868,7 +846,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should describe its intended audience.\nThe audience description should be a short, language-tagged text.\nRecommended property: \nExample statement (text/turtle): doap:audience \"This ontology is intended for researchers in derivational morphology, a branch of linguistics.\"@en ."""@en ; skos:editorialNote "see also open comment at G-Doc: https://docs.google.com/document/d/1FRmCQ7eD6PcqSQgPbqCGjki3t39ROoYozsehCPX9E0Q/edit?disco=AAAAwke7GNs" ; sh:name "Ontology audience description"@en ; ] ; @@ -892,7 +869,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should provide its audience description as an rdf:langString.\n\nRecommended property: \n\nExample statement (text/turtle): <https://www.purl.org/SomeOntology> doap:audience \"This ontology is intended for researchers in derivational morphology, a branch of linguistics.\"@en . """@en ; sh:name "Ontology audience description - language"@en ; ] ; @@ -903,7 +879,6 @@ Example statement (text/turtle): sh:path dcterms:subject ; sh:severity sh:Info ; sh:minCount 1 ; - # sh:message """The ontology should provide some keywords to describe its subject(s).\nIt is recommended to use identifiers of controlled vocabularies or ontologies to do so.\nYou can search for fitting terms on TIB Terminology Service (https://terminology.tib.eu).\nRecommended property: http://purl.org/dc/terms/subject\nExample statement (text/turtle): dcterms:subject , , , ."""@en ; sh:message """

    The ontology should provide ontology subjects with IRIs from controlled vocabularies or ontologies. Subjects should not be given as free text. @@ -951,7 +926,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should provide ontology subjects with IRIs from controlled vocabularies or ontologies. Subjects should not be given as free text.\nYou can search for fitting terms on TIB Terminology Service (https://terminology.tib.eu).\nRecommended property: \nExample statement (text/turtle): dcterms:subject , , , ."""@en ; sh:name "Ontology subject(s) - datatype"@en ; ] ; @@ -984,7 +958,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should provide information about the ontology annotation language(s) (e.g. for term labels, term definitions, etc.).\nIt should only claim that the ontology uses an annotation language, if all ontology elements or an extensive part of the ontology is annotaed in that languge.\nRecommended controlled vocabulary: \nRecommended property: \nExample statement (text/turtle): dcterms:language , ."""@en ; sh:name "Ontology annotation language(s)"@en ; ] ; @@ -1011,7 +984,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should specify the ontology annotation language(s) via IRIs.\nRecommended controlled vocabulary: \nRecommended property: \nExample statement (text/turtle): dcterms:language , ."""@en ; sh:name "Ontology annotation language(s) - datatype"@en ; ] ; @@ -1030,7 +1002,6 @@ Example identifier: http://id.loc.gov/vocabulary/iso639-2/tgl Recommended property: https://schema.org/inLanguage

    """@en ; - # sh:message """The ontology should provide ontology annotation language values that match the pattern for language identifiers from 'ISO 639-2: Codes for the Representation of Names of Languages - Part 2: Alpha-3 Code for the Names of Languages' (cf. https://id.loc.gov/vocabulary/iso639-2.html).\nExample identifier: """@en ; sh:name "Ontology annotation language(s) - pattern"@en ; ] ; @@ -1061,7 +1032,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should state which logical framework it applies.\nThe information can be given as a text, referring to the Semantic Web Standard (e.g. 'OWL 2') and possibly the OWL profile (e.g. 'OWL 2 EL profile').\nRecommended property: \nExample statement (text/turtle): mod:hasFormalityLevel \"OWL version 2, EL profile\"@en ."""@en ; sh:name "Applied logical framework description"@en ; ] ; @@ -1084,7 +1054,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should provide the description its logical framework as an rdf:langString.\nRecommended property: \nExample statement (text/turtle): mod:hasFormalityLevel \"OWL version 2, EL profile\"@en ."""@en ; sh:name "Applied logical framework description - language"@en ; ] ; @@ -1149,7 +1118,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should state its serialization/ file format.\nThe value should be provided as an IRI.\nWe recommend to provide the information about the media type/ file format of your ontology as one of the values from the Media Types list of the Internet Assigned Number Authority (IANA) (cf. https://www.iana.org/assignments/media-types/media-types.xhtml) or from the W3C resource "Unique URIs for File Formats" :\n\nIn order to publish your ontology on the TIB Terminology Service, you must provide the ontology in one of the following formats:\n - resp. \n - resp. \n - OBO format (cf. http://purl.obolibrary.org/obo/oboformat/spec.html)\nCurrently, there is no registered media type for obo format.\nRecommended property: \nExample statement (text/turtle): ."""@en ; sh:name "Ontology serialization/ file format"@en ; ] ; @@ -1211,7 +1179,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should state its serialization/ file format.\nThe value should be provided as an IRI.\nWe recommend to provide the information about the media type/ file format of your ontology as one of the values from the Media Types list of the Internet Assigned Number Authority (IANA) (cf. https://www.iana.org/assignments/media-types/media-types.xhtml) or from the W3C resource \"Unique URIs for File Formats\" :\n\nIn order to publish your ontology on the TIB Terminology Service, you must provide the ontology in one of the following formats:\n - resp. \n - resp. \n - OBO format (cf. http://purl.obolibrary.org/obo/oboformat/spec.html)\nCurrently, there is no registered media type for obo format.\nRecommended property: \nExample statement (text/turtle): ."""@en ; sh:name "Ontology serialization/ file format - datatype"@en ; ] ; @@ -1308,7 +1275,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should state its serialization/ file format.\nThe value should be provided as an IRI.\nWe recommend to provide the information about the media type/ file format of your ontology as one of the values from the Media Types list of the Internet Assigned Number Authority (IANA) (cf. https://www.iana.org/assignments/media-types/media-types.xhtml) or from the W3C resource \"Unique URIs for File Formats\" :\n\nIn order to publish your ontology on the TIB Terminology Service, you must provide the ontology in one of the following formats:\n - resp. \n - resp. \n - OBO format (cf. http://purl.obolibrary.org/obo/oboformat/spec.html)\nCurrently, there is no registered media type for obo format.\nRecommended property: \nExample statement (text/turtle): [sh:alternativePath ( ) ]; ."""@en ; sh:name "Ontology serialization/ file format - controlled vocabulary value"@en ; ] ; @@ -1342,7 +1308,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should declare its current maintenance status. You could use an English label to do so. We recommend using one of 'active', 'inactive', 'orphaned' or 'obsolete' (cf. https://obofoundry.org/docs/OntologyStatus.html).\nThe value you use should be language-tagged.\nRecommended property: \nExample statement (text/turtle): bibo:status \"inactive\"@en ."""@en ; sh:name "Ontology status"@en ; ] ; @@ -1371,7 +1336,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should provide the link to its code repository.\nThe ontology should be on a code repository and the ontology should contain the repository's IRI.\nRecommended property: \nExample statement (text/turtle): doap:repository ."""@en ; sh:name "Ontology code repository"@en ; ] ; @@ -1394,7 +1358,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should provide the link to its code repository as an IRI.\nRecommended property: \nExample statement (text/turtle): doap:repository ."""@en ; sh:name "Ontology code repository - datatype"@en ; ] ; @@ -1422,14 +1385,13 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should provide IRIs to its available alternative serializations or distributions.\nRecommended property: \nExample statement (text/turtle): , , ."""@en ; sh:name "Ontology distributions/ products"@en ; ] ; ## Application example ### status: developer and external review needed sh:property [ - sh:path ; + sh:path ; sh:severity sh:Info ; sh:minCount 1 ; sh:nodeKind sh:IRI ; @@ -1441,17 +1403,16 @@ The ontology should provide a link to an example demonstrating its application. Ideally, the ontology provides a PID to e.g. a publication describing applications of the ontology, or directly to an application or online service that uses the ontology.

    -Recommended property: https://vocab.org/vann/example +Recommended property: http://purl.org/vocab/vann/example

    Example statement (text/turtle):

    -

    <http://www.w3.org/ns/dcat> <https://vocab.org/vann/example> <https://www.w3.org/TR/vocab-dcat-2/#collection-of-examples> .
+
    <http://www.w3.org/ns/dcat> <http://purl.org/vocab/vann/example> <https://www.w3.org/TR/vocab-dcat-2/#collection-of-examples> .
 
    
 
    
 """@en ;
-        # sh:message """The ontology should provide a link to an example demonstrating its application.\nIdeally, the ontology provides a PID to e.g. a publication describing applications of the ontology, or directly to an application or online service that uses the ontology.\nRecommended property: \nExample statement (text/turtle):  vann:example  ."""@en ;
         sh:name "Application example"@en ;
     ] ;
 
@@ -1483,7 +1444,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should provide references to its related resources via IRI.\nRelated recources could for example be publications introducing, discussing, evaluating or describing the ontology, recources containing alignments of your ontology to other ontologies, or any other resources that you would like to reference in your ontology.\nThe reference should be provided via PID, for example a DOI, if available.\nRecommended property: \nExample statement (text/turtle): dcterms:references ."""@en ; sh:name "Related resource(s)"@en ; ] ; @@ -1512,7 +1472,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should provide information about how it should be cited.\nThe information should be provided as an rdf:langString.\nRecommended property: \nExample statement (text/turtle): dcterms:bibliographicCitation \"Last name, first name; last name, first name et al. (YYYY): Title. URL: https://w3id.org/SomeOntology/1.1.6\"@en ."""@en ; sh:name "Citation suggestion"@en ; ] ; @@ -1541,7 +1500,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should specify whether and from which other ontologies it has been derived.\nThe reference should be made by an owl:versionIRI of the ontology from which the current ontology has been derived.\nRecommended property: \nExample statement (text/turtle): pav:derivedFrom ."""@en ; sh:name "Ontology sources (derived from)"@en ; ]; @@ -1574,7 +1532,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should explicitly declare its root classes.\nThis information can be used for tree-like visualizations of the class hierarchy in technical services, e.g. TIB Terminology Service.\nThe respective classes (if any) need to be provided via their identifier.\nRecommended property: \nExample statement (text/turtle): ."""@en ; sh:name "Ontology root classes"@en ; ] ; @@ -1606,7 +1563,6 @@ Example statetement (text/turtle):

    """@en ; - # sh:message """The ontology should provide its description as an rdf:langString.\nRecommended property: \nExample statetement (text/turtle): schema:description \"Free text describing the ontology and how it came to be. Basically everything you might want to add and which does not fit into the abstract.\"@en ."""@en ; sh:name "Ontology description - language"@en ; ] ; @@ -1631,7 +1587,6 @@ Example statements (text/turtle):

    """@en ; - # sh:message """The ontology should only provide one ontology description per language.\nRecommended property: \nExample statements (text/turtle): schema:description \"Free text describing the ontology and how it came to be. Basically everything you might want to add and which does not fit into the abstract.\"@en, \"Freitext, der die Ontologie und ihre Genese beschreibt. Hier können umfangreiche Hintergrundinformationen zur Ontologie gegeben werden, die über ein kurzes Abstract hinausgehen.\"@de ."""@en ; sh:name "Ontology description - unique language"@en ; ] ; @@ -1658,7 +1613,6 @@ Example statement (text/turtle):

    """@en; - # sh:message """The ontology should provide its alternative title(s) as an rdf:langString.\nRecommended property: \nExample statement (text/turtle): dcterms:alternative \"My Ontology\"@en ."""@en; sh:name "Alternative ontology title - language"@en; ] ; @@ -1684,7 +1638,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should provide its alternative prefix as an xsd:string.\nRecommended property: \nExample statement (text/turtle): idot:alternatePrefix \"mo\"^^xsd:string ."""@en ; sh:name "Alternative ontology prefix/ acronym - datatype"@en ; ] ; @@ -1716,7 +1669,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should provide its prior version as an IRI.\nIdeally, a resolving ontology versionIRI should be used.\nRecommended property: \nExample statement (text/turtle): owl:priorVersion ."""@en ; sh:name "Prior ontology version"@en ; ] ; @@ -1745,7 +1697,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should provide its related version as an IRI.\nIdeally, a resolving ontology versionIRI should be used.\nRecommended property: \nExample statement (text/turtle): dcterms:isVersionOf ."""@en ; sh:name "Related ontology version"@en ; ] ; @@ -1774,7 +1725,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should provide compatible versions of itself as IRIs.\nIdeally, a resolving ontology versionIRI should be used.\nRecommended property: \nExample statement (text/turtle): owl:backwardCompatibleWith ."""@en ; sh:name "Compatible ontology version"@en ; ] ; @@ -1803,7 +1753,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should provide incompatible versions of itself as IRIs.\nIdeally, a resolving ontology versionIRI should be used.\nRecommended property: \nExample statement (text/turtle): owl:incompatibleWith ."""@en ; sh:name "Incompatible ontology version"@en ; ] ; @@ -1836,7 +1785,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should declare at most one KOS type for itself. Use an identifier from the NKOS type vocabulary (https://nkos.dublincore.org/nkostype/nkostype.rdf).\nRecommended property: \nExample statement (text/turtle): dcterms:type ."""@en ; sh:name "KOS type"@en ; ] ; @@ -1879,7 +1827,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The KOS type identifier should be provided as an IRI. The IRI should be one of the KOS types defined by the NKOS type vocabulary (https://nkos.dublincore.org/nkostype/nkostype.rdf).\nRecommended property: \nExample statement (text/turtle): dcterms:type ."""@en ; sh:name "KOS type"@en ; ] ; @@ -1905,7 +1852,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should declare any example identifiers for the ontology as an IRI.\nRecommended property: \nExample statement (text/turtle): idot:exampleIdentifier ."""@en ; sh:name "Example ontology identifier"@en ; ] ; @@ -1932,7 +1878,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should provide its identifier pattern as an xsd:string.\nRecommended property: \nExample statement (text/turtle): idot:identifierPattern \"^\\d{4}-[A-Z]{2}$\"^^xsd:string ."""@en ; sh:name "Ontology identifier pattern"@en ; ] ; @@ -1960,7 +1905,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should provide its homepage as an IRI.\nRecommended property: \nExample statement (text/turtle): foaf:homepage ."""@en ; sh:name "Ontology homepage"@en ; ] ; @@ -1998,7 +1942,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should specify its publisher via ROR, ISNI or GND identifier.\nThe value you provide should be given as an IRI and match the identifier patterns.\nIf you use valid ROR, ISNI or GND identifiers, this should be the case.\nRecommended property: \nExample statement (text/turtle): dcterms:publisher ."""@en ; sh:name "Ontology publisher"@en ; ] ; @@ -2024,7 +1967,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """Any comments about the ontology should be given as rdf:langStrings.\nRecommended property: \nExample statement (text/turtle): rdfs:comment \"SomeOntology does not actually exist.\"@en ."""@en ; sh:name "Ontology comments"@en ; ] ; @@ -2051,7 +1993,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should provide its example classes as IRIs.\nRecommended property: \nExample statement (text/turtle): void:exampleResource ."""@en ; sh:name "Example ontology class - data type"@en ; ] ; @@ -2079,12 +2020,12 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should provide its mailing list as an IRI.\nRecommended property: \nExample statement (text/turtle): doap:mailing-list ."""@en ; sh:name "Ontology mailing list"@en ; ]; ## Ontology logo/ depiction/ related visualizations ### status: developer and external review needed +### needs to be split for forms and validation? > logo should be its own datum, depictions and visualizations can go together sh:property [ sh:path [sh:alternativePath ( )] ; @@ -2105,7 +2046,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should provide links to related depictions as IRIs.\nRecommended property: \nExample statement (text/turtle): foaf:logo ."""@en ; sh:name "Ontology logo/ depiction/ related visualizations"@en ; ]; @@ -2135,8 +2075,7 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should provide its identifiers as IRIs.\nThe identifier used as the base uri of the ontology should be provided with .\nRecommended property: \nExample statement (text/turtle): dcterms:identifier ."""@en ; - sh:name "Related identifiers"@en ; + sh:name "Alternative identifiers of the ontology"@en ; ]; ## Development environment @@ -2167,7 +2106,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should provide information about other ontologies it is aligned to as IRIs.\nRecommended property: \nExample statement (text/turtle): mod:hasEquivalencesWith ."""@en ; sh:name "Aligned resources"@en ; ]; @@ -2203,7 +2141,6 @@ Example statement 2 (text/turtle):

    """@en ; # inconsistent with forms shape - # sh:message """The ontology should provide the link to its competency questions as an IRI or provide the questions directly as an rdf:langString.\nRecommended property: \nExample statement 1 (text/turtle): \"Who developed an ontology?\"@en .\nExample statement 2 (text/turtle): ."""@en ; # inconsistent with forms shape sh:name "Competency questions"@en ; ]; @@ -2232,7 +2169,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should provide at most one preferred namespace URI for itself.\nRecommended property: \nExample statement (text/turtle): ."""@en ; sh:name "Preferred ontology namespace"@en ; ] ; @@ -2255,7 +2191,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should provide its preferred namespace URI as an IRI.\nRecommended property: \nExample statement (text/turtle): ."""@en ; sh:name "Preferred ontology namespace - datatype"@en ; ] ; @@ -2288,7 +2223,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should provide at most one issue date that conforms to xsd:dateTime.\nRecommended property: \nExample statement (text/turtle): \"2023-11-21T00:00:00\"^^xsd:dateTime ."""@en ; sh:name "Ontology issue date - datatype"@en ; ] ; @@ -2315,7 +2249,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should provide at most one ontology modification date in xsd:dateTime format (ideally the latest).\nRecommended property: \nExample statement (text/turtle): dcterms:modified \"2020-11-19T00:00:00\"^^xsd:dateTime."""@en ; sh:name "Ontology modification date"@en ; ] ; @@ -2326,7 +2259,6 @@ Example statement (text/turtle): sh:path [sh:alternativePath (owl:versionInfo pav:version)]; sh:severity sh:Info ; sh:xone ( [sh:datatype xsd:string ;] [sh:datatype rdf:langString ;] ); - # sh:datatype xsd:string ; sh:message """

    The ontology should provide textual information about its version as an xsd:string. @@ -2355,14 +2287,13 @@ Example statement 2 (text/turtle):

    -Example statement 3: +Example statement 3 (text/turtle): 

    <https://www.purl.org/SomeOntology> <http://www.w3.org/2002/07/owl#versionInfo> "Ontology version 1.0.0 of the subject classification in tabular format from Nov 2024."@en.

    """@en ; - # sh:message """The ontology should provide textual information about its version as an xsd:string.\nIt is recommended to use semantic versioning (cf. https://semver.org/) or OBO style date-based versioning (http://obofoundry.org/principles/fp-004-versioning.html).\nIf you need to add a larger comment in natural language, you should provide the info as an rdf:langString, i.e. with a language tag. We do not encourage this, since such statements can most likely be expressed in more granular fashion with formal statements.\nRecommended property: \nExample statement 1 (text/turtle): owl:versionInfo \"2023-01-01\"^^xsd:string .\nExample statement 2 (text/turtle): owl:versionInfo \"1.0.0\"^^xsd:string.\nExample statement 3: owl:versionInfo \"Ontology version 1.0.0 of the subject classification in tabular format from Nov 2024.\"@en."""@en ; sh:name "Ontology version information"@en ; ] ; @@ -2408,7 +2339,6 @@ Example statement 2 (text/turtle):

    """@en ; - # sh:message """The ontology should provide at most one textual information about the ontology version.\nThe value should be provided as an xsd:string.\nIt is recommended to use semantic versioning (cf. https://semver.org/) or OBO style date-based versioning (http://obofoundry.org/principles/fp-004-versioning.html).\nRecommended property: \nExample statement 1 (text/turtle): owl:versionInfo \"2023-01-01\"^^xsd:string .\nExample statement 2 (text/turtle): owl:versionInfo \"1.0.0\"^^xsd:string."""@en ; sh:name "Ontology version information"@en ; ] ; @@ -2435,7 +2365,6 @@ Example statement (text/turtle):

    """@en ; - # sh:message """The ontology should provide its version notes (e.g. notes on updates as compared to the previous version of the ontology) as an rdf:langString.\nRecommended property: \nExample statement (text/turtle): adms:versionNotes \"Changes from 2000-01-12: add annotation properties: familyName [...]\"@en ."""@en ; sh:name "Ontology version notes"@en ; ] ; diff --git a/TabularOverview.tsv b/TabularOverview.tsv index b84c34c..2ee0fa1 100644 --- a/TabularOverview.tsv +++ b/TabularOverview.tsv @@ -19,7 +19,7 @@ order number section metadatum Preferred property Mandatory Recommended Optional 18 4.9 Status x 0...1 true false false true true true true true true true true false true 19 4.10 Code repository x 0...1 false true false true false false true false false true false true false 20 4.11 Distributions/ products x 0…* true true false false false false true false true false true false false -21 4.12 Application example x 0…* false true false true false false true false false false false false false +21 4.12 Application example x 0…* false true false true false false true false false false false false false 22 4.13 Related resource(s) x 0…* true true false false true true true false true true true true false 23 4.14 Citation suggestion x 0…* false true false false true true true true false false true false false 24 4.15 Ontology sources (derived from) x 0…* true true false true true true true true true false true false false