Re: [dxwg] Create generic properties such as "hasExpression" or "documentedIn" instead of hasResource/(hasRole | hasArtifact) (#747)

Note that one issue for this is the loss of flexibility for representing the roles: using as many properties  (possibly in a hierarchy) as there are possible roles work well when the number of roles is small and controled. It will become unwieldy if extensions have to be devised, or if the hierarchy of property is difficult to conceive (e.g. in case there is multiple inheritance, or properties that do not relate very well to any other). In the latter case, and especially if there's no requirement for expressing formal axioms about the relationships/roles, then a simple SKOS-inspired vocabulary for these relationships/roles will probably be easier to handle.

-- 
GitHub Notification of comment by aisaac
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/747#issuecomment-463003183 using your GitHub account

Received on Wednesday, 13 February 2019 00:33:29 UTC