Some shacl node properties will be derived from LinkML slots that have identifier: true and would be required to be completed in the shacl-based UI in order to save the node data. Some identifiers would be full URIs, some will be CURIEs with globally resolvable prefixes, and some identifiers will only need to make sense within the context of some local namespace particular to the schema. The implementers/maintainers of the schema will likely need to either define which prefix the id needs to use (for a given class), or provide some guidance to let the user decide.
In any event, the user interface will need to be able to identify a property that is an identifier, directly (unlikely that this is possible) or indirectly. This challenge of identifying such a property has overlap with https://github.com/psychoinformatics-de/shacl-vue/issues/23.
It would likely be useful to allow the user to select their preferred prefix for the ID, and then only enter the post-prefix part of the identifier. To achieve this, one could implement a custom editor component in view, that matches based on the solution of how to identify a property that is an identifier.
The aspect of providing some ui guidance can actually be generalised for any slot (not only identifiers), by adding some annotation in the LinkML schema (better yet if that annotation term comes from a standard vocabulary).
Some shacl node properties will be derived from LinkML slots that have
identifier: trueand would be required to be completed in the shacl-based UI in order to save the node data. Some identifiers would be full URIs, some will be CURIEs with globally resolvable prefixes, and some identifiers will only need to make sense within the context of some local namespace particular to the schema. The implementers/maintainers of the schema will likely need to either define which prefix the id needs to use (for a given class), or provide some guidance to let the user decide.In any event, the user interface will need to be able to identify a property that is an identifier, directly (unlikely that this is possible) or indirectly. This challenge of identifying such a property has overlap with https://github.com/psychoinformatics-de/shacl-vue/issues/23.
It would likely be useful to allow the user to select their preferred prefix for the ID, and then only enter the post-prefix part of the identifier. To achieve this, one could implement a custom editor component in view, that matches based on the solution of how to identify a property that is an identifier.
The aspect of providing some ui guidance can actually be generalised for any slot (not only identifiers), by adding some annotation in the LinkML schema (better yet if that annotation term comes from a standard vocabulary).