|SimpleGraph-Excel||Excel||https://poi.apache.org/spreadsheet/quick-guide.html||makes Microsoft Excel workbooks accessible via the Apache POI API|
|SimpleGraph-FileSystem||FileSystem||https://docs.oracle.com/javase/8/docs/api/java/io/File.html||your FileSystem accessible via the Java FileSystem API|
|SimpleGraph-JSON||JSON||https://www.json.org/||makes JSON parse results accessible to Graph processing.|
|SimpleGraph-MapSystem||MapSystem||https://docs.oracle.com/javase/8/docs/api/java/util/Map.html||supplies a simple wrapper for a graph with nodes that have key/value pairs in form of HashMaps. We would not really need this since Apache Tinkerpop/Gremlin already supplies us with properties per node/vertex. Still this system is useful as a helper system and to illustrate the wrapping concepts and possibilities of SimpleGraph|
|SimpleGraph-MediaWiki||MediaWiki||https://www.mediawiki.org/wiki/API:Main page MediaWiki||makes MediaWiki site content accessible to Graph processing. It exposes the MediaWiki API using the mediawiki-japi Library by BITPlan.|
|SimpleGraph-PowerPoint||PowerPoint||https://poi.apache.org/slideshow/xslf-cookbook.html||makes Microsoft PowerPoint presentations accessible via the Apache POI API|
|SimpleGraph-SMW||SMW||https://www.semantic-mediawiki.org/wiki/Help:API||makes SemanticMediaWiki accessible via the SMW API|
|SimpleGraph-SQL||SQL||https://docs.oracle.com/javase/8/docs/api/java/sql/package-summary.html||makes relational SQL databases accessible via the Java JDBC API.|
|SimpleGraph-TripleStore||TripleStore||https://github.com/BITPlan/org.sidif.triplestore||makes BITPlan's SIDIF TripleStore accessible|
|SimpleGraph-WikiData||WikiData||https://github.com/Wikidata/Wikidata-Toolkit||makes WikiData data available via the Wikidata-Toolki API|
|SimpleGraph-pdf||makes pdf-files accessible|
Solving IT Problems across System boundaries can get very difficult. There may be a wealth of APIs which first looks helpful but given the diversity of approaches it a daunting task will need to be tackled to get reasonable results. More often than not projects are not even started since the cost/benefit ratio is not good enough. SimpleGraph aims to supply a unified graph API access to Systems for which this makes sense. In fact for most systems it makes sense to have a graph API. Quite a few problems will get much easier to solve if the subdivision of the problem is done with the goal to apply graph algorithms.
Let's assume we have a business that works in the following manner:
The monthly reports should in the future be modified to give geographical information. Basically a revenue/region sales count per product/region information is wanted.
The 1000 dollar question - can this report be created efficiently semi-manually with reasonable software effort? Sadly it sounds more like 10.000 or 100.000 dollar question.
There are at least 6 different systems involved. SimpleGraph simplifies accessing all 6 systems.
The AirRoutes example