After a discussion with @ucsdlib/domm we agreed to do a bit more thinking about the best way to model the relatedResource class and related predicates that will use the class.
After speaking with @lsitu we agreed that it would be best to do some R&D, from a technical standpoint, to help make a decision about the following options:
Create individual relatedResource predicates for each "type". The class itself only has a label and (optional) URL properties
Create a single relatedResource predicate. The class contains a label, (optional) URL, and a type property that pulls from a CV list.
Rationale
Knowing how the Hyrax framework best handles this kind of modeling choice, from both a form and end-user display standpoint, will hopefully help us decide how to complete this mapping.
Descriptive summary
After a discussion with @ucsdlib/domm we agreed to do a bit more thinking about the best way to model the relatedResource class and related predicates that will use the class.
After speaking with @lsitu we agreed that it would be best to do some R&D, from a technical standpoint, to help make a decision about the following options:
Rationale
Knowing how the Hyrax framework best handles this kind of modeling choice, from both a form and end-user display standpoint, will hopefully help us decide how to complete this mapping.