You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 APIdescription: Description of my APIcontact:
name: Contact Nameurl: https://www.mywebsite.orglicence: http://example.org/licence.htmlqueries:
- name: foourl: https://www.mywebsite.org/query1.rq
- name: barurl: https://www.mywebsite.org/query2.rq
- name: bazurl: https://www.otherwebsite.org/query3.rq
The text was updated successfully, but these errors were encountered:
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
andhttp://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?The text was updated successfully, but these errors were encountered: