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

feat: Add distribution analyzer #32

Merged
merged 1 commit into from
Nov 30, 2023
Merged

feat: Add distribution analyzer #32

merged 1 commit into from
Nov 30, 2023

Conversation

ddeboer
Copy link
Member

@ddeboer ddeboer commented Nov 30, 2023

  • Probe SPARQL distributions through a simple select query.
  • Probe RDF downloads through an HTTP HEAD request.
  • Store successful responses’ Content-Length and Last-Modified headers.
  • Store error responses’ status code, using
    https://www.w3.org/2011/http-statusCodes.

Prepare for #1

<https://schema.org/target> <https://www.openarchieven.nl/foundlinks/linkset/33ff3fa4744db564807b99dbc4a3d012.nt.gz>;
<https://schema.org/error> 404.
```

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@EnnoMeijers @coret Does this data model make sense?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking at the Schema.org spec this seems to fit well. I am just trying to figure out if schema:object would be more appropriate than schema:tartget but I am not sure, so let's keep at schema:target. Should we use https://www.w3.org/2011/http-statusCodes#404 instead of just 404?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we use https://www.w3.org/2011/http-statusCodes#404 instead of just 404?

I agree we should prefer URIs over literals. Unfortunately, https://www.w3.org/2011/http-statusCodes#404 is not a valid URI; that should be https://www.w3.org/2011/http-statusCodes#NotFound.

@ddeboer ddeboer force-pushed the distribution-analyzer branch 2 times, most recently from fed22c5 to 0850d5f Compare November 30, 2023 10:37
@ddeboer ddeboer force-pushed the distribution-analyzer branch from 0850d5f to 8065ad6 Compare November 30, 2023 10:55
@ddeboer ddeboer merged commit e292ec9 into main Nov 30, 2023
1 check passed
@ddeboer ddeboer deleted the distribution-analyzer branch November 30, 2023 11:00
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

Successfully merging this pull request may close these issues.

2 participants