Related to #1810 unresolvable IRIs

[ghost]

Related to #1810 unresolvable IRIs
assigned numeric IDs to native CL object properties

[ghost]

QC appears to fail because two of the three renamed entities have an 'expand expression to' annotation, which is not permitted for terms with CL IRIs per ../sparql/illegal-annotation-property-violation.sparql:

FAIL Rule ../sparql/illegal-annotation-property-violation.sparql: 2 violation(s)
[32](https:/obophenotype/cell-ontology/actions/runs/4241973672/jobs/7372881034#step:4:33)
term,annotation
[33](https:/obophenotype/cell-ontology/actions/runs/4241973672/jobs/7372881034#step:4:34)
http://purl.obolibrary.org/obo/CL_4030046,http://purl.obolibrary.org/obo/IAO_0000424
[34](https:/obophenotype/cell-ontology/actions/runs/4241973672/jobs/7372881034#step:4:35)
http://purl.obolibrary.org/obo/CL_4030045,http://purl.obolibrary.org/obo/IAO_0000424

[ghost]

Thanks for reviewing, @balhoff.
@matentzn, can you comment on the QC failure noted above? Is there a reason why that annotation is blocked for CL terms?

[matentzn]

This failure gives me great peace of mind. All you need to do is edit the

../sparql/illegal-annotation-property-violation.sparql file and add the new property to the list of allowed properties. You can do this on this branch here, and assign me as a reviewer

[ghost]

Thanks, @matentzn. SPARQL file updated.
Why are some annotations blocked for CL terms?

[matentzn]

Looks great! Now QC should pass. Thanks!

[ghost]

Looks great! Now QC should pass. Thanks!

Why are some annotations blocked for CL terms?

[matentzn]

Generally, this solves two purposes:

1. Make sure wrong annotations are not added accidentally (it's cheaper to list the allowed properties then to anticipate the millions of wrong combinations)
2. make sure to avoid uncontrolled annotation proliferation. Like in a datamodel, we want adding annotations to be an explicitly sanctioned process by the CL editors committee and not something left to the discretion of individual taste.

[ghost]

Generally, this solves two purposes:
...

Thank you for the context and for the review!