Skip to content

Commit

Permalink
Applying changes from commit 717b52ba8c566d2e47058c9f54fda821cad2886f
Browse files Browse the repository at this point in the history
  • Loading branch information
Circle CI Builder committed Feb 2, 2024
1 parent 13708ee commit 5d49bd1
Show file tree
Hide file tree
Showing 18 changed files with 466 additions and 446 deletions.
30 changes: 20 additions & 10 deletions DCAT-AP/releases/3.0.0/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -211,7 +211,17 @@
"href": "https://w3id.org/",
"title" : "Permanent Identifiers for the Web",
"publisher" : "W3C Permanent Identifier Community Group"
}
},
"ODRL" : {
"href": "https://www.w3.org/ns/odrl/2/",
"title" : "The Open Digital Rights Language Ontology Version 2.2",
"publisher" : "W3C POE Working Group"
},
"FAIR" : {
"href": "https://www.openaire.eu/how-to-make-your-data-fair",
"title" : "How to make your data FAIR",
"publisher" : "OpenAire"
}
}
};

Expand Down Expand Up @@ -2939,7 +2949,7 @@ <h3 id="DataService">
<td property="skos:scopeNote">
The standards referred here SHOULD describe the Data Service and not the data it serves. The latter is provided by the dataset with which this Data Service is connected.

For instance the data service adheres to the OGC WFS API standard, while the associated dataset adheres to the INSPIRE Address data model.
For instance the data service adheres to the OGC WFS API standard, while the associated dataset adheres to the <a href="https://knowledge-base.inspire.ec.europa.eu/index_en">INSPIRE</a> Address data model.
</td>
<!--
<td>
Expand Down Expand Up @@ -6862,7 +6872,7 @@ <h3 id="Distribution">
0..1
</td>
<td property="rdfs:comment">
The policy expressing the rights associated with the distribution if using the ODRL vocabulary.
The policy expressing the rights associated with the distribution if using the [[ODRL]] vocabulary.
</td>
<td property="skos:scopeNote">

Expand Down Expand Up @@ -8994,7 +9004,7 @@ <h3 id="Literal">
Definition
</dt>
<dd>
A literal value such as a string or integer; Literals may be typed, e.g. as a date according to xsd:date. Literals that contain human-readable text have an optional language tag as defined by BCP 4715.
A literal value such as a string or integer; Literals may be typed, e.g. as a date according to xsd:date. Literals that contain human-readable text have an optional language tag as defined by BCP 47 [[rfc5646]].
</dd>


Expand Down Expand Up @@ -9706,7 +9716,7 @@ <h2>
</div>

</td><td>
rdfs:Literal encoded using the relevant ISO [[8601]] Date and Time compliant string and typed using the appropriate XML Schema datatype (xsd:gYear, xsd:gYearMonth, xsd:date, or xsd:dateTime).
rdfs:Literal encoded using the relevant [[ISO8601]] Date and Time compliant string and typed using the appropriate XML Schema datatype (xsd:gYear, xsd:gYearMonth, xsd:date, or xsd:dateTime).
</td></tr>
<tr><td>
<a href="https://github.com/SEMICeu/DCAT-AP/issues/new?title=Issue%20for%20TimeInstant&body=Explain%20your%20issue"}}>
Expand Down Expand Up @@ -9913,8 +9923,8 @@ <h2>Legal information</h2>

Providing correct and sufficient legal information is important to create trust by candidate reusers.
Without explicit legal information there is a risk involved in the reuse of data, because one has no way of knowing what is allowed.
While in the past legislation and initiatives such as Findable, Accessible, Interoperable and Reusable (FAIR) data stress the importance of this information,
recent legislations, such as the High Value Datasets regulation, have become more demanding by imposing a minimum level of reuse.
While in the past legislation and initiatives such as Findable, Accessible, Interoperable and Reusable [[FAIR]] data stress the importance of this information,
recent legislations, such as the <a href="https://eur-lex.europa.eu/eli/reg_impl/2023/138/oj">High Value Datasets regulation</a>, have become more demanding by imposing a minimum level of reuse.
As a general principle, it is recommended that publishers consult their legal services to provide the appropriate values.

