Mark Jensen

@eliasweatherfield Use of 'some' is fairly standard in many ontology definitional patterns, as it implies: "at least one, but does not preclude all". This has roots in logic, e.g, the...

@neilotte Currently, we perform a small set of validations as part of a release. Examples of logical ones are: consistency and to ensure a valid OWL DL profile. For metadata,...

@swartik >Even better would be to (automatically) test completeness each time a commit is pushed to github. Note above, these tests are run automatically as part of a release. It...

> I think all classes and properties should have a textual definition, without exception. I agree. Especially for a MLO standard. So, the question becomes: Do these relations seem reasonable...

@swartik Thanks for catching this. What page informaiton are you referring to? Are you downloading them and then opening in a text editor?

I agree that the axiom is implied by the definition and should be added.

I'm not clear about what more needs to be said at the level of the term in the ontology, other than what is currently mentioned about designation happening within a...

@alanruttenberg > the quality type qt (e.g. a temperature of 40 degrees) In CCO we handle this differently. We assert an instance of a Temperature Quality and have an ICE...

The Stasis and Change heirarchies have been refactored and is available on the `stasis-change` branch. Discussed [here](https://github.com/CommonCoreOntology/CommonCoreOntologies/wiki/Proposed-revisions-to-Stasis-and-Change-Hierarchies)

Ideally, when a new version of the ontology is uploaded to the repo, any issues which are addressed with fixes or additions will be noted in comments for the commit....