-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Description
Hello! I'm not able to find this information anywhere in the documentation, so I'm hoping the community can help clarify these points.
I'm implementing DCAT-AP and have questions about the intended usage of version-related fields:
- Is the version/versionNotes in DCAT-AP meant to track changes to the actual data asset, the metadata describing it, or both?
- How does the modification date (dct) relate to versioning? Should it be updated when metadata changes, when the underlying data asset changes, or both?
- Is there a recommended approach for tracking metadata changes? Should we create new versions whenever metadata changes, or only when the underlying data changes?
- Is metadata versioning considered valuable in DCAT-AP implementations, or should versioning focus primarily on data content changes?
Any clarification would help ensure our implementation follows best practices for interoperability.
Metadata
Metadata
Assignees
Labels
No labels