Edits to acornOntology.ttl and turbo_valid_graph_specification.ttl for the sake of post_icbo_synthea_omop_cnp_transformation_instructions.ttl

[turbomam]

In the spirit of #67

Sorry for lumping several things together here.

Requests

• [x] MultiObjectDescribers aren't defined in acornOntology.ttl anymore, but they are still mentioned in Drivetrain error messages.
• [ ] Drivetrain errors of the same type should all be reported at once
  • for example, https://github.com/PennTURBO/Drivetrain/HealthcareEncounterRegDen is not present as an input and has a range list size that is not 1

Incomplete/potentially conflictual?

See MAM 20191120 comments in post_icbo_synthea_omop_cnp_transformation_instructions.ttl and turbo_valid_graph_specification.ttl

• The OMOP condition_occurrence_id... variable will be an integer, not a string. Didn't we talk about asserting a general type in the valid graph specification and a more specific type in the transformation instructions?
  • I don't think I know what to do with The object of connection https://github.com/PennTURBO/Drivetrain/DiagKeySymbHasRepresentation is not a literal, but the connection is a datatype connection.
• do you remember why drivetrain:hasRequiredInput drivetrain:MulScoMul is commented out? Did I do that, or you? I feel like we discussed something like that in the past but can't remember any more than that.
• I thought I replaced hard-coded TURBO column terms in the valid graph specification with drivetrain:ClassResourceLists, but I still see the hard-coded values, just commented out, as in drivetrain:RxAboutnessAxiomDbXrefPartOfColumn. If you have any ideas for finishing this as a bulk operation, please let me know.

Hopefully these are harmless:

• I tidied up TBC-style # baseURI and @prefix :
• I added ontology version placeholders
  • required adding some type assertions to the end of acornOntology.ttl

[turbomam]

I'm thinking now that I commented drivetrain:hasRequiredInput drivetrain:MulScoMul because it caused a performance degradation.

[turbomam]

And the replacement of hard-coded TURBO column terms with drivetrain:ClassResourceList really was complete. The issue I posted about that was just a manic oversight.