search

SEMICeu / GeoDCAT-AP

Repository of the geospatial extension to DCAT-AP (GeoDCAT-AP)
https://joinup.ec.europa.eu/solution/geodcat-application-profile-data-portals-europe
Creative Commons Attribution 4.0 International
19 stars 6 forks source link

Definitions of recommended classes and properties are inconsistent #48

Closed andrea-perego closed 3 years ago

andrea-perego commented 3 years ago

§2 Terminology defines recommended classes and properties inconsistently. Quoting:

Recommended class: a sender of data SHOULD provide information about instances of the class; a sender of data MUST provide information about instances of the class, if such information is available; a receiver of data MUST be able to process information about instances of the class.

Recommended property: a receiver MUST be able to process the information for that property; a sender SHOULD provide the information for that property if it is available.

They should be aligned.

andrea-perego commented 3 years ago

Proposed revision:

Recommended class: a receiver of data MUST be able to process information about instances of the class; a sender of data SHOULD provide information about instances of the class; a sender of data MUST provide information about instances of the class, if such information is available.

Recommended property: a receiver MUST be able to process the information for that property; a sender SHOULD provide information for that property; a sender MUST provide information for that property, if such information is available.

andrea-perego commented 3 years ago

Proposed revision implemented via PR https://github.com/SEMICeu/GeoDCAT-AP/pull/50