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

Distinguish distribution types #45

Open
ddeboer opened this issue Jul 1, 2021 · 2 comments
Open

Distinguish distribution types #45

ddeboer opened this issue Jul 1, 2021 · 2 comments

Comments

@ddeboer
Copy link
Member

ddeboer commented Jul 1, 2021

How can we make the type of distribution more explicit? A distribution currently looks like:

{
  "@id": "http://vocab.getty.edu/aat/sparql",
  "@type": "DataDownload",
  "encodingFormat": "application/sparql-query",
  "contentUrl": "http://vocab.getty.edu/sparql"
}

The type is determined based on schema:encodingFormat. We may distinguish:

Type encodingFormat Explanation
SPARQL endpoint application/sparql-query request content type
RDF file dump text/turtle, application/ld+json etc. MIME type of the file
Non-RDF file dump text/csv etc. MIME type of the file
Content-negotiated RDF ? How to express same contentUrl providing multiple MIME types?
OAI-PMH endpoint ? How to express OAI-PMH endpoint which is underdetermined by just application/xml?
Zipped file ? Schema.org suggests application/zip but that underdetermines the type of file contained in the archive.
@coret
Copy link
Contributor

coret commented Sep 30, 2021

The application/sparql-query shouldn't be used as this is the request content type. What it intended (and expected) is the content type of the response. The default content type (if no accept header n request is given) is not defined.

I think we must apply the same logic to the "Content-negotiated RDF", so stick with the default (no accept header in request) content-type of the output.

I regards to the OAI-PMH endpoint, the (The Open Archives Initiative Protocol for Metadata Harvesting)[http://www.openarchives.org/OAI/openarchivesprotocol.html#XMLResponse] specification says:

All responses to OAI-PMH requests must be well-formed XML instance documents.

An OAI-PMH endpoint could provide XML data in one or more MetadataFormats, but this can be discovered by using verb=ListMetadataFormats

In the case of compressed files, which contain one of more files of only one type, to use the MIME type of the contents, rather than application/zip or application/gzip.

@coret
Copy link
Contributor

coret commented Sep 14, 2022

See #67 #64 and #68

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

No branches or pull requests

2 participants