- From: makxdekkers via GitHub <sysbot+gh@w3.org>
- Date: Mon, 19 Mar 2018 12:08:42 +0000
- To: public-dxwg-wg@w3.org
@arminhaller I think there are two ways to handle conflicting licences. The first is, as you propose, to expose the conflict to the world. This lets the publisher off the hook and moves the problem to the consumer to sort out -- maybe by contacting the publisher to find out what the intention and legal situation is. The second approach could be to force the publisher to resolve the conflict during the publication process, i.e. making sure that in the published metadata there is no conflict. This puts the problem where I think it belongs, namely at the publisher. It is much easier for publishers to resolve the issue -- they would decide which of the conflicting licences applies to a particular distribution and put that in the metadata of the distribution; no need for the consumer to try and sort it out. I do not entirely understand the situation you describe where multiple datasets are packaged into a single Distribution -- this is a situation that I don't think is part of the current DCAT model. Is it? -- GitHub Notification of comment by makxdekkers Please view or discuss this issue at https://github.com/w3c/dxwg/issues/104#issuecomment-374190496 using your GitHub account
Received on Monday, 19 March 2018 12:08:46 UTC