slightly improving docs see #4

.gitignore

@@ -1,15 +1,18 @@
 .idea
 owl/*.owl
 download/
-db/
+db/*.db
 docs/
 load*-*
 schemaload*-*
 venv
 bin/
 target/
 test.db
-inferences/
+inferences/*tsv
+inferences/*owl
+inferences/*ttl
+*.load
 __pycache__
 *.old
 #.*#

README.md

@@ -23,6 +23,18 @@ E.g.
 SELECT * FROM my_big_table WHERE col1='...' AND col2 IN (SELECT subject FROM subclass_of_closure WHERE object='UBERON:nnnnnnn');
 ```
 
+## In flux
+
+Some parts of this repo are in-flux, see https://github.com/cmungall/semantic-sql/issues/4
+
+One particularly confusing thing is that there are two sets of semi-redundant VIEW definitions in 2 folders:
+
+ * sql/
+ * ddl/
+
+The ones in ddl are generated from the YAML, and they will eventually replace the ones in sql/
+
+
 ## Requirements
 
  * [rdftab](https://github.com/ontodev/rdftab.rs)
@@ -77,7 +89,7 @@ The `problem` view is actually a UNION view over multiple individual QC checks i
 
 ## Relation Graphs
 
-We use `relation-graph` to materialize inferred edges such as `fingernail part-of body`, these are loaded into an `entailed_edge` table
+We use [relation-graph](https://github.com/balhoff/relation-graph) to materialize inferred edges such as `fingernail part-of body`, these are loaded into an `entailed_edge` table
 
 
 

demo/cam/README.md

@@ -0,0 +1 @@
+Downloaded files will go here

demo/gaf/README.md

@@ -0,0 +1 @@
+Downloaded files will go here

tests/outputs/README.md

@@ -0,0 +1 @@
+generated files go here

utils/gpi2tsv

@@ -0,0 +1,4 @@
+#!/bin/sh
+SCRIPTPATH="$( cd "$(dirname "$0")" >/dev/null 2>&1 ; pwd -P )"
+cat $SCRIPTPATH/gpi.header.tsv
+grep -v ^\! $1