-
Notifications
You must be signed in to change notification settings - Fork 12
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
Broken examples #165
Comments
I will have a look when I have the chance. At least the generation of the API should work. The server generation is a little more tricky, with a lot of changing dependencies. |
Thanks. The API generation works fine. |
Another quick question egarding the design of OBA and how it constructs paths and queries on those paths.... (I sent you an email a few minutes ago but not sure if you're at that address any more) When OBA generates the openapi.yaml file, are these query parameters (in bold below) reserved words? paths: It sort of looks like ‘label’ corresponds to rdfs:label class annotations, but I want to be able to query on skos:label so how would I set that? Also, how would I construct an API that can query based on the name of an instance? e.g. I have an instance |
Hello, To query on skos labels, you would have to modify the |
Thanks for your reply. Another quick question - reading through Rhys commit: 6686b8c The query manager has been updated to use ' named_graph_base=ENDPOINT_GRAPH_BASE' instead of the old 'graph_base=ENDPOINT_GRAPH_BASE' Does this mean that for graph databases using a named graph, that the config.yaml file should now use the Endpoint option like this? endpoint: |
It looks like it's how you are suggesting. However, I haven't run OBA for a while. Maybe @mosoriob knows better these options (I know best the mapping part) |
Thanks Daniel. BTW, is there an option to turn on detailed logging in OBA to see submitted URL's? I'm trying to access GraphDB at this endpoint address: endpoint: But when I submit something in my OBA generated API it returns this error: 2022-07-07 01:59:53,387 - oba - INFO - #+ summary: Given a rdf type, returns all the resources related to the type During handling of the above exception, another exception occurred: Traceback (most recent call last): |
Hmm, I do not think so, as far as I remember. We do have logging, but I don't think we enabled detailed logging :( |
Hi - this issue
This seems to be caused in OBA Sparql Query Manager not handling the JSON-LD @content processing correctly for payloads returned from a graph in JSON-LD Expanded format. I've raised an issue in KnowledgeCaptureAndDiscovery/OBA_sparql#43 |
Hi
The DBPedia Music example is now broken - it returns this error if I search for the Beatles
2022-07-06 07:14:49,310 - werkzeug - INFO - 172.17.0.1 - - [06/Jul/2022 07:14:49] "GET /v1.3.0/bands?label=Beatles&page=1&per_page=100 HTTP/1.1" 200 -
2022-07-06 07:15:11,329 - oba - INFO - #+ summary: Return the query to a resource by the resource_iri
PREFIX rdfs: http://www.w3.org/2000/01/rdf-schema#
CONSTRUCT {
http://dbpedia.org/resource/beatles ?predicate ?prop .
?prop a ?type .
?prop rdfs:label ?label
}
WHERE {
http://dbpedia.org/resource/beatles ?predicate ?prop
OPTIONAL {
?prop a ?type
OPTIONAL {
?prop rdfs:label ?label
}
}
}
2022-07-06 07:16:20,671 - grlc - ERROR - json serialize failed
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/obasparql/query_manager.py", line 455, in frame_results
response_dict = json.loads(response)
File "/usr/local/lib/python3.10/json/init.py", line 339, in loads
raise TypeError(f'the JSON object must be str, bytes or bytearray, '
TypeError: the JSON object must be str, bytes or bytearray, not tuple
2022-07-06 07:16:20,672 - werkzeug - INFO - 172.17.0.1 - - [06/Jul/2022 07:16:20] "GET /v1.3.0/bands/beatles HTTP/1.1" 200 -
Also Model Catalog fails to generate an OpenAPI server docker image.
cheers
Dougal
The text was updated successfully, but these errors were encountered: