{"id":141909,"date":"2013-11-17T16:28:15","date_gmt":"2013-11-17T16:28:15","guid":{"rendered":"https:\/\/staging2.simonw59.sg-host.com\/pav-ontology-provenance-authoring-and-versioning\/"},"modified":"2022-05-26T13:43:40","modified_gmt":"2022-05-26T13:43:40","slug":"pav-ontology-provenance-authoring-and-versioning","status":"publish","type":"post","link":"https:\/\/force11.org\/post\/pav-ontology-provenance-authoring-and-versioning\/","title":{"rendered":"PAV ontology: Provenance, Authoring and Versioning"},"content":{"rendered":"<div class=\"ct_body\">\n<p>Authors: Paolo Ciccarese<br \/>\n\tStian Soiland-Reyes<br \/>\n\tKhalid Belhajjame<br \/>\n\tAlasdair J G Gray<br \/>\n\tCarole Goble<br \/>\n\tTim Clark<\/p>\n<p>Provenance is a critical ingredient for establishing trust of published scientific content. This is true whether we are considering a data set, a computational workflow, a peer-reviewed publication or a simple scientific claim with supportive evidence. Existing vocabularies such as DC Terms and the W3C PROV-O are domain-independent and general-purpose and they allow and encourage for extensions to cover more specific needs. We identify the specific need for identifying or distinguishing between the various roles assumed by agents manipulating digital artifacts, such as author, contributor and curator.<br \/>\n\tWe present the Provenance, Authoring and Versioning ontology (PAV): a lightweight ontology for capturing just enough descriptions essential for tracking the provenance, authoring and versioning of web resources. We argue that such descriptions are essential for digital scientific content. PAV distinguishes between contributors, authors and curators of content and creators of representations in addition to the provenance of originating resources that have been accessed, transformed and consumed. We explore five projects (and communities) that have adopted PAV illustrating their usage through concrete examples. Moreover, we present mappings that show how PAV extends the PROV-O ontology to support broader interoperability.<br \/>\n\tThe authors strived to keep PAV lightweight and compact by including only those terms that have demonstrated to be pragmatically useful in existing applications, and by recommending terms from existing ontologies when plausible.<br \/>\n\tWe analyze and compare PAV with related approaches, namely Provenance Vocabulary, DC Terms and BIBFRAME. We identify similarities and analyze their differences with PAV, outlining strengths and weaknesses of our proposed model. We specify SKOS mappings that align PAV with DC Terms.<\/p>\n<\/div>\n<p class=\"ct_meta\"><span class=\"ct_label\">Archive:<\/span>&nbsp;<a class=\"ct_archive\" target=\"_blank\" href=\"https:\/\/archive.force11.net\/node\/6386\" rel=\"noopener\">https:\/\/archive.force11.net\/node\/6386<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Authors: Paolo Ciccarese Stian Soiland-Reyes Khalid Belhajjame Alasdair J G Gray Carole Goble Tim Clark Provenance is a critical ingredient for establishing trust of published scientific content. This is true whether we are considering a data set, a computational workflow, a peer-reviewed publication or a simple scientific claim with supportive evidence. Existing vocabularies such as &#8230; <a title=\"PAV ontology: Provenance, Authoring and Versioning\" class=\"read-more\" href=\"https:\/\/force11.org\/post\/pav-ontology-provenance-authoring-and-versioning\/\" aria-label=\"More on PAV ontology: Provenance, Authoring and Versioning\">Read more<\/a><\/p>\n","protected":false},"author":205907,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"advgb_blocks_editor_width":"","advgb_blocks_columns_visual_guide":"","footnotes":""},"categories":[151],"tags":[],"force11":[],"blog_series":[],"working_group":[],"class_list":["post-141909","post","type-post","status-publish","format-standard","hentry","category-news"],"acf":[],"author_meta":{"display_name":"Tim Clark","author_link":"\/members\/tim-clark"},"featured_img":null,"coauthors":[],"tax_additional":{"categories":{"linked":["<a href=\"https:\/\/force11.org\/category\/news\/\" class=\"advgb-post-tax-term\">News<\/a>"],"unlinked":["<span class=\"advgb-post-tax-term\">News<\/span>"]}},"comment_count":"0","relative_dates":{"created":"Posted 12 years ago","modified":"Updated 4 years ago"},"absolute_dates":{"created":"Posted on 17 Nov 2013","modified":"Updated on 26 May 2022"},"absolute_dates_time":{"created":"Posted on 17 Nov 2013 16:28","modified":"Updated on 26 May 2022 13:43"},"featured_img_caption":"","series_order":"","_links":{"self":[{"href":"https:\/\/force11.org\/wp-json\/wp\/v2\/posts\/141909","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/force11.org\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/force11.org\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/force11.org\/wp-json\/wp\/v2\/users\/205907"}],"replies":[{"embeddable":true,"href":"https:\/\/force11.org\/wp-json\/wp\/v2\/comments?post=141909"}],"version-history":[{"count":0,"href":"https:\/\/force11.org\/wp-json\/wp\/v2\/posts\/141909\/revisions"}],"wp:attachment":[{"href":"https:\/\/force11.org\/wp-json\/wp\/v2\/media?parent=141909"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/force11.org\/wp-json\/wp\/v2\/categories?post=141909"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/force11.org\/wp-json\/wp\/v2\/tags?post=141909"},{"taxonomy":"force11","embeddable":true,"href":"https:\/\/force11.org\/wp-json\/wp\/v2\/force11?post=141909"},{"taxonomy":"blog_series","embeddable":true,"href":"https:\/\/force11.org\/wp-json\/wp\/v2\/blog_series?post=141909"},{"taxonomy":"working_group","embeddable":true,"href":"https:\/\/force11.org\/wp-json\/wp\/v2\/working_group?post=141909"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}