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

As a service provider, I want easy access to the registry's data in a machine-readable format, so that I can use the data directly in my service #15

Open
paulwalk opened this issue Dec 5, 2019 · 3 comments

Comments

@paulwalk
Copy link
Contributor

paulwalk commented Dec 5, 2019

No description provided.

@paulwalk paulwalk changed the title As a service provider, I want access to the registry's data in a machine-readable format, so that I can use the data directly in my service As a service provider, I want easy access to the registry's data in a machine-readable format, so that I can use the data directly in my service Jan 6, 2020
@paulwalk
Copy link
Contributor Author

paulwalk commented Jan 6, 2020

related to #19

@fsummann
Copy link

fsummann commented Jan 9, 2020

Does this issue include the question of the API design (OpenAPI standard, which query language, which aspects) and other design aspects? Relationship to existing related systems as OpenDOAR and re3data?

@paulwalk
Copy link
Contributor Author

I think that certainly these issues should be considered. But I think that we cannot, at this stage, insist on a requirement to solve the issue of standardising with other similar registry systems.

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

No branches or pull requests

2 participants