From d8fd95a2f23c6d472bf75556bce94889057f5f89 Mon Sep 17 00:00:00 2001
From: EvaGarciaAlvarez <93911102+EvaGarciaAlvarez@users.noreply.github.com>
Date: Fri, 27 Sep 2024 12:33:12 +0200
Subject: [PATCH] Update general_provenance.md

---
 provenance/general_provenance.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/provenance/general_provenance.md b/provenance/general_provenance.md
index 567a792d..acc03d19 100644
--- a/provenance/general_provenance.md
+++ b/provenance/general_provenance.md
@@ -39,7 +39,7 @@ Provenance is typically realised as metadata of a documented object, such as a d
 ## Good practices for provenance information
 ### Considerations
 1. **Purpose**. Provenance collection should serve a pre-defined purpose. Without a defined purpose for provenance collection, it is not possible to determine what provenance information must be collected to serve a specific use case. 
-  a. **Backward traceability** of documented objects is **the most crucial purpose** of provenance collection, as it is a prerequisite for any other purposes. For instance, we can not assess the quality of a dataset without being able to trace back from what other objects and how the dataset was generated.
+* a. **Backward traceability** of documented objects is **the most crucial purpose** of provenance collection, as it is a prerequisite for any other purposes. For instance, we can not assess the quality of a dataset without being able to trace back from what other objects and how the dataset was generated.
 2. **Interoperability**. Generated provenance information should be interoperable with provenance coming from other sources, to enable its **automated** processing. This is particularly important in settings where objects described by provenance can be combined or shared (between organisations). The interoperability should be achieved on both semantic and syntactic levels. The Common Provenance Model (see Existing approaches) serves as a glue to integrate domain specific provenance standards.
 3. **Trustworthiness**. The generated provenance information must be trustworthy so others can make decisions using the information stored in provenance. The level of required trustworthiness is dependent on the purpose, for which provenance is used. 
 4. **Confidentiality & privacy**. Provenance may contain any non-public or sensitive information. It would be possible for the provenance to contain e.g. location and time of data acquisition and (contact) information about the principal investigator of a study. For that purpose, confidentiality of provenance must be addressed and the privacy of the subjects must be protected.