<p></p>
Expand All @@ -9932,7 +9942,7 @@ <h2>Legal information</h2>
<p></p>
This creates a natural tendency to use licences (or rights) which have a wider adoption than national legislation.
Unless restricted by national legislation, implementers are encouraged for that reason to use widely recognised licences such as Creative Commons licences.
In particular it is advised for FAIR data to consider CC BY 4.0 (the minimum limit set by the HVD implementing regulation) or more permissive such as licences CC Zero.
In particular it is advised for [[FAIR]] data to consider CC BY 4.0 (the minimum limit set by the HVD implementing regulation) or more permissive such as licences CC Zero.

<p></p>

Expand Down Expand Up @@ -9980,10 +9990,10 @@ <h2>Agent Roles</h2>
The first possible approach is based on the use of a predicate vocabulary that provides a set of properties that represent additional types of relationships between Datasets and Agents.
For example, properties could be defined, such as foo:owner, foo:curator or foo:responsibleParty, in addition to the use of existing well-known properties, such as dct:creator and dct:rightsHolder.
A possible source for such additional properties is the Roles Named Authority List maintained by the Publications Office of the EU.
Other domain-specific sources for additional properties are the INSPIRE Responsible Party roles , the Library of Congress’ MARC relators and DataCite’s contributor types.
Other domain-specific sources for additional properties are the <a href="https://knowledge-base.inspire.ec.europa.eu/index_en">INSPIRE</a> Responsible Party roles ,<a href="https://www.loc.gov/marc/relators/relaterm.html">the Library of Congress’ MARC relators</a> and <a href="https://support.datacite.org/docs/datacite-metadata-schema-v44-recommended-and-optional-properties#:~:text=Foo%20Data%20Center-,7.a%20contributorType,-Occurrence%3A%201">DataCite’s contributor types</a>.
To enable the use of such properties, they must be defined as RDF properties with URIs in a well-managed namespace.
</p><p>
A second approach is based on the use of W3C’s PROV ontology [[prov-o]] which provides a powerful mechanism to express a set of classes, properties, and restrictions that can be used to represent and interchange provenance information generated in different systems and under different contexts. In the context of work on GeoDCAT-AP, a PROV-conformant solution for expressing agent roles was agreed . This solution uses prov:qualifiedAttribution in combination with a dct:type assertion pointing to the code list for Responsible Party Role in the INSPIRE registry. To enable the use of such types, they must be defined with URIs in a well-managed namespace.
A second approach is based on the use of W3C’s PROV ontology [[prov-o]] which provides a powerful mechanism to express a set of classes, properties, and restrictions that can be used to represent and interchange provenance information generated in different systems and under different contexts. In the context of work on GeoDCAT-AP, a PROV-conformant solution for expressing agent roles was agreed . This solution uses prov:qualifiedAttribution in combination with a dct:type assertion pointing to the code list for Responsible Party Role in the <a href="https://knowledge-base.inspire.ec.europa.eu/index_en">INSPIRE</a> registry. To enable the use of such types, they must be defined with URIs in a well-managed namespace.
</p><p>
Based on the experience gained with the use of domain-specific extensions for additional ‘agent roles’ in the exchange of information about Datasets and on the requests of implementors and stakeholders, the DCAT Application Profile release 2.0.0 is extended with additional roles as proposed by DCAT Version 2 [[vocab-dcat-2]] that have proven to be useful across domains. Precisely, properties <a href="#Dataset.creator">creator</a>, <a href="#Dataset.qualifiedattribution">qualified attribution</a> and <a href="#Dataset.qualifiedrelation">qualified relation</a> have been added to <a href="#Dataset">Dataset</a> class to further facilitate relationships between datasets and agents.
</p><p>
Expand Down
30 changes: 20 additions & 10 deletions DCAT-AP/releases/3.0.0/index_en.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -211,7 +211,17 @@
"href": "https://w3id.org/",
"title" : "Permanent Identifiers for the Web",
"publisher" : "W3C Permanent Identifier Community Group"
}
},
"ODRL" : {
"href": "https://www.w3.org/ns/odrl/2/",
"title" : "The Open Digital Rights Language Ontology Version 2.2",
"publisher" : "W3C POE Working Group"
},
"FAIR" : {
"href": "https://www.openaire.eu/how-to-make-your-data-fair",
"title" : "How to make your data FAIR",
"publisher" : "OpenAire"
}
}
};

