Skip to content
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

dcterms:format: how to handle content negotiation support #174

Open
DavidFichtmueller opened this issue Sep 11, 2024 · 1 comment
Open
Assignees
Labels

Comments

@DavidFichtmueller
Copy link
Contributor

Term Name

dcterms:format

Digital Object Name

DigitalSpecimen: Identifier

Feedback

Definition: "Mime type of content returned by identifier in case the identifier is resolvable."

Which mime type is returned could also depend if the hosting server supports content negotiation and serves the data in multiple formats. The definition (or potentially the usage notes) should cover how to handle this. Our recommendation would be to allow for multiple formats in form of an array (thus changing the data type of this property) and list all the ones, that the server is known to provide.

@samleeflang
Copy link
Contributor

Fair point, there might be multiple Mime types in which servers can respond. I will make this an array. This will mean that we deviate from the DWCA Extension for Alternative Identifiers in which this is a single text field. However, I don't see any issues in deviating slightly on this property.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants