My prior post on Geoff pointed to a page about Geoff that appears to no longer exist. I have updated that page to point to the new location.
The current description reads:
Geoff is a text-based interchange format for Neo4j graph data that should be instantly readable to anyone familiar with Cypher, on which its syntax is based.
From the webpage:
This service allows conversion of generic XML data into a Cypher CREATE statement, which can then be loaded into Neo4j.
And:
From the webpage:
This service allows conversion of generic XML data into a Geoff interchange file, which can then be loaded into Neo4j.
Both services can be used as a web service, in addition to supporting the pasting in of XML in a form.
You will also want to visit Nigel Small’s Github page and his
homepage.
While poking around I also found:
XML data can easily be converted into a graph. Simply load paste the XML data into the left-hand side, convert into both Geoff and a Cypher CREATE statement, then view the results in the Neo4j console.
Definitely worth a deep look later this week with XML schemas.
Introducing Py2neo and Geoff by Nigel Small. (podcast)
From the description:
Py2neo has become a popular library for Python developers to drive Neo4j’s REST API. In this presentation for the Neo4j User Group, Nigel Small describes how Py2neo evolved, provide an introduction to how it is used. Nigel also explores Geoff, a textual format for storing and transmitting graph data (with a syntax heavily influenced by Neo4j’s Cypher language) and how it powers the Neo4j REPL.
If you want to read along, slides.
I don’t know the order of Neo4j, Py2neo and Geoff in a trifecta but I do know they make a very nice triplet.
Make tonight a movie night and catch this presentation.
From the webpage:
XML data can easily be converted into a graph. Simply load paste the XML data into the left-hand side, convert into Geoff, then view the results in the Neo4j console.
I would have modeled the XML differently, but that is probably a markup prejudice.
Still, an impressive demonstration and worth your time to review.
From the webpage:
Geoff is a declarative notation for representing graph data within concise human-readable text, designed specifically with Neo4j in mind. The format has been built to allow independent subgraphs to be represented outside of a graph database environment in such a way that they may be stored, transmitted and imported easily and efficiently. The basic elements which make up the Geoff format – subgraphs, rules and descriptors – are well defined but there exist several container representations which serve different purposes; commonly, either delimited text or a form of JSON is used.
Updated documentation and development of Geoff.
Topic mappers will be particularly interested in: Indexes and Merging.
Geoff This link is broken. New URL (and somewhat different explanatory text): http://nigelsmall.com/geoff
Nigel Small writes:
Geoff is a declarative notation for representing graph data within concise human-readable text, designed specifically with Neo4j in mind. It can be used to store snapshots within a flat file or to transmit data changes over a network stream.
A Geoff data set or file consists of a sequence of rules. Each rule comprises a descriptor and an optional set of data held as key:value pairs. The descriptor is a sequence of tokens, somewhat similar to the notation used in the Cypher query language and can designate additive or subtractive requirements for nodes and relationships as well as manipulations to index entries.
This looks like it will repay close study fairly quickly. More to follow.
Powered by WordPress