This document provides a data model describing the structure and content of the IVOA Provenance Data Model. This re-uses the concepts from the W3C Provenance DM, but extends it with a description layer for Activities and Entities and bridges to classes existing in other IVOA datamodels. For a DatasetEntity , location provides a way to access to the data file. We consider it can be instanciated as : - a url to the datafile , proposed by the data archive , so a valid access url as designed in IVOA protocols . - a datalink service which serves the data file in other words : at the end of this link , direct or service provided , you will reach the data file Base Data Types V1.0 (2014) A thing which is consumed or produced in a task , namely here in the astronomical domain. It represents some data file , or an instrument, and has a location or a quality status for instance , and has a value. link to the corresponding EntityDescription instance. Many Entities may share the same EntityDescription instance. Association between an Agent and an Entity it is responsible for . A unique identifier for an Entity. Must be unique in the domain, here astronomy. The IVOA identifiers specification can help to mint such an identifier. This is a text string which designate the Entity for display in application or diagrams . It can follow various syntax and naming conventions depending on the Entity subclass : dataset, quality flag, device name convention, etc . The access link to the entity represented by the instance : a value , a dataset. the time of generation for the entity , in ISOTime Time stamp to indicate the Entity was discarded in the system. however it is still there as a historical record. A short text about some peculiar information on the instance. The link from the progenitor Entity to its descendant. This indicates a dependency from one Entity (generated) to its progenitor (used). The provenance information system may not have the involved Activity instance implemented into the data base. A collection of Entities. It is a way to consider a set of entities when produced and consumed with respect to an Activity. Allows coarse description of the provenance. A task executed at some time. It consumes products via relations of type Used and produces results via linrelations of type WasGeneratedBy. The method applied for this task is described in the ActivityDescription class and its subtree. <Enter note text here> <Saisir le texte de la note ici> <Enter note text here> This allows to know when the activity was launched . This is recommended to fill in as it helps to check dependencies and errors into the database. The "comment" attribute allows to store comments in free text on each instance. It can be filled occasionally and is not controled . Binds an Activity to the Entities it consumes . <Enter note text here> This link points to some description of the Usage in the context of one specific ActivityDescription. Binds an Entity to the Activity that produced it as a result. This link points to some description of the results produced in the context of one specific ActivityDescription. A person or an organisation that was involved in the follow-up of an Activity, or can be credited for the production of an Entity. defines the AgentType : Individual or Organisation The relation when an Agent has some responsibility, explained in the role attribute with respect to an Activity instance. A label for the Agent to explain his function or responsability with respect to an Activity instance. The label values belong to the AgentRole type defined in the Provenance vocabulary. Links an Agent to the Entity it is responsible for . Various roles for this relation are allowed and defined in the Provenance vocabulary under AgentRole A label for the Agent to explain his function or responsability with respect to an Entity instance.The label values belong to the AgentRole type defined in the Provenance vocabulary. It describes the constraints to obey for an Entity before being used or produced by an Activity. Information can be on : format, encoding, size, version? , etc .The values stored for an EntityDescription attribute will/could be differentwhether the Entity is linked via a Used link or via a WasGeneratedBy link.Example:Regridding activities gets input image files from various filters or various exposures in the  same filter. <ul> <li>The required format is FITS, with encoding 32 bits /pixels</li> <li>The output entities are one regridded image, that can be a Fits image again  and a positional  error map (astrometry confidence) that can be either a preview image stored in JPEG or a FITS image .</li> </ul> A class to describe a method applied for the execution of an Activity.The system ActivityDescription , Usage Description and Generation Description has a tree structure and can be seen as a template for launching, tracing an activity.It can be completed with domain specific documentation, provided by link to some external file or service. Short text of explaination. This class gathers description features about the products an ActivityDescription consider as input resources. It can distinguish between various roles and types of Entities consumed by the task described by the ActivityDescription class. This class gathers description features about the products an ActivityDescription consider as output results. It can distinguish between various roles and types of Entities generated by the task described by the ActivityDescription class. A label that describes the function of what was produced. It is defined in the context of an ActivityDescription instance. Short text explaining the products issued by an ActivityDescription. An entity that only contains a value. Its features like data type , ucd , units etc. are described in the instance linked to it of type ValueDescription. The value of the Entity. The data type , meaning, units, etc., are stored in the ValueDescription instance bound to it. A description of the properties of a ValueEntity. can serve as description of multiple instances of ValueEntity. An Entity which represents a data file in the Provenance system. It is not the data file itself . The DatasetEntity has a link to the science data distributed in the science archive . Such dataproducts are modeled in the IVOA using the DatasetMetadata model and accessed thtough protocols , like tap or ObsTAP. The data themselves are not represented in the Provenance data model. The description of a DatasetEntity. Can be pointed to by multiple instances of DatasetEntity. This package gathers the necessary classes for expressing the configuration of a task before, during and after execution. We consider only the executed version will be stored in a provenance information system. A Parameter class allows to expose the values read by an activity to parametrize its execution. Each Parameter is identified by its name and can be queried. A Parameter is a specific class.  In contrary to ValueEntity it does not hold all the relations an Entity may have : <ul> <li>no Agent link,</li> <li>no hadMember link</li> <li>no Used link</li> <li>no wasGeneratedBy</li> </ul> If a Parameter value is chosen with respect to a Result Entity R, computed on purpose to generate this configuration value, or just reused from a previous excecution,  then the Parameter Instance may have a wasInfluencedBy  relation to this Result Entity R. This Entity R is then described in the system with the usual Entity links wasGeneratedBy and the Activity generating this value may also be described. The WasInfluencedBy relation is part of the relations defined in the vo-dml list of relations (College Park version).The description of this parameter is stored in the ParameterDescription instance, which is connected via a Parameter --> ParameterDescription link, a Subset of Entity --> EntityDescription linkThis allow Parameters to be totally focused on the Configuration part of the Provenance DM , but still be traced to the Entities they may be derived from when necessary.Identified and dedicated access to the configuration  information allows to trace and interpret the quality of the activities /result Entities more efficiently than sorting between Entity types and Used relations types.  A Parameter instance can have a value derived from a ValueEntity value element computed previously by some former Activity instance . Therefore , the ValueEntity it refers to is generated with another instance of the Activity class, in a different generation scenario executed previously. The value of the parameter. The data type , meaning, units, etc., are stored in the ParameterDescription instance bound to it. To represent the semantics of the values entered to run an activity in addition to data sets. A Parameter can be queried, on its value and on its description. A short text that explains the content and purpose of this Parameter. This is an association class binding an Activity Instance to one configuration artefact which can be a Parameter instance or a ConfigFile instance . Attribute "artefactType" holds the type of its target . <Enter note text here> The values used to control the activity can be provided as a Configuration file document, which contains a key=value list . This belongs to the Activity Configuration package , has the same life cycle as the activity which is configured from it . However the description of such a Configuration file , is the same as a DatasetDescription . It inherits the attributes , but not the behaviour as it cannot be involved in link to UsageDescription reserved to Entities stored in the Core Provenance. The mechanism to search a value into this Document is managed by the project providing the Provenance information, usually using contextual text search. This is outside the scope of this model. <Enter note text here> This is a text string which designate the Entity for display in application or diagrams . It can follow various syntax and naming conventions depending on the Entity subclass : parameter , documents, etc . The Description attributes of the ConfigFile. Mainly a contentType to specify the format , and a text field for comment if needed . A short text that explains the content and purpose of the configuration file. A dataset feature summary as exposed in the DatasetMetadata data model and used via IVOA models and protocols like ObsCore and ObsTAP. The configuration for an Activity ( job) can be fully explicit , with a list of searchable parameters , or expressed into a document file storing the configuration . This attribute contains the type of config information at the end of the wasConfiguredby association instance . The various values for the role keyword for an Agent with respect to an Activity or an Entity. This class binds to the description of parameters or config file . It works like a bridge on the Description side , between ActivityDescription and the description for Parameter and configFile. not used currently. Short text for explanation. A literal for specifying the Agent type : Individal or Organisation or SoftwareAgent Title=IVOA Provenance Data Model Description Subject=IVOA Provenance Data Model Description Status=PR Author=PR Version=M.LOUYS Address=Mireille LOUYS - ASTERICS -DADI Provenance Project Copyright=@ all rights reserved Status=Description