Currently, the https://credreg.net/ctdl/terms/hasMember property supports a limited subset of CTID-enabled CTDL classes as members of a collection. This seems too limiting. I would think the range of that property should be rdfs:Resource (or maybe xsd:anyURI to match ceterms:proxyFor) instead, but this may have ramifications for implementations (within CE and/or CaSS) that we'd need to consider.
For example, we currently have a use case that requires having collections of Competency Frameworks, and the schema does not currently allow this.
Currently, the https://credreg.net/ctdl/terms/hasMember property supports a limited subset of CTID-enabled CTDL classes as members of a collection. This seems too limiting. I would think the range of that property should be rdfs:Resource (or maybe xsd:anyURI to match ceterms:proxyFor) instead, but this may have ramifications for implementations (within CE and/or CaSS) that we'd need to consider.
For example, we currently have a use case that requires having collections of Competency Frameworks, and the schema does not currently allow this.
Proposal: