Charles Tapley Hoyt

Hi @jannahastings, I think this got lost in the pile of issues. I've come back to this recently and begun curating and storing some of these in a repository at...

Thanks @balhoff. We're actually using exactly that document as a basis for alignment between BioLink and the Bioregistry. The remaining prefixes we haven't yet been able to contextualize or otherwise...

@bgyori can we revisit this? I think it will solve the issue I showed last friday on cogex that the MONDO term for asthma wasn't connected to the rest of...

I still don't think this is addressed

@nataled simplest way might be to create a new label for the issue tracker / PRs

Another one for this list: #2454

I see, I never thought of this before. You might be able to use https://github.com/cthoyt/class-resolver/blob/403da7a0dd54e7174d533894887de7723cc9a6b6/src/class_resolver/base.py#L142-L147, but that's also no so obvious

@jamesaoverton does this mean if there's a mismatch then it will explode? I think it will still be useful to just get the base ontology information.

So if the import failing to parse doesn't cause the entire job to break, then this is fine for me.

Reading through https://github.com/mapping-commons/sssom-py/compare/v0.3.41...v0.4.0-rc1 is not fun but is one way to do it. Maybe also contextualizing with the various PR descriptions