Define "slot_uri"

[only1chunts]

@turbomam is this definition correct?

A Uniform Resource Identifier (URI) is a string of characters that identifies a resource, a slot_uri is the URI of a LinkML slot. The URIs's used in MIxS are based on a numerical identifier, the MIXS_ID

If so, where is the appropriate place in the LinkML document to hold that definition so that makeDocs can present it? (same question for all the other definitions in metaslot definitions project

[turbomam]

All slots in a LinkML model have slot_uris

If they are not asserted, then they are silently inferred, using the schema's default prefix and the slot's name.

I can't remember what craziness happens in the schema doesn't have a defaul_prefix.

Bottom line: all MIxS terms should assert their slot_uri so it's not left to some algorithm.

The slot_uri can be totally unrelated to the slot, and in fact, that is the pattern we have been following. MIxS slot_uris are based on a numerical identifier. That's a good practice because the slot_uri and the semantics can be held cosntant, even if the community decides that a change should be made to the name.

From that perspective, it would be preferable for NCBI and other INSDC databases to include the id or slot_uri in their representations, like

https://www.ncbi.nlm.nih.gov/biosample/docs/attributes/

[turbomam]

Now, the question that remains open: what tools and policies will we use to manage MIxS ids? Are in-use, retired or pending ids saved in any system of record?