Silvano Cirujano Cuesta

> It looks like this PR hasn't seen activity in a long time. If you would still like to work on this please respond here and I'll keep it open....

I've also created a small Bash script to reproduce the issue on my side, you might be interested on it (you'll want to remove the `.txt` extension, GitHub doesn't allow...

> It is also not possible to remove a slot requirement if the requirement is set in the definition of the slot and then removed using slot_usage. I'm sorry, but...

The time I reported this issue, I wasn't fully understanding LinkML expectations. @turbomam made me aware that it wasn't supposed to work due to the fact that non-monotonic inferences are...

AFAIK no news on this issue. I haven't tried it out again since I reported it, but I assume that it hasn't been fixed yet. I haven't had neither the...

I stumbled once again upon this issue... The main problem is that LinkML is not using so-called "safe CURIEs" and therefore we have [foreseen ambiguities](https://www.w3.org/TR/2010/NOTE-curie-20101216/#sec_2.2.) that are IMO being resolved...

2 would be the most robust way to resolve it (that's why it's the recommended disambiguation solution in the spec). But I assume that such a breaking change (it would...

@cmungall IMO we can move the conversation to #258 and close this issue. I'm not closing it since you already labeled it and also added it to the milestone.

> Can this be closed? What needs to be done to "move the conversation to #258" - did you want the comments to be copied over, or just have further...

Is something happening around the topics mentioned in this PR? I see a real need to address this topic, but no movement for the last 2 months...