confusing exceptions thrown when a StringDocumentSource is passed in but
parsers for text formats fail.

The RIO binary formats will fail on StringDocumentSource because no
input streams can be found. This looks like an IO error, that stops
parsers from being attempted and gives the final user an IO error,
without parsing errors reports.

Better matching of parseability of a source and parser to use would be
useful. In the meantime, a special catch for the binary formats should
do.
added a getFormat method to avoid fetching around a manager just for
this purpose
Test cases improved. 

This test builds a variety of axioms, to be reused for testing other
visitors
fixed test broken by latest changes
removed nondeterminism from facet order
Added Builder based tests
more tests
fix #288 Errors with object property assertions with inverseOf
properties
more tests
fix #289 Manchester syntax errors: inverse() not recognized, SWRL rules
rendered twice
incomplete compareTo for literals causes random order changes in sorted
lists
roundtrip for all parsers

some formats have known bugs. This test reports failures on System.out
more tests
changes recommended by IntelliJ inspections
warnings removed
some refactorings to use lambdas
tasks reviewed and updated
fix build
Eclipse classpath for version 5 updated
OBOFormat: Configuration option to skip validation before writing OBO
file #290