Re: [dxwg] Relax global domain axioms on many dcat properties

@akuckartz - deprecate but not delete - indeed! However, there has been no proposal that I've seen to delete (or even deprecate) any terms. The expectations around this are quite clear. 

The issue on the table here is whether and how much to adjust the definitions of some existing terms. You have quite validly raised the question about whether any proposed changes are sufficient that the meaning has changed, so new URIs are required. 

As mentioned at the top of the thread, this concern was triggered by the discovery that re-use of some of the DCAT properties is - almost certainly inadvertently - disallowed because global domain/range constraints were used ubiquitously in DCAT v1 - see #95 and #97 . This issue #110 is an 'umbrella' for a set of individual issues to examine each property, in turn, to verify if the global constraints are indeed appropriate. 

My take on where we have got to so far: 

@makxdekkers initially proposed that the starting assumption should be to _not_ have domain constraints, in order to enable maximum re-use https://github.com/w3c/dxwg/issues/110#issuecomment-365337292 . - this got quite a few +1s

@philarcher provided a bit of context around the use of global constraints, and maybe a hint about the desirability of moving away from that modeling style https://github.com/w3c/dxwg/issues/131#issuecomment-366165887 . 

I have suggested that we might adopt a pattern recently used by the Spatial Data group, in which the vocabulary is packaged in multiple graphs, which allows users to get the level of axiomatization that they prefer https://github.com/w3c/dxwg/issues/110#issuecomment-366585293 and https://github.com/w3c/dxwg/issues/111#issuecomment-366556100 . 

@makxdekkers sees some risks in this https://github.com/w3c/dxwg/issues/110#issuecomment-366769200

Several people have quite reasonably cautioned that any changes **must** be motivated by real documented requirements.

-- 
GitHub Notification of comment by dr-shorthair
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/110#issuecomment-366814802 using your GitHub account

Received on Monday, 19 February 2018 22:12:26 UTC