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

vocabulary parameter not needed for taxonomy searches #16

Open
MikeThacker1 opened this issue Mar 6, 2020 · 0 comments
Open

vocabulary parameter not needed for taxonomy searches #16

MikeThacker1 opened this issue Mar 6, 2020 · 0 comments
Labels
API

Comments

@MikeThacker1
Copy link
Contributor

We have previously suggested that API searches for services matching a taxonomy term should take this syntax:

/services/?&taxonomy_id=esdServiceType:242&vocabulary=esdServiceTypes

However, API guidance now makes it clear how CURIEs should be used for all taxonomy term identifiers. So we expect taxonomy identifiers to be unique across all vocabularies.

Hence the "vocabulary" parameter should not be needed and this syntax should be sufficient:

/services/?&taxonomy_id=esdServiceType:242
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
API
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@MikeThacker1