This happened on different projects:
After having a first mapping to a shared dimension, we did create a new shared dimension and re-create the mapping.
After that, when exporting the .trig file of the project, we can see that some former triples are still there.
This is not causing any problem that I am aware of, as I do not know how that 'a prov:Entity' is used.
But there seems to be some "mess" during RDF updates, which is certainly not something good.
Example:
In one project, the mapping was done on 3 different versions of the shared dimension, but we can see that all triples are still in the .trig:
<https://ld.admin.ch/cube/dimension/ghg_emission_sectors_co2_ordinance_test4_gen_fab/1> a prov:Entity .
<https://ld.admin.ch/cube/dimension/ghg_emission_sectors_co2_ordinance_test3_gen_fab/1> a prov:Entity .
<https://ld.admin.ch/cube/dimension/ghg_emission_sectors_co2_ordinance/1> a prov:Entity .
This happened on different projects: After having a first mapping to a shared dimension, we did create a new shared dimension and re-create the mapping. After that, when exporting the .trig file of the project, we can see that some former triples are still there.
This is not causing any problem that I am aware of, as I do not know how that 'a prov:Entity' is used. But there seems to be some "mess" during RDF updates, which is certainly not something good.
Example: In one project, the mapping was done on 3 different versions of the shared dimension, but we can see that all triples are still in the .trig: