diff --git a/src/chapter/4-introduction.md b/src/chapter/4-introduction.md index 9c696ab..5e0d282 100644 --- a/src/chapter/4-introduction.md +++ b/src/chapter/4-introduction.md @@ -53,7 +53,7 @@ Properties derived from draft [HealthDCAT-AP](https://healthdataeu.pages.code.eu A tabular overview of all classes and properties—including their range, cardinality, controlled vocabulary (if applicable), and usage notes—is provided below. A reference sheet containing this information can be found [here](Documents/Metadata_CoreGenericHealth_v2.xlsx). This sheet also documents property histories (compared to v1 of the Health-RI core metadata schema) and specifies the origins of new constraints (whether they stem from DCAT-AP v3, DCAT-AP NL, or HealthDCAT-AP). -## UML Class Diagram v2.0.2 +## UML Class Diagram v2.0.3 Health-RI Metadata Diagram diff --git a/src/excel/HealthRI_v2.0.2.xlsx b/src/excel/HealthRI_v2.0.2.xlsx index 029d8df..b6c4256 100644 Binary files a/src/excel/HealthRI_v2.0.2.xlsx and b/src/excel/HealthRI_v2.0.2.xlsx differ diff --git a/src/excel/HealthRI_v2.0.3.xlsx b/src/excel/HealthRI_v2.0.3.xlsx new file mode 100644 index 0000000..d755997 Binary files /dev/null and b/src/excel/HealthRI_v2.0.3.xlsx differ diff --git a/src/excel/~$HealthRI_v2.0.2.xlsx b/src/excel/~$HealthRI_v2.0.2.xlsx deleted file mode 100644 index cd772b0..0000000 Binary files a/src/excel/~$HealthRI_v2.0.2.xlsx and /dev/null differ diff --git a/src/property/properties-adms_identifier.html b/src/property/properties-adms_identifier.html index b74e39b..b51b440 100644 --- a/src/property/properties-adms_identifier.html +++ b/src/property/properties-adms_identifier.html @@ -14,7 +14,7 @@ notation A string that is an identifier in the context of the identifier scheme referenced by its datatype. skos:notation - xsd:string + rdfs:Literal 1..1 The value of this property is the alternative identifier of the dataset, next to the one indicated in the dct:identifier property. @@ -22,7 +22,7 @@ schema agency The name of the agency that issued the identifier. adms:schemaAgency - xsd:string + rdfs:Literal 0..1 N.A. diff --git a/src/property/properties-agent.html b/src/property/properties-agent.html index 3f4b0fa..f0e05d1 100644 --- a/src/property/properties-agent.html +++ b/src/property/properties-agent.html @@ -20,11 +20,15 @@ email - A email address via which contact can be made. This property SHOULD be used to provide the email address of the Agent, specified using fully qualified mailto: URI scheme [ RFC6068 ]. The email SHOULD be used to establish a communication channel to the agent. + A email address via which contact can be made. This property SHOULD be used to provide the email address of the Agent, specified using fully qualified mailto: URI scheme [  RFC6068  ]. The email SHOULD be used to establish a communication channel to the agent. foaf:mbox rdfs:Resource  (IRI) 1 - It is preferred to provide a general email address of the appropriate institution or department instead of a personal email address, even if an individual is described with this instance of foaf:Agent.\nThis protects their privacy and enables contact about the resource even after the individual has left the institution.\n\nThe email address has to be provided starting with mailto: prefix.\nFor example: mailto:info@example.com + It is preferred to provide a general email address of the appropriate institution or department instead of a personal email address, even if an individual is described with this instance of foaf:Agent. +This protects their privacy and enables contact about the resource even after the individual has left the institution. + +The email address has to be provided starting with mailto: prefix. +For example: mailto:info@example.com identifier diff --git a/src/property/properties-attribution.html b/src/property/properties-attribution.html index 66cfb6a..d2fe6c9 100644 --- a/src/property/properties-attribution.html +++ b/src/property/properties-attribution.html @@ -24,7 +24,10 @@ dcat:hadRole rdfs:Resource (IRI) 0..1 - Choose one of the roles as listed in the controlled vocabulary. Note that for HealthDCAT-AP, the list of roles might be extended in the future.\nExample: https://standards.iso.org/iso/19115/resources/Codelists/gml/CI_RoleCode.xml#processor

Controlled vocabulary
The value for the property must be selected from the specified vocabulary or list.

https://standards.iso.org/iso/19115/resources/Codelists/gml/CI_RoleCode.xml
https://jats4r.niso.org/credit-taxonomy/#table-1-credit-terms-and-urls
+ Choose one of the roles as listed in the controlled vocabulary. Note that for HealthDCAT-AP, the list of roles might be extended in the future. +Example: https://standards.iso.org/iso/19115/resources/Codelists/gml/CI_RoleCode.xml#processor + +Next to the CI_RoleCode, we also propose to use the CRediT Taxonomy to specify roles of contributors.

Controlled vocabulary
The value for the property must be selected from the specified vocabulary or list.

https://standards.iso.org/iso/19115/resources/Codelists/gml/CI_RoleCode.xml
https://jats4r.niso.org/credit-taxonomy/#table-1-credit-terms-and-urls
\ No newline at end of file diff --git a/src/property/properties-catalogue.html b/src/property/properties-catalogue.html index 1b054fa..3cd93dd 100644 --- a/src/property/properties-catalogue.html +++ b/src/property/properties-catalogue.html @@ -22,7 +22,7 @@ catalog A catalog that is listed in the catalog. dcat:catalog - dcat:Catalog (IRI) + dcat:Catalog 0..n For certain research projects, multiple catalogs may need to be organized in a nested manner. This property serves to connect the different catalogs with each other. @@ -32,7 +32,8 @@ dcat:contactPoint vcard:Kind 1 - This property points to a contact point (department or person) that can answer questions about the catalogue. Details on how to describe these are provided under class vcard:Kind.\nWhenever possible, use a general contact information (for example from a department) instead of contact information of an individual. + This property points to a contact point that can answer questions about the dataset. Details on how to describe these are provided under class vcard:Kind. +Whenever possible, use a general contact information (for example from a department) instead of contact information of an individual. creator @@ -40,14 +41,16 @@ dct:creator foaf:Agent 0..n - Note that the Health-RI model diverges from DCAT-AP NL here, which reduces the maximum number of creators to 1. The Health-RI model allows specification of multiple creators of a catalogue. + The creator is the entity responsible for making the resource. According to Dutch databank and copyright law, this is in most cases the organisation / employer bearing investment risk, instead of an individual (e.g. individual researcher). Therefore, in many cases, this might be the same Agent as the dct:publisher, being the organisation (not a department or subdivision of the organisation) where the catalogue was created. +In case there are multiple (collaborating) organisation involved in data creation, all of them can be stated as dct:creator, as the model allows more than one creator. +Note that the Health-RI model diverges from DCAT-AP NL here, which reduces the maximum number of creators to 1. The Health-RI model allows the specification of multiple creators of a catalogue. dataset A dataset that is listed in the catalog. dcat:dataset dcat:Dataset - 0..n + 1..n Each catalog contains one or more datasets. This property serves to link datasets to a catalogue. Therefore, a dataset is always contained inside a catalogue. @@ -70,9 +73,10 @@ has part A related resource that is included either physically or logically in the described resource. dct:hasPart - dcat:Catalog (IRI) + dcat:Catalog 0..n - Use this property to establish another catalogue in this catalogue.\nNote that deeply nested structures should be avoided, and can currently not be displayed in the National Health Data Catalogue. + Use this property to establish another catalogue in this catalogue. +Note that deeply nested structures should be avoided, and can currently not be displayed in the National Health Data Catalogue. home page @@ -88,7 +92,8 @@ dct:language dct:LinguisticSystem (IRI) 0..n - The value of this property must be an IRI from the provided controlled vocabulary.\nFor example: http://publications.europa.eu/resource/authority/language/NLD

Controlled vocabulary
The value for the property must be selected from the specified vocabulary or list.

http://publications.europa.eu/resource/authority/language
+ The value of this property must be an IRI from the provided controlled vocabulary. +For example: http://publications.europa.eu/resource/authority/language/NLD

Controlled vocabulary
The value for the property must be selected from the specified vocabulary or list.

http://publications.europa.eu/resource/authority/language
licence @@ -134,7 +139,7 @@ service A service that is listed in the catalog. dcat:service - dcat:DataService (IRI) + dcat:DataService 0..n Some datasets may have real-time Data Services (e.g., Beacon API counting individuals). IT teams should define the relationship between the catalog and the Data Service via this property. While crucial for interoperability, this property is not relevant for end-users to collect. @@ -150,9 +155,9 @@ themes A main category of the resource. A resource can have multiple themes. dcat:themeTaxonomy - skos:ConceptScheme (IRI) + skos:ConceptScheme 0..n - This property refers to a knowledge organisation system used to classify the Catalogue's Datasets. It must have at least the value NAL:data-theme as this is the mandatory controlled vocabulary for dcat:theme.

Controlled vocabulary
At least one of the provided values must come from the specified vocabulary (additional values from other sources may be included where relevant).

http://publications.europa.eu/resource/authority/data-theme
+ This property refers to a knowledge organisation system used to classify the Catalogue's Datasets. It must have at least the value NAL:data-theme as this is the mandatory controlled vocabulary for dcat:theme. title diff --git a/src/property/properties-checksum.html b/src/property/properties-checksum.html index d6bd142..f518070 100644 --- a/src/property/properties-checksum.html +++ b/src/property/properties-checksum.html @@ -22,7 +22,7 @@ checksum value The checksumValue property provides a lower case hexidecimal encoded digest value produced using a specific algorithm. spdx:checksumValue - rdfs:Literal + xsd:hexBinary 1 N.A. diff --git a/src/property/properties-dataservice.html b/src/property/properties-dataservice.html index 3d9975c..8eb988f 100644 --- a/src/property/properties-dataservice.html +++ b/src/property/properties-dataservice.html @@ -40,7 +40,8 @@ dcat:contactPoint vcard:Kind 1 - This property points to a contact point (department or person) that can answer questions about the data service. Details on how to describe these are provided under class vcard:Kind.\nWhenever possible, use a general contact information (for example from a department) instead of contact information of an individual. + This property points to a contact point that can answer questions about the dataset. Details on how to describe these are provided under class vcard:Kind. +Whenever possible, use a general contact information (for example from a department) instead of contact information of an individual. creator @@ -48,7 +49,9 @@ dct:creator foaf:Agent 0..n - Note that the Health-RI model diverges from DCAT-AP NL here, which reduces the maximum number of creators to 1. The Health-RI model allows specification of multiple creators of a data service. + The creator is the entity responsible for making the resource. According to Dutch databank and copyright law, this is in most cases the organisation / employer bearing investment risk, instead of an individual (e.g. individual researcher). Therefore, in many cases, this might be the same Agent as the dct:publisher, being the organisation (not a department or subdivision of the organisation) where the catalogue was created. +In case there are multiple (collaborating) organisation involved in data creation, all of them can be stated as dct:creator, as the model allows more than one creator. +Note that the Health-RI model diverges from DCAT-AP NL here, which reduces the maximum number of creators to 1. The Health-RI model allows the specification of multiple creators of a catalogue. rights @@ -166,7 +169,7 @@ serves dataset A collection of data that this data service can distribute. dcat:servesDataset - dcat:Dataset (IRI) + dcat:Dataset 0..n This property connects the Data Service class to its corresponding dataset(s), ensuring every data service links to at least one dcat:Dataset. While essential for metadata implementation teams on each node, it’s less relevant for researchers to collect. diff --git a/src/property/properties-dataset.html b/src/property/properties-dataset.html index 785805f..dca9ac8 100644 --- a/src/property/properties-dataset.html +++ b/src/property/properties-dataset.html @@ -16,13 +16,18 @@ dct:accessRights dct:RightsStatement (IRI) 1 - Information that indicates whether the Dataset is publicly accessible, has access restrictions or is not public. It is foreseen that one of the three options have to be used: public, restricted, non-public.\n    Open Data (Public): The dataset is available under general open data rules, such as those covered by the High Value Datasets Implementing Regulation.\n    Protected Data (Restricted): The dataset contains protected data and is accessible only under specific conditions, as outlined in regulations like the Data Governance Act.\n    Sensitive Data (Non public): The dataset includes resources that may contain sensitive or personal information, falling under regulations such as the EHDS Regulation.\n\nSince most data contain personal information, these datasets will need to take the value 'non-public' for the access rights property.

Controlled vocabulary
The value for the property must be selected from the specified vocabulary or list.

http://publications.europa.eu/resource/authority/access-right
+ Information that indicates whether the Dataset is publicly accessible, has access restrictions or is not public. It is foreseen that one of the three options have to be used: public, restricted, non-public. +    Open Data (Public): The dataset is available under general open data rules, such as those covered by the High Value Datasets Implementing Regulation. +    Protected Data (Restricted): The dataset contains protected data and is accessible only under specific conditions, as outlined in regulations like the Data Governance Act. +    Sensitive Data (Non public): The dataset includes resources that may contain sensitive or personal information, falling under regulations such as the EHDS Regulation. + +Since most data contain personal information, these datasets will need to take the value 'non-public' for the access rights property.

Controlled vocabulary
The value for the property must be selected from the specified vocabulary or list.

http://publications.europa.eu/resource/authority/access-right
analytics An analytics distribution of the dataset. healthdcatap:analytics - dcat:Distribution (IRI) + dcat:Distribution 0..n Publishers are encouraged to provide URLs pointing to document repositories where users can access or request associated resources such as technical reports of the dataset, quality measurements, usability indicators,... Note that HealthDCAT-AP mentions also API endpoints or analytics services, but these would not be Distriutions but rather DatasetServices. @@ -32,7 +37,11 @@ dcatap:applicableLegislation eli:LegalResource (IRI) 1..n - The ELI of the EHDS was published in March 2025 and can now be included as the applicable legislation mandating that the dataset has to be made public.\nFor health datasets, the value must include the ELI of the EHDS Regulation (http://data.europa.eu/eli/reg/2025/327/oj).\nAs multiple legislations may apply to the resource the maximum cardinality is not limited.\n\nWhile the applicable legislation indicates which legislation mandates the publication of the dataset, the legal basis property (also in Datasets) described the legal basis for initial collection and processing of (personal) data. + The ELI of the EHDS was published in March 2025 and can now be included as the applicable legislation mandating that the dataset has to be made public. +For health datasets, the value must include the ELI of the EHDS Regulation (http://data.europa.eu/eli/reg/2025/327/oj). +As multiple legislations may apply to the resource the maximum cardinality is not limited. + +While the applicable legislation indicates which legislation mandates the publication of the dataset, the legal basis property (also in Datasets) described the legal basis for initial collection and processing of (personal) data. code values @@ -64,7 +73,8 @@ dcat:contactPoint vcard:Kind 1 - This property points to a contact point (department or person) that can answer questions about the dataset. Details on how to describe these are provided under class vcard:Kind.\nWhenever possible, use a general contact information (for example from a department) instead of contact information of an individual. + This property points to a contact point that can answer questions about the dataset. Details on how to describe these are provided under class vcard:Kind. +Whenever possible, use a general contact information (for example from a department) instead of contact information of an individual. creator @@ -72,7 +82,9 @@ dct:creator foaf:Agent 1..n - This property points to a person (known as Agent) responsible for generating the dataset. In most cases, this should be the project’s Principal Investigator, provided they consent to being listed in the catalogue. If not, the associated department or institute may be specified instead. + The creator (of the dataset) is the entity responsible for making the resource. According to Dutch databank and copyright law, this is in most cases the organisation / employer bearing investment risk, instead of an individual (e.g. individual researcher). Therefore, in many cases, this might be the same Agent as the dct:publisher, being the organisation (not a department or subdivision of the organisation) where the dataset was created. +In case there are multiple (collaborating) organisation involved in data creation, all of them can be stated as dct:creator, as the model allows more than one creator. +In case you wish to credit other contributors to the dataset, you can use the prov:qualifiedAttribution property. This could be useful if you wish to indicate, for example, the funding organisation(s), collaborating organosation(s) or name specific individuals (e.g., principal investigator) involved in creation or managing of the dataset. description @@ -86,7 +98,7 @@ distribution An available Distribution for the Dataset. dcat:distribution - dcat:Distribution (IRI) + dcat:Distribution 0..n Metadata element used as a key link to the class Distribution. @@ -104,7 +116,8 @@ dct:accrualPeriodicity skos:Concept (IRI) 0..1 - The value of this property should be the IRI from the listed controlled vocabulary indicating the frequency at which the dataset is updated.\nFor example: http://publications.europa.eu/resource/authority/frequency/WEEKLY

Controlled vocabulary
The value for the property must be selected from the specified vocabulary or list.

http://publications.europa.eu/resource/authority/frequency
+ The value of this property should be the IRI from the listed controlled vocabulary indicating the frequency at which the dataset is updated. +For example: http://publications.europa.eu/resource/authority/frequency/WEEKLY

Controlled vocabulary
The value for the property must be selected from the specified vocabulary or list.

http://publications.europa.eu/resource/authority/frequency
geographical coverage @@ -118,7 +131,7 @@ has version This resource has a more specific, versioned resource. dcat:hasVersion - dcat:Dataset (IRI) + dcat:Dataset 0..n Indicate the dataset which is the other version of the current dataset. @@ -136,13 +149,14 @@ dct:identifier rdfs:Literal 1 - Current status: Health-RI is currently working on a strategy for persistant identifiers for, among other things, datasets. Until a solid solution has been found, we propose the following temporary solution:\nIf your data is published in a repository, fill in with the provided DOI (Example: https://doi.org/10.34894/ZLOYOJ). If not, use the identifier of the dataset as generated in the FAIR data point (FDP). Ensure that metadata is updated if your situation changes. + Current status: Health-RI is currently working on a strategy for persistant identifiers for, among other things, datasets. Until a solid solution has been found, we propose the following temporary solution: +If your data is published in a repository, fill in with the provided DOI (Example: https://doi.org/10.34894/ZLOYOJ). If not, use the identifier of the dataset as generated in the FAIR data point (FDP). Ensure that metadata is updated if your situation changes. in series A dataset series of which the dataset is part. dcat:inSeries - dcat:DatasetSeries (IRI) + dcat:DatasetSeries 0..n This property points to which Dataset Series the Dataset is part of. @@ -152,7 +166,8 @@ dct:isReferencedBy rdfs:Resource (IRI) 0..n - The value of this property is the IRI of the doi to the publication or other related resource.\nFor example: https://doi.org/10.1186/s13690-021-00709-x + The value of this property is the IRI of the doi to the publication or other related resource. +For example: https://doi.org/10.1186/s13690-021-00709-x keyword @@ -174,15 +189,19 @@ legal basis Indicates use or applicability of a Legal Basis. dpv:hasLegalBasis - dpv:LegalBasis (IRI) + dpv:LegalBasis 0..n - The legal basis can be provided as a value from the dpv taxonomy (see Controlled vocabulary column).\n\nWhile the applicable legislation indicates which legislation mandates the publication of the dataset, the legal basis property described the legal basis for initial collection and processing of (personal) data.\n\nExample value for this property could be: dpv:Consent

Controlled vocabulary
The use of the specified vocabulary is optional, but recommended when applicable.

https://w3c.github.io/dpv/2.0/dpv/modules/legal_basis.html#vocab-legal-basis
+ The legal basis can be provided as a value from the dpv taxonomy (see Controlled vocabulary column). + +While the applicable legislation indicates which legislation mandates the publication of the dataset, the legal basis property described the legal basis for initial collection and processing of (personal) data. + +Example value for this property could be: dpv:Consent

Controlled vocabulary
The use of the specified vocabulary is optional, but recommended when applicable.

https://w3c.github.io/dpv/2.0/dpv/modules/legal_basis.html#vocab-legal-basis
maximum typical age Maximum typical age of the population within the dataset healthdcatap:maxTypicalAge - xsd:nonNegativeInteger + xsd:non NegativeInteger 0..1 The approximate maximum age of subjects in the dataset, if applicable. Approximate age is given to protect potentially sensitive information of subjects in the dataset. @@ -190,7 +209,7 @@ minimum typical age Minimum typical age of the population within the dataset healthdcatap:minTypicalAge - xsd:nonNegativeInteger + xsd:non NegativeInteger 0..1 The approximate minimum age of subjects in the dataset, if applicable. Approximate age is given to protect potentially sensitive information of subjects in the dataset. @@ -206,7 +225,7 @@ number of records Size of the dataset in terms of the number of records healthdcatap:numberOfRecords - xsd:nonNegativeInteger + xsd:NonNegativeInteger 0..1 Number of records inside a Dataset. @@ -214,7 +233,7 @@ number of unique infividuals Number of records for unique individuals. healthdcatap:numberOfUniqueIndividuals - xsd:nonNegativeInteger + xsd:NonNegativeInteger 0..1 This property is not mandatory, since not all datasets might include data from individuals. @@ -230,9 +249,10 @@ personal data Indicates association with Personal Data. dpv:hasPersonalData - dpv:PersonalData (IRI) + dpv:PersonalData 0..n - The different types of personal information that are collected in the dataset can be indicated with this property. Values can be picked from the dpv taxonomy (see controlled vocabulary column).\nFor example: dpv-pd:Gender

Controlled vocabulary
The value for the property must be selected from the specified vocabulary or list.

https://w3c.github.io/dpv/2.0/pd/
+ The different types of personal information that are collected in the dataset can be indicated with this property. Values can be picked from the dpv taxonomy (see controlled vocabulary column). +For example: dpv-pd:Gender

Controlled vocabulary
The value for the property must be selected from the specified vocabulary or list.

https://w3c.github.io/dpv/2.0/pd/
population coverage @@ -254,9 +274,10 @@ purpose Indicates association with Purpose. dpv:hasPurpose - dpv:Purpose (IRI) + dpv:Purpose 0..n - One (or many) category or sub-category of the purposes can be chosen from the taxonomy provided by dpv (see controlled vocabulary column).\nExample value could be: dpv:ResearchAndDevelopment.

Controlled vocabulary
The use of the specified vocabulary is optional, but recommended when applicable.

https://w3c.github.io/dpv/2.1/dpv/#vocab-purposes
+ One (or many) category or sub-category of the purposes can be chosen from the taxonomy provided by dpv (see controlled vocabulary column). +Example value could be: dpv:ResearchAndDevelopment.

Controlled vocabulary
The use of the specified vocabulary is optional, but recommended when applicable.

https://w3c.github.io/dpv/2.1/dpv/#vocab-purposes
qualified attribution @@ -264,7 +285,12 @@ prov:qualifiedAttribution prov:Attribution 0..n - This property makes use of another small class (prov:Attribution). There, you can choose one of the roles as listed in the controlled vocabulary and link that to a specific Agent (expressed with foaf:Agent). Note that for HealthDCAT-AP, the list of roles might be extended in the future.\nExample: https://standards.iso.org/iso/19115/resources/Codelists/gml/CI_RoleCode.xml#processor\n\nUse this property if you would like to indicate the funder of the (research project that resulted in creation of the) dataset.\nThe value for role then becomes: https://standards.iso.org/iso/19115/resources/Codelists/gml/CI_RoleCode.xml#funder + This property makes use of another small class (prov:Attribution). There, you can choose one of the roles as listed in the controlled vocabulary and link that to a specific Agent (expressed with foaf:Agent). +Repeat this property if you wish to specify multiple roles for the same agent. +Refer to the Attribution class for more information how to fill this. + +Use this property if you would like to indicate the funder of the (research project that resulted in creation of the) dataset. +The value for role in the Attribution class then becomes: https://standards.iso.org/iso/19115/resources/Codelists/gml/CI_RoleCode.xml#funder qualified relation @@ -302,7 +328,7 @@ sample Links to a sample of an Asset (which is itself an Asset). adms:sample - dcat:Distribution (IRI) + dcat:Distribution 0..n This property makes use of the dcat:Distribution class to describe a sample distribution of the dataset, which can be anonymized or synthetic data, or the data dictionary provided in CSVW format. This is currently further developed by the TEHDAS2 program. More information can be found here: https://healthdcat-ap.github.io/#sample-distribution @@ -310,7 +336,7 @@ source A related resource from which the described resource is derived. dct:source - dcat:Dataset (IRI) + dcat:Dataset 0..n Indicate the dataset on which this described dataset is based. @@ -320,7 +346,8 @@ adms:status skos:Concept (IRI) 0..1 - This property makes use of a controlled vocabulary to indicate the status of the described dataset.\nFor example: http://publications.europa.eu/resource/authority/dataset-status/COMPLETED

Controlled vocabulary
The value for the property must be selected from the specified vocabulary or list.

https://publications.europa.eu/resource/authority/dataset-status
+ This property makes use of a controlled vocabulary to indicate the status of the described dataset. +For example: http://publications.europa.eu/resource/authority/dataset-status/COMPLETED

Controlled vocabulary
The value for the property must be selected from the specified vocabulary or list.

https://publications.europa.eu/resource/authority/dataset-status
temporal coverage @@ -382,7 +409,7 @@ was generated by Generation is the completion of production of a new entity by an activity. This entity did not exist before generation and becomes available for usage after this generation. prov:wasGeneratedBy - prov:Activity (IRI) + prov:Activity 0..n N.A. diff --git a/src/property/properties-datasetseries.html b/src/property/properties-datasetseries.html index 8fc1a12..f615fbf 100644 --- a/src/property/properties-datasetseries.html +++ b/src/property/properties-datasetseries.html @@ -24,7 +24,8 @@ dcat:contactPoint vcard:Kind 1..n - This property points to a contact point (department or person) that can answer questions about the dataset series. Details on how to describe these are provided under class vcard:Kind.\nWhenever possible, use a general contact information (for example from a department) instead of contact information of an individual. + This property points to a contact point that can answer questions about the dataset. Details on how to describe these are provided under class vcard:Kind. +Whenever possible, use a general contact information (for example from a department) instead of contact information of an individual. description diff --git a/src/property/properties-distribution.html b/src/property/properties-distribution.html index 58debe1..ce11be6 100644 --- a/src/property/properties-distribution.html +++ b/src/property/properties-distribution.html @@ -96,7 +96,8 @@ dct:language dct:LinguisticSystem (IRI) 0..n - Indicates the natural language used in the Distribution, indicated with a value from the EU controlled vocabulary. Not all distributions might have a language, for example imaging data.\nNote that here the Health-RI model diverges from DCAT-AP NL, which allows maximum of 1 languages per Distribution. The Health-RI model allows multiple languages in the same Distribution.

Controlled vocabulary
The value for the property must be selected from the specified vocabulary or list.

http://publications.europa.eu/resource/authority/language
+ Indicates the natural language used in the Distribution, indicated with a value from the EU controlled vocabulary. Not all distributions might have a language, for example imaging data. +Note that here the Health-RI model diverges from DCAT-AP NL, which allows maximum of 1 languages per Distribution. The Health-RI model allows multiple languages in the same Distribution.

Controlled vocabulary
The value for the property must be selected from the specified vocabulary or list.

http://publications.europa.eu/resource/authority/language
license @@ -120,7 +121,9 @@ dcat:mediaType dct:MediaType (IRI) 0..1 - Use the specified vocabularies, prioritizing IANA media types whenever possible. If unavailable, consider other ontologies, such as ZonMw generic terms, to descibe the format.\nExample: https://www.iana.org/assignments/media-types/text/csv (for csv)\nIf IANA media types do not sufficiently describe the format, use "format" to describe it in more detail.

Controlled vocabulary
The value for the property must be selected from the specified vocabulary or list.

http://www.iana.org/assignments/media-types/media-types.xhtml
+ Use the specified vocabularies, prioritizing IANA media types whenever possible. If unavailable, consider other ontologies, such as ZonMw generic terms, to descibe the format. +Example: https://www.iana.org/assignments/media-types/text/csv (for csv) +If IANA media types do not sufficiently describe the format, use "format" to describe it in more detail.

Controlled vocabulary
The value for the property must be selected from the specified vocabulary or list.

http://www.iana.org/assignments/media-types/media-types.xhtml
modification date @@ -160,7 +163,9 @@ dct:rights dct:RightsStatement (IRI) 1 - A statement that concerns all rights not addressed in fields License or Access rights. In case of not open data (as specified in the dct:licence property), further agreements regarding data reuse (eg. Data Transfer Agreement, DTA,) should be stated in this property.\nThe rights statement should be a free-text statement placed at an web-accessible location such that the value of this property is the IRI pointing to that statement.\nCurrent status: This recommendation on how to state data transfer/reuse conditions will be pilotted in 2025. + A statement that concerns all rights not addressed in fields License or Access rights. In case of not open data (as specified in the dct:licence property), further agreements regarding data reuse (eg. Data Transfer Agreement, DTA,) should be stated in this property. +The rights statement should be a free-text statement placed at an web-accessible location such that the value of this property is the IRI pointing to that statement. +Current status: This recommendation on how to state data transfer/reuse conditions will be pilotted in 2025. status @@ -168,7 +173,7 @@ adms:status skos:Concept (IRI) 0..1 - It MUST take one of the values Completed, Deprecated, Under Development, Withdrawn from the provided controlled vocabulary.

Controlled vocabulary
The value for the property must be selected from the specified vocabulary or list.

https://publications.europa.eu/resource/authority/distribution-status
+ It MUST take one of the values Completed, Deprecated, Under Development, Withdrawn from the provided controlled vocabulary.

Controlled vocabulary
The value for the property must be selected from the specified vocabulary or list.

http://publications.europa.eu/resource/authority/distribution-status
temporal resolution @@ -183,7 +188,7 @@ A name given to the resource. dct:title rdfs:Literal - 1..n + 0..n A title given to the distribution. e.g., Data Access Request of Healthy Brain study diff --git a/src/property/properties-kind.html b/src/property/properties-kind.html index 3341bd1..0e1302d 100644 --- a/src/property/properties-kind.html +++ b/src/property/properties-kind.html @@ -24,7 +24,11 @@ vcard:hasEmail rdfs:Resource  (IRI) 1 - When naming a contact point this information needs to be further specified with additional information, i.e., an email address. This email address does not need to be a direct contact to the person responsible for the management of the data, it could be a generic information email.\nThe email address has to be provided starting with mailto: prefix.\nFor example: mailto:info@example.com / mailto: jane.doe@example.com + It is preferred to provide a general email address of the appropriate institution or department instead of a personal email address, even if an individual is described with this instance of vcard:Kind. +This protects their privacy and enables contact about the resource even after the individual has left the institution. + +The email address has to be provided starting with mailto: prefix. +For example: mailto:info@example.com formatted name diff --git a/src/property/properties-qualitycertificate.html b/src/property/properties-qualitycertificate.html index bbd3ff8..3f8e5a1 100644 --- a/src/property/properties-qualitycertificate.html +++ b/src/property/properties-qualitycertificate.html @@ -16,7 +16,8 @@ oa:hasTarget rdfs:Resource (IRI) 0..1 - This property has to be filled with the same value as the dct:identifier of the dataset described, in order to link the quality certificate to that dataset.\nSee also example in HealthDCAT-AP: https://healthdcat-ap.github.io/#dqvhasqualityannotation + This property has to be filled with the same value as the dct:identifier of the dataset described, in order to link the quality certificate to that dataset. +See also example in HealthDCAT-AP: https://healthdcat-ap.github.io/#dqvhasqualityannotation body diff --git a/src/property/properties-relationship.html b/src/property/properties-relationship.html index 506af6d..39947f2 100644 --- a/src/property/properties-relationship.html +++ b/src/property/properties-relationship.html @@ -16,7 +16,8 @@ dcat:hadRole skos:Concept (IRI) 1..n - Specify, ideally with a value from the linked controlled vocabulary, the nature of the relationship between the linked resources.\nExample: http://www.iana.org/assignments/relation/related

Controlled vocabulary
The value for the property must be selected from the specified vocabulary or list.

https://www.iana.org/assignments/link-relations/link-relations.xhtml
https://standards.iso.org/iso/19115/resources/Codelists/gml/DS_AssociationTypeCode.xml
+ Specify, ideally with a value from the linked controlled vocabulary, the nature of the relationship between the linked resources. +Example: http://www.iana.org/assignments/relation/related

Controlled vocabulary
The value for the property must be selected from the specified vocabulary or list.

https://www.iana.org/assignments/link-relations/link-relations.xhtml
https://standards.iso.org/iso/19115/resources/Codelists/gml/DS_AssociationTypeCode.xml
relation diff --git a/src/python/Excel_To_Html.py b/src/python/Excel_To_Html.py index 087661f..b19a378 100644 --- a/src/python/Excel_To_Html.py +++ b/src/python/Excel_To_Html.py @@ -6,7 +6,7 @@ from urllib.parse import urlparse, urlunparse -EXCEL_FILE_PATH = "../excel/HealthRI_v2.0.2.xlsx" +EXCEL_FILE_PATH = "../excel/HealthRI_v2.0.3.xlsx" OUTPUT_PATH = Path("../property") LINKS_FILE = Path(__file__).parent / "links.json"