documentation required in LinkML or MIxS: who wins when there is a conflict in a slot definition/usage between a `is_a` parent and a `mixin`?

[turbomam]

first: determine what slots are used by both Checklists and Extensions

[turbomam]

may especially be of interest for recommended and required

[turbomam]

see src/scripts/mims_and_soil_slots.py

I'm illustrating this with a slot called conflicting, which has conflicting patterns

It looks like Mims (a Checklist, bound with mixins) wins over Soil (an Extension, bound with is_a) in MimsSoil

So what if there are multiple mixins?

  MimsSoil:
    description: MIxS Data that comply with the Mims checklist and the Soil Extension
    title: Mims combined with Soil
    in_subset:
      - combination_classes
    is_a: Soil
    mixins:
      - Mims
    class_uri: MIXS:0010007_0016012

conflicting slot's usage in Mims:
name: conflicting
pattern: ^[a-zA-Z]+$

conflicting slot's usage in Soil:
name: conflicting
pattern: ^[0-9]+$

Induced slot conflicting in MimsSoil

name: conflicting
description: intentionally set to incompatible states between a Checklist and an Extension
from_schema: https://w3id.org/GenomicsStandardsConsortium/mixs-missing-value-sandbox
alias: conflicting
owner: MimsSoil
domain_of:

• Mims
• Soil

range: string
pattern: ^[a-zA-Z]+$

[turbomam]

If either the mixin or the is_a parent is required: true, then in my opinion the combination should be required: true