Expand Down Expand Up @@ -2939,7 +2949,7 @@ <h3 id="DataService">
<td property="skos:scopeNote">
The standards referred here SHOULD describe the Data Service and not the data it serves. The latter is provided by the dataset with which this Data Service is connected.

For instance the data service adheres to the OGC WFS API standard, while the associated dataset adheres to the INSPIRE Address data model.
For instance the data service adheres to the OGC WFS API standard, while the associated dataset adheres to the <a href="https://knowledge-base.inspire.ec.europa.eu/index_en">INSPIRE</a> Address data model.
</td>
<!--
<td>
Expand Down Expand Up @@ -6862,7 +6872,7 @@ <h3 id="Distribution">
0..1
</td>
<td property="rdfs:comment">
The policy expressing the rights associated with the distribution if using the ODRL vocabulary.
The policy expressing the rights associated with the distribution if using the [[ODRL]] vocabulary.
</td>
<td property="skos:scopeNote">

Expand Down Expand Up @@ -8994,7 +9004,7 @@ <h3 id="Literal">
Definition
</dt>
<dd>
A literal value such as a string or integer; Literals may be typed, e.g. as a date according to xsd:date. Literals that contain human-readable text have an optional language tag as defined by BCP 4715.
A literal value such as a string or integer; Literals may be typed, e.g. as a date according to xsd:date. Literals that contain human-readable text have an optional language tag as defined by BCP 47 [[rfc5646]].
</dd>


Expand Down Expand Up @@ -9706,7 +9716,7 @@ <h2>
</div>

</td><td>
rdfs:Literal encoded using the relevant ISO [[8601]] Date and Time compliant string and typed using the appropriate XML Schema datatype (xsd:gYear, xsd:gYearMonth, xsd:date, or xsd:dateTime).
rdfs:Literal encoded using the relevant [[ISO8601]] Date and Time compliant string and typed using the appropriate XML Schema datatype (xsd:gYear, xsd:gYearMonth, xsd:date, or xsd:dateTime).
</td></tr>
<tr><td>
<a href="https://github.com/SEMICeu/DCAT-AP/issues/new?title=Issue%20for%20TimeInstant&body=Explain%20your%20issue"}}>
Expand Down Expand Up @@ -9913,8 +9923,8 @@ <h2>Legal information</h2>

Providing correct and sufficient legal information is important to create trust by candidate reusers.
Without explicit legal information there is a risk involved in the reuse of data, because one has no way of knowing what is allowed.
While in the past legislation and initiatives such as Findable, Accessible, Interoperable and Reusable (FAIR) data stress the importance of this information,
recent legislations, such as the High Value Datasets regulation, have become more demanding by imposing a minimum level of reuse.
While in the past legislation and initiatives such as Findable, Accessible, Interoperable and Reusable [[FAIR]] data stress the importance of this information,
recent legislations, such as the <a href="https://eur-lex.europa.eu/eli/reg_impl/2023/138/oj">High Value Datasets regulation</a>, have become more demanding by imposing a minimum level of reuse.
As a general principle, it is recommended that publishers consult their legal services to provide the appropriate values.

