...
Any reference to a URI in any context other than as the object of an annotation property must have a type triple for that URI. https://github.com/edmcouncil/fibo/blob/master/etc/testing/hygiene/testHygiene1testHygiene0001.sqsparql
Crossing domains / ranges
If one property is a sub of another, then the domains (respectively ranges) should not be subClasses in the opposite direction. https://github.com/edmcouncil/fibo/blob/master/etc/testing/hygiene/testHygiene2.sqtestHygiene0002sparql
https://github.com/edmcouncil/fibo/blob/master/etc/testing/hygiene/testHygiene3testHygiene0003.sqsparql
Labels and Definitions
Every Class and Property defined in FIBO must have an rdfs:label and a skos:definition https://github.com/edmcouncil/fibo/blob/master/etc/testing/hygiene/testHygiene4testHygiene0004.sqsparql
Ontology Metadata
Every Ontology defined in FIBO must have a rdfs:label, sm:copyright, dct:license, dct:abstract https://github.com/edmcouncil/fibo/blob/master/etc/testing/hygiene/testHygiene0005.sparql
String printability
Text should not use special characters https://github.com/edmcouncil/fibo/blob/master/etc/testing/hygiene/testHygiene0114.sparql
References to owl:Thing
We should not make explicit references to owl:Thing https://github.com/edmcouncil/fibo/blob/master/etc/testing/hygiene/testHygiene0268.sparql
Unique Labels
Labels should be unique across FIBO for classes and properties. https://github.com/edmcouncil/fibo/blob/master/etc/testing/hygiene/testHygiene5.sq testHygiene1067.sparql
Multiple Inverses
Object properties shouldn't have more than one inverse. https://github.com/edmcouncil/fibo/blob/master/etc/testing/hygiene/testHygiene1078.sparql
Annotation vocabulary
rdfs:comment shouldn't be used for FIBO annotation.https://github.com/edmcouncil/fibo/blob/master/etc/testing/hygiene/testHygiene1079.sparql
Equivalent Named Classes
Equivalent classes may indicate polysemy spread accross multiple classes https://github.com/edmcouncil/fibo/blob/master/etc/testing/hygiene/testHygiene1103.sparql
Disjunctive definitions
Definitions should not contain the "or" connective. https://github.com/edmcouncil/fibo/blob/master/etc/testing/hygiene/testHygiene1127.sparql
Proposed Hygiene tests:
Definition FormatThe definition is made up of one or more full sentences, beginning with an upper case letter and ending with a period.
NO, NO, NO - see https://wiki.edmcouncil.org/display/FLT/Policy+for+Naming+Conventions - definitions should be partial sentences, no capitals, no period at the end - something that can be reused in the place of the concept in a sentence; the format proposed is at the opposite end of the spectrum from this. We have said that we would conform to the recommendations of ISO 704, which is what's specified on the naming conventions page.
No property may have more than one inverse
...