PROV-DM Case Study (part 3)

https://qillknows.wordpress.com/

Last post (PROV-DM Case Study (part 2)), we had added some roles in our graph and demonstrated the revision on dataset. Now, we imagine that someone has quoted some text about this article, and provenance decided that this text (exb:quoteInBlogEntry‐20130326) is quoted from the article. The newspaper has also anticipated that there could be revisions to the article, so they created identifiers for both the article in general (exn:article) as a URI that got redirected to the first version of the article (exn:articleV1), allowing both to be referred to as entities in provenance data. Finally, after new dataset has arrived and a new chart was built, a new article, exn:articleV2 was created. In addition, The entities of exn:articleV1 and exn:articleV2 are related. Continue reading

PROV-DM Case Study (part 1)

https://qillknows.wordpress.com/

After looking at PROV-DM (Data Model), let’s try to implement that through case study. The case study was taken from W3C, about online newspaper that publishes an article with a chart about crime statistics based on data (GovData) provided by a government portal. The article includes a chart based on the data, with data values composed (aggregated) by geographical regions. Based on that sentence, we can derive 5 entities refer to:
•The article (exn:article),
•An Original data set (exg:dataset1),
•A list of regions (exc:regionList),
•Data aggregated by region (exc:composition1),
•A chart (exc:chart1) Continue reading