This issue was raised by Huda Khan at the Development call 7/13/17
Some ontologies (rdf and rdfs specifically) contain rdfProperty. rdfProperty is not an owl:ObjectProperty nor an owl:DataProperty. The application does not know what to do.
We have been using a workaround – we add owl:ObjectProperty and owl:DataProperty assertions to ontologies as necessary to "make them work" in VIVO.
This creates at least three problems: 1) We are adding information to the ontology that the ontology did not provide. We might be mistake; 2) Our export of the ontology includes these assertions, so we contaminate the ontology in round tripping it through VIVO; 3) We can not automatically add and use ontologies. We must perform a manual step to add these owl assertions.
Can we use faux properties to add the required information? This would keep the added information out of application logic and out the ontology
Can we make the application smarter to handle rdfProperty in some reasonable way? This would avoid having to do manual work and would keep additional assertions out of the ontology.
Much to consider here