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

Figure out how custom statements could output to multiple graph formats #26

Open
beechnut opened this issue Sep 17, 2021 · 1 comment
Open

Comments

@beechnut
Copy link
Collaborator

beechnut commented Sep 17, 2021

Okay, first things first, the compiler really wants Formatter objects instead of this string handling here.

Second and most importantly, we need to figure out how to support custom statements for various output formats.

Parse the Cypher and do something with it
Parse the Cypher (maybe with libcypher-parser) and render JSON or GEXF with the output. Use FFI to get the output into Ruby. May be difficult to implement, but easier on the authors.

Custom formatter per language
Custom formatter is scoped to a specific output format, so you write a template and then outputs for JSON, GEXF, and/or Cypher, whichever you're using. Maybe this is what we start with for now; I'd like to get Neo4j out of the Aspen Editor stack. Relatively simple to implement but requires more writing on the authors' part, which is antithetical to the goals of Aspen.

Introduce an abstraction
Have an abstracted graph templating language that looks like Cypher but isn't, perhaps a subset. This would require long-term support, and be quite complex, and would introduce quite a few limitations because it can't support full Cypher.

@beechnut
Copy link
Collaborator Author

I've been hearing about GQL, a standard Graph Query Language. If we wait long enough, this problem might solve itself.

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

1 participant