-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Feature Suggestion: Using JSON-LD for Gizmo results #820
Comments
Totally agree on this! Also, don't forget |
Updated the description |
Also, in "future proposals", do you mean changing The change mentioned above will break things already, so it will be HTTP API v2, and we can easily change the default |
Yeah, it will look like that: {
"@id": "bob",
"name": "Bob",
"englishName": { "@value": "Bob", "@language": "en" },
"timeCreated": {
"@value": "2010-05-29T14:17:39+02:00",
"@type": "http://www.w3.org/2001/XMLSchema#dateTime"
}
} |
Later, we can streamline the format in GraphQL as well as done in: https://github.com/rubensworks/GraphQL-LD.js |
Took a deeper look into Gremlin. It seems like you need to be explicit about the return type you get there. g.V() To get values: g.V(1).values('name') To get tags g.V().as('a').out().as('b').out().as('c').select('a','b','c') Which I find more explicit and simple. With JSON-LD the results will be: { "@id": "bob" } "Bob" { "a": { "@id": "bob" }, "b": { "@id": "alice" }, "c": { "@id": "steve" } } |
Here is a basic implementation: #821 |
@dennwc what do you think about the previous comment? |
@iddan It's definitely a nicer way for selecting results. May also help the optimizer to some extent. |
Merged #821 |
Description
Currently, Gizmo returns JSONs of strings which may or may not be valid n3 values. This is a non-standard behaviour that is hard to integrate with other systems.
Examples
Results of IRIs:
Results of literals:
"Bob"
Results of literals with language:
Results of literals with type:
All together
Future Proposals
id
default propertyThe text was updated successfully, but these errors were encountered: