Allow for class/slot specific range hints #34

Open
opened 2025-02-09 06:37:37 +00:00 by mih · 0 comments
mih commented 2025-02-09 06:37:37 +00:00 (Migrated from hub.datalad.org)

Related conceptually to #9

Sometime a schema slot range is uriorcurie for technical reasons. Maybe because a more suitable class (for the purpose of manual annotation is not available at that schema layer).

It would be useful to be able to declare a range hint (in the editor config) that makes it present instances of a particular class (also), rather than just allow for a plain identifier.

I concrete example is an annotation of "approved audiences" fir a metadata record. This would be a low-level schema feature, but for manual annotation only instances of Agent make sense (for selection).

Related conceptually to #9 Sometime a schema slot range is `uriorcurie` for technical reasons. Maybe because a more suitable class (for the purpose of manual annotation is not available at that schema layer). It would be useful to be able to declare a range hint (in the editor config) that makes it present instances of a particular class (also), rather than just allow for a plain identifier. I concrete example is an annotation of "approved audiences" fir a metadata record. This would be a low-level schema feature, but for manual annotation only instances of `Agent` make sense (for selection).
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
trr379/annotate-trr379-demo#34
No description provided.