I'm investigating some problems with the generated OWL for the CCDH model: cancerDHC/ccdhmodel#64

I started by following the linkml tutorial, and I think I see some of the issues in that simple example as well:

• Create personinfo.yaml as in https://github.com/linkml/linkml/blob/main/examples/tutorial/tutorial01/personinfo.yaml
• Run gen-rdf personinfo.yaml >personinfo.ttl. Observe the phone slot has IRI <https://w3id.org/linkml/examples/personinfo/person__phone>.
• Run gen-owl personinfo.yaml >personinfo.owl.ttl. Some problems:
  • The phone slot has IRI using the main linkml namespace: <https://w3id.org/linkml/phone>
  • The phone slot is not declared as any particular type of OWL property, e.g., owl:ObjectProperty
  • The phone slot is used in OWL restrictions without having been declared:

    <https://w3id.org/linkml/examples/personinfo/Person> a owl:Class,
       linkml:ClassDefinition ;
       rdfs:subClassOf [ a owl:Restriction ;
           owl:maxQualifiedCardinality 1 ;
           owl:onClass linkml:String ;
           owl:onProperty linkml:phone ]
    

All of this seems to be the cause of parsing failures found by the Java OWL API.