Damion Dooley

Ah, I see, is_a being single valued could be problematic visa vis inheritance etc. d.

LinkML has a "tree_root" marker that can be set explicitly (or is otherwise inferred within various LinkML interrogation methods as a class that doesn't show up in range of another...

What we are seeing with the new DataHarmonizer 1-many data schema is that we need a "Container" class in a LinkML specification that lists all the Classes to show as...

Closing this as we are phasing out dh_interface in favour of the Container object having top-level class to display in a schema as a selectable template, and underlying 1-many classes...

So I see this table in the Gold paper that summarizes the dependency: I guess the first challenge is how to wind these relationships into the LinkML enums? Has that...

So its a polyhierarchy - and terms like "Biofilm" can occur at several levels too. This argues for having each enumeration's items have a 'pertinent to' relation to one or...

How is the need for this functionality in DH looking now? It seems like validation rules wouldn't handle this; instead dynamic filtering is required.

The DH pull is just about ready for testing. I'll let you know later today but you can actually see it in action with the TEST template in pull request's...

One helpful file in that regard is a separate term deprecation file containing all the deprecated terms and a reference to the replacement term. This can be an import file...

This suggests a feature for dataset management perhaps via dataharmonizer, namely an option to supply dataharmonizer with a list of mappings from deprecated to replaced values, such that dataharmonizer could...