In this tutorial, our aim is to write a schema and load it into our knowledge graph; phone_calls. One that describes the reality of our dataset.
First off, let’s look at the dataset we are going to be working with. Simply put, we’re going to have:
We know Grakn can be leveraged to model highly complex data, but how do we go about building a detailed model of a real-world system?
Here, we delve into Transport for London (TFL) data to understand and gain insights into the operation of the London Underground Network.
We go on to build surely the most desirable tool for such a network: a journey planner. (Because who doesn’t want to shave 0.3 minutes off their commute?)
At Grakn, we recently released Grakn 1.3, with a slew of new features, bug fixes, and performance enhancements. Included in this release are new gRPC-based drivers for Java, NodeJS, and Python. This article will walk you through the Python driver and provide guidelines on how you can write your own for your language of choice.
The main reason for rewriting our drivers was a move from REST to gRPC in Grakn. This change has cleaned up our API and should provide performance benefits. Further, all of our available drivers (Java, Node, and Python) now expose the same objects and methods to users, subject to language naming conventions and available types. To maintain this uniformity across the stack, new language drivers should provide the same interface. Note that you will require both gRPC and protobuf support to create a functioning driver, so double check a) that compilers for your language exist, and b) your target language version is compatible with the compiler.
