-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DCAT AP v3 profile #294
DCAT AP v3 profile #294
Conversation
Need to use Package.extras instead ckan/ckan#8288
Move from an inheritance approach to a more "composition" one, separating properties handling in three kinds of methods: * `_base()` methods with common properties to *all* versions * `_vX()` methods with properties also applied to higher versions * `_vX_only()` methods with properties only applied to the current version So for instance, the DCAT AP 3 profile calls the following methods in order: ``` def graph_from_dataset(self, dataset_dict, dataset_ref): # Call base method for common properties self._graph_from_dataset_base(dataset_dict, dataset_ref) # DCAT AP v2 properties also applied to higher versions self._graph_from_dataset_v2(dataset_dict, dataset_ref) # DCAT AP v2 scheming fields self._graph_from_dataset_v2_scheming(dataset_dict, dataset_ref) # DCAT AP v3 properties also applied to higher versions self._graph_from_dataset_v3(dataset_dict, dataset_ref) ```
Anyone interested in trying the DCAT AP v3 profile, this is ready to give it a go |
Fix method call in dcat ap 3 profile, surfaced after switching the default profile. Add changelog and update docs.
Great work @amercader ! Are there any plans for DatasetSeries support? It seems one of the most exciting (and difficult?) features of DCAT-3! |
You nailed it at the "difficult" bit @Markus92 ! 😄 |
New
euro_dcat_ap_3
profile with initial support for DCAT AP v3. It includes changes in thedcat:Dataset
anddcat:Distribution
properties.The v3 changes are not big in themselves but the profile classes have been refactored to a more "composition" approach to make easier to extend them going forward. For each DCAT AP version there are three kinds of methods:
_base()
methods with common properties to all versions_vX()
methods with properties introduced in this version and also applied to higher versions_vX_only()
methods with properties only applied to the current versionTested the serializations against the official SHACL shapes (we are ignoring the same violations described in https://github.com/ckan/ckanext-dcat/pull/291for now)