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

Handling of name clashes for endpoints #344

Open
jaw111 opened this issue Jun 2, 2021 · 1 comment
Open

Handling of name clashes for endpoints #344

jaw111 opened this issue Jun 2, 2021 · 1 comment

Comments

@jaw111
Copy link

jaw111 commented Jun 2, 2021

Opening this to continue discussion from #331 about handling of name clashes for endpoints that may arise if the 'local' names of sparql queries are the same. Let's say I reference queries http://example.com/path/query.rq and http://example.com/some/other/path/query.rq, what should the behavior be?

Is it reasonable to allow to (optionally) specify a name for the endpoint possibly by adding a new name decorator or extending the YAML specification?

title: Title of my API
description: Description of my API
contact:
  name: Contact Name
  url: https://www.mywebsite.org
licence: http://example.org/licence.html
queries:
  - name: foo
    url: https://www.mywebsite.org/query1.rq
  - name: bar
    url: https://www.mywebsite.org/query2.rq
  - name: baz
    url: https://www.otherwebsite.org/query3.rq
@c-martinez
Copy link
Collaborator

I think this is a nice proposal. Are there any other attributes we would like to for each query?

@albertmeronyo -- any thoughts?

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