(Re)defining isDefinedBy

[leskneebone]

The vocform implements a field for the isDefinedBy property in alignment with the VocPub profile.
https://agldwg.github.io/vocpub-profile/specification.html#2.3.2

I think the VocPub profile spec needs revision here. Membership in a concept scheme via skos:inScheme should be sufficient for deriving what is intended by rdfs:isDefinedBy. Note that a concept may have multiple skos:inScheme relationships. In most cases a concept will have only one inScheme relationship.

rdfs:isDefinedBy is better suited to referencing non-vocabulary, or not-semantic resources, such as framing literature (e.g. legislation, policy, seminal works etc). RDFS doesn't know anything about skos concepts or concept schemes. It's fair to say that linking an sos:concept to a skos:conceptScheme via rdfs:isDefinedBy is valid, but it shouldn't be a default setting, as the VocPub implies.

Happy to hear other views on this, especially VocPub fans (@nicholascar) :-). As stated, the vocform implementation is correct, as far as VocPub goes. I'm really questioning VocPub itself.