This is regarding to the psi-validator-2.0.0 (general schema validator).
Case-insensitive CV-rules(terms) would be very helpful, especially if we really think about object rules and custom ontology access implementations.
For example, MI:0444 (database citation) children can be used to validate database names in e.g. BioPAX Xrefs. However, look, a valid term
"chebi" is there often used as "chEBI", or "pubmed" - "PubMed", etc. Furthermore, one would like to validate e.g. protein ID (not ontology) from the
"chebi" database using the MIRIAM web service! Although there's no problem there with using "chEBI"/"chebi" as the database name, but it is not ok
about "gene ontology", which is often used as "Gene Ontology", which is simply "go" in the MIRIAM... but this is rather about ontology mapping. :))
For now, I would suggest (at least) adding a new attribute to the CvMappingRules.xsd (an the corresponding modifications to other classes) to allow the following:
<CvTerm isTermCaseSensitive="false" />
schema patch