dcterms:issues is the more appropriate property to use, which is defined as "Date of formal issuance of the resource." https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/issued Resolves #456 - [ ] ~~`docs/` have been added/updated if necessary~~ - [ ] ~~`make test` has been run locally~~ - [ ] ~~tests have been added/updated (if applicable)~~ - [X] [CHANGELOG.md](https://github.com/mapping-commons/sssom/blob/master/CHANGELOG.md) has been updated. If you are proposing a change to the SSSOM metadata model, you must - [ ] provide a full, working and valid example in `examples/` - [ ] provide a link to the related GitHub issue in the `see_also` field of the linkml model - [ ] provide a link to a valid example in the `see_also` field of the linkml model - [ ] make sure any new slot is annotated with the appropriate `added_in` annotation - [ ] run SSSOM-Py test suite against the updated model @gouttegd I don't think we need to add verioning annotations when we make a change like this, right?

Change publication_date to be dcterms:issued #456

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions