- I might merge it all in Java if it proves to be too annoying
  to do the RPC

- Better put all Go code into one repo.

- I've now wasted an hour on stupid file shuffling.

- It's the command line tool that will use the ulocollect lib.

- It's a Git submodule.

- code goes into /src

- prose in /doc

- /experimental is a playground

- Name interfaces in the canonical Golang way.

- Skip the complicated logging madness for now. I do want
  dedicated logging for each job, but not right now...

- This now works just fine.

- Next up is (1) refactoring, (2) cleanup of the received ULO/RDF
  files and (3) better state information (for the web interface)

We now run jobs w/o limits. This is probably bad in a hosted setup but
we can worry about that later should it ever become a problem. As it
stands the implementation is easier with a simple goroutine rather than
a complicated pool of threads.

- Not perfect yet. I think Job should be a struct so
  Collector can modify its members easily.

Now we are getting started for real :)

- This uses the RDF4J library which is what GraphDB is based on.
  Though it also supports other backends.

- The API is kinda nice tbh.

- By the end of the week I should know about the API.

- We could use SPARQL, but the RDF4J interface is essentialy SPARQL on
  steroids.

- I'm going to use graphcli to explore the GraphDB Java interface
  as the tutorials use Java.

- I'll look into Scala later (ideally tomorrow).

- Encountered some missing data in the example dataset.

- Going to look at the idea behind ulo:aligned-with

- I run these queries on graphdb which contains a subset
  of the exported Coq and Isabelle dataset.

- I can't run it on the whole datasaet yet because my
  computer would explode.

We'll have to get an iri lib or better yet fix the export in the long
run.

passed an rdf file w/ bad iris on stdin, it returns
a fixed version