<p></p>
Expand All @@ -9932,7 +9942,7 @@ <h2>Legal information</h2>
<p></p>
This creates a natural tendency to use licences (or rights) which have a wider adoption than national legislation.
Unless restricted by national legislation, implementers are encouraged for that reason to use widely recognised licences such as Creative Commons licences.
In particular it is advised for FAIR data to consider CC BY 4.0 (the minimum limit set by the HVD implementing regulation) or more permissive such as licences CC Zero.
In particular it is advised for [[FAIR]] data to consider CC BY 4.0 (the minimum limit set by the HVD implementing regulation) or more permissive such as licences CC Zero.

<p></p>

Expand Down Expand Up @@ -9980,10 +9990,10 @@ <h2>Agent Roles</h2>
The first possible approach is based on the use of a predicate vocabulary that provides a set of properties that represent additional types of relationships between Datasets and Agents.
For example, properties could be defined, such as foo:owner, foo:curator or foo:responsibleParty, in addition to the use of existing well-known properties, such as dct:creator and dct:rightsHolder.
A possible source for such additional properties is the Roles Named Authority List maintained by the Publications Office of the EU.
Other domain-specific sources for additional properties are the INSPIRE Responsible Party roles , the Library of Congress’ MARC relators and DataCite’s contributor types.
Other domain-specific sources for additional properties are the <a href="https://knowledge-base.inspire.ec.europa.eu/index_en">INSPIRE</a> Responsible Party roles ,<a href="https://www.loc.gov/marc/relators/relaterm.html">the Library of Congress’ MARC relators</a> and <a href="https://support.datacite.org/docs/datacite-metadata-schema-v44-recommended-and-optional-properties#:~:text=Foo%20Data%20Center-,7.a%20contributorType,-Occurrence%3A%201">DataCite’s contributor types</a>.
To enable the use of such properties, they must be defined as RDF properties with URIs in a well-managed namespace.
</p><p>
A second approach is based on the use of W3C’s PROV ontology [[prov-o]] which provides a powerful mechanism to express a set of classes, properties, and restrictions that can be used to represent and interchange provenance information generated in different systems and under different contexts. In the context of work on GeoDCAT-AP, a PROV-conformant solution for expressing agent roles was agreed . This solution uses prov:qualifiedAttribution in combination with a dct:type assertion pointing to the code list for Responsible Party Role in the INSPIRE registry. To enable the use of such types, they must be defined with URIs in a well-managed namespace.
A second approach is based on the use of W3C’s PROV ontology [[prov-o]] which provides a powerful mechanism to express a set of classes, properties, and restrictions that can be used to represent and interchange provenance information generated in different systems and under different contexts. In the context of work on GeoDCAT-AP, a PROV-conformant solution for expressing agent roles was agreed . This solution uses prov:qualifiedAttribution in combination with a dct:type assertion pointing to the code list for Responsible Party Role in the <a href="https://knowledge-base.inspire.ec.europa.eu/index_en">INSPIRE</a> registry. To enable the use of such types, they must be defined with URIs in a well-managed namespace.
</p><p>
Based on the experience gained with the use of domain-specific extensions for additional ‘agent roles’ in the exchange of information about Datasets and on the requests of implementors and stakeholders, the DCAT Application Profile release 2.0.0 is extended with additional roles as proposed by DCAT Version 2 [[vocab-dcat-2]] that have proven to be useful across domains. Precisely, properties <a href="#Dataset.creator">creator</a>, <a href="#Dataset.qualifiedattribution">qualified attribution</a> and <a href="#Dataset.qualifiedrelation">qualified relation</a> have been added to <a href="#Dataset">Dataset</a> class to further facilitate relationships between datasets and agents.
</p><p>
Expand Down
4 changes: 2 additions & 2 deletions DCAT-AP/releases/3.0.0/shacl/dcat-ap-SHACL.jsonld
View file
Original file line number Diff line number Diff line change
Expand Up @@ -1895,7 +1895,7 @@
"@id": "https://semiceu.github.io/DCAT-AP/releases/3.0.0#dcat:DistributionShape/36b68d0f06c0eacbbddd0d2891379c6d005dc861",
"rdfs:seeAlso": "https://semiceu.github.io/DCAT-AP/releases/3.0.0#Distribution.haspolicy",
"sh:description": {
"en": "The policy expressing the rights associated with the distribution if using the ODRL vocabulary."
"en": "The policy expressing the rights associated with the distribution if using the [[ODRL]] vocabulary."
},
"sh:maxCount": "1",
"sh:name": {
Expand Down Expand Up @@ -2040,7 +2040,7 @@
"rdfs:seeAlso": "https://semiceu.github.io/DCAT-AP/releases/3.0.0#Distribution.haspolicy",
"sh:class": "http://www.w3.org/ns/odrl/2/Policy",
"sh:description": {
"en": "The policy expressing the rights associated with the distribution if using the ODRL vocabulary."
"en": "The policy expressing the rights associated with the distribution if using the [[ODRL]] vocabulary."
},
"sh:name": {
"en": "has policy"
Expand Down
4 changes: 2 additions & 2 deletions DCAT-AP/releases/3.0.0/shacl/dcat-ap-SHACL.ttl
View file
Original file line number Diff line number Diff line change
Expand Up @@ -891,7 +891,7 @@
shacl:path <http://www.w3.org/ns/adms#status> .

<https://semiceu.github.io/DCAT-AP/releases/3.0.0#dcat:DistributionShape/36b68d0f06c0eacbbddd0d2891379c6d005dc861> rdfs:seeAlso "https://semiceu.github.io/DCAT-AP/releases/3.0.0#Distribution.haspolicy";
shacl:description "The policy expressing the rights associated with the distribution if using the ODRL vocabulary."@en;
shacl:description "The policy expressing the rights associated with the distribution if using the [[ODRL]] vocabulary."@en;
shacl:maxCount 1;
shacl:name "has policy"@en;
shacl:path <http://www.w3.org/ns/odrl/2/hasPolicy> .
Expand Down Expand Up @@ -964,7 +964,7 @@

<https://semiceu.github.io/DCAT-AP/releases/3.0.0#dcat:DistributionShape/8c1e0d1ac55cc7da56ed33785c09a2980899a997> rdfs:seeAlso "https://semiceu.github.io/DCAT-AP/releases/3.0.0#Distribution.haspolicy";
shacl:class <http://www.w3.org/ns/odrl/2/Policy>;
shacl:description "The policy expressing the rights associated with the distribution if using the ODRL vocabulary."@en;
shacl:description "The policy expressing the rights associated with the distribution if using the [[ODRL]] vocabulary."@en;
shacl:name "has policy"@en;
shacl:path <http://www.w3.org/ns/odrl/2/hasPolicy> .

Expand Down
4 changes: 2 additions & 2 deletions DCAT-AP/releases/3.0.0/shacl/dcat-ap-SHACL_en.jsonld
View file
Original file line number Diff line number Diff line change
Expand Up @@ -1895,7 +1895,7 @@
"@id": "https://semiceu.github.io/DCAT-AP/releases/3.0.0#dcat:DistributionShape/36b68d0f06c0eacbbddd0d2891379c6d005dc861",
"rdfs:seeAlso": "https://semiceu.github.io/DCAT-AP/releases/3.0.0#Distribution.haspolicy",
"sh:description": {
"en": "The policy expressing the rights associated with the distribution if using the ODRL vocabulary."
"en": "The policy expressing the rights associated with the distribution if using the [[ODRL]] vocabulary."
},
"sh:maxCount": "1",
"sh:name": {
Expand Down Expand Up @@ -2040,7 +2040,7 @@
"rdfs:seeAlso": "https://semiceu.github.io/DCAT-AP/releases/3.0.0#Distribution.haspolicy",
"sh:class": "http://www.w3.org/ns/odrl/2/Policy",
"sh:description": {
"en": "The policy expressing the rights associated with the distribution if using the ODRL vocabulary."
"en": "The policy expressing the rights associated with the distribution if using the [[ODRL]] vocabulary."
},
"sh:name": {
"en": "has policy"
Expand Down
Loading

0 comments on commit 5d49bd1

Please sign in to comment.