Typo in rdfs:comment for classes GainOfDisposition and GainOfFunction about commoncoreontologies

[mark-jensen]

@swartik Thanks! Will be fixed asap.

Curious, are you using BFO2020 and the all/some properties? If so, how are they working out for you? Any problems with translating btw them and RO/ERO?

[swartik]

@mark-jensen Yes, we are using BFO2020 and its properties. Fortunately for us there was no legacy work to migrate: we based all our work on BFO2020. So we haven't had any translation problems. As I noted in #156, I was surprised to discover that some RO properties had no analogy in BFO2020, but their lack only resulted in using higher-level properties: using bearer of rather than has role. I imagine we will start creating domain ontology-specific properties that reflect the roles we model. So far this has not been important.

In our rush to deliver a product, we are using "some" properties rather than "all" properties unless we are very, very certain a relationship will always hold. We are still prototyping, and are sending graph patterns to our developer, who figures out how to turn data into those patterns. As we work through examples, we may discover a need for an "all" property. At this stage, switching properties won't be a problem: we aren't accumulating data in triple stores yet. And we have not found a need for rigid classes, per @neilotte's comment.

Really, the main problem using the new properties is their longer labels. The diagrams I draw for documentation are larger than in the past. Good thing we're not restricted to 8 1/2 x 11 paper any more.