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.

Sign up for GitHub

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

Jump to bottom

Clarify status of excluded vocabularies #39

Open
nichtich opened this issue Jul 8, 2024 · 1 comment
Open

Clarify status of excluded vocabularies #39

nichtich opened this issue Jul 8, 2024 · 1 comment
Labels
question Further information is requested
Milestone
1.0.0

Comments

@nichtich
Copy link
Member

nichtich commented Jul 8, 2024

The following URI namespaces are excluded via HTTP proxy in front of uri.gbv.de/terminology/

These should better also be served via jskos-proxy (might require #31).
@nichtich nichtich added the question Further information is requested label Jul 8, 2024
@nichtich nichtich added this to the 1.0.0 milestone Jul 8, 2024
@StiftungAusNachlass
Copy link
Member

Beispiele:
https://uri.gbv.de/terminology/crro/rrc-290.2?format=json
https://uri.gbv.de/terminology/entityfacts/100000983?format=json
https://uri.gbv.de/terminology/gn250/DEBKGGND00000KTU?format=json

Aber alles was da bei den oben genannten Diensten kommt, ist nicht gut jskos-kompatibel. Bzw. reicht da jskos einfach überhaupt nicht und niemand würde das jskos nutzen. Die meisten der genannten Dienste sind außerdem nur Proxys und liefern letztendlich die Originaldaten der externen Schnittstellen aus. Das Originalformat muss bestehen bleiben, da es überall genutzt wird..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question Further information is requested
Projects
None yet
Milestone
1.0.0
Development

No branches or pull requests
2 participants
@nichtich @StiftungAusNachlass