Bill Duncan

Since ENVO now satisfies with the DL profile, I am closing this issue. The addition of the `has component` relation will be tracked in issue https://github.com/EnvironmentOntology/envo/issues/1101.

Should we add the simple has participant relation to RO? Suggestions for what to call the relation: - has partaker - has simple participant - has contributor

@cmungall `has direct participant` sounds good too :) Another possible option is to annotate the axioms. For instance suppose, we add annotation properties (I'm not tied to these names): -...

Or perhaps use a single `cardinality` annotation property and annotate the axiom like this: 

I included the name of the property in order to account for cases in the axioms have more than one property. E.g.: ``` 'has part' max 2 Foo and 'has...

@cmungall sorry ... I'm not quite following your point :) Suppose we a class has a subclass axiom like: ``` ('part of' some Foo) and ('has input' some Bar) ```...

@matentzn @cmungall I just ran the following on `envo-edit.owl`: ``` robot validate-profile --profile DL --input envo-edit.owl > dl-profile-errors.txt ``` See attached file for errors. I posted in Slack about doing...

@matentzn Sorry, I'm not following. `envo-edit.owl` is in OFN syntax. For kicks, I made a new copy called `envo-edit.ofn`, and ran: ``` robot validate-profile --profile DL --input envo-edit.ofn > dl-ofn-errors.txt...

@matentzn To be clear: there isn't a make command to convert `envo-edit.owl` to OFN b/c it is already in that form. I tired using `robot` to convert the `envo-edit.owl` file...

I think this is good information to put in a comment. We should also consider including in the information in the definition (which is currently has the annotation property 'has_narrrow_synonym').