- From: Riccardo Albertoni via GitHub <sysbot+gh@w3.org>
- Date: Thu, 15 Feb 2018 12:01:59 +0000
- To: public-dxwg-wg@w3.org
+1 to Antoine. @antoine > there's no crucial adverse consequence indeed Not sure, maybe the adversities are not so crucial, but the tons of inferred prov:Entity added to dcat:Dataset instances without no actual PROV properties are in my opinion a quite annoying risk coming from the prov:Entity subclassing. @dr-shorthair > I do see a benefit of adding the prov:Entity relationship now because it would tell users 'if you do want to record complex provenance metadata, then use PROV, rather than inventing something new'. I see your goal, but I am not sure the subclassing is an effective solution to meet it: probably a consumer who recognizes what a prov:Entity is, already knows PROV. I suspect that explicitly stating in the DCAT document > if you do want to record complex provenance metadata, then use PROV, rather than inventing something new is still our best option to meet the goal, at least at this stage of the discussion. Perhaps we want to return to this specific issues after that we have solved #128 ... -- GitHub Notification of comment by riccardoAlbertoni Please view or discuss this issue at https://github.com/w3c/dxwg/pull/94#issuecomment-365907146 using your GitHub account
Received on Thursday, 15 February 2018 12:02:03 UTC