Stream: implementers
Topic: Proposal for denormalization of source
Grahame Grieve (Oct 24 2017 at 02:39):
At present, you can describe the provenance of a resource in a fair degree of detail using the Provenance resource. It's based on W3C Prov work, and you can specify the source material, the agents involved, etc. This is good stuff.
Grahame Grieve (Oct 24 2017 at 02:39):
but what you can't do easily is describe the source of the resource in simple terms - especially if you just have a simple text description of the source from upstream. Provenance is too rich.
Grahame Grieve (Oct 24 2017 at 02:41):
I think we could add to Resource.meta a property
source : String [0..1] "A short text description of the source of the data in this resource" with a note that it is suitable to be used in a popup/flyover in a UI, or etc, and that it is a denormalized summary of full information that may/should also be available in a provenance resource that refers to this resource
John Moehrke (Oct 25 2017 at 00:06):
We have plenty of other parts of Provenance scattered within resources as necessary... (W5)... But, why would this not follow the similar rule we have for W5, that is a resource can add a provenance description if it is critical to that resource. I think adding it to Resource.meta might be going to far and start us down the path of putting all of Provenance into Resource.meta. What about revisions, are they required to clear this element and add their revision provenance?... Note, I am not necessarily against this change, just want to think out-loud about the potential negative impact.
Grahame Grieve (Oct 25 2017 at 00:14):
I think that revisions would usually update the content as part of the revision. I agree with your concerns which is why I've taken so long to raise this. But what do you do, no, if all you have is text provenance information? and this is a common refrain....
John Moehrke (Oct 25 2017 at 00:16):
understood.. hence why I am mostly supportive.
Grahame Grieve (Nov 16 2017 at 09:47):
@Dunmail here you go
Grahame Grieve (Nov 23 2017 at 01:35):
ok, added this so people can look at it
Eric Haas (Nov 25 2017 at 01:43):
Here http://build.fhir.org/resource.html#Meta
right?
Grahame Grieve (Nov 25 2017 at 02:47):
Yes
John Moehrke (Nov 25 2017 at 12:49):
Could have a comment to explain how this is an alternative to Provenance. That is to explain that it is intended to be a lighter weight way to express the source, and thus can only point at the source and not explain W5. Wonder if the directionality difference between this and Provenance should be explained (Is it likely someone will set source to their Provenance record)?
Last updated: Apr 12 2022 at 19:14 UTC