Some turtle doesn't load

[cuddihyge]

<uri://semtk#03e7e60c-7ac6-4f02-8186-55937ccaa2e8> <http://arcos.rack/PROV-S#dataInsertedBy> <uri://semtk#fa4280ba-200d-4966-aea2-02121d30e2db> .
<uri://semtk#03e7e60c-7ac6-4f02-8186-55937ccaa2e8> <http://arcos.certgate/LM#gid> "f1a48655-73f4-4dda-be34-eb5ddfbbcd97 " .
<uri://semtk#03e7e60c-7ac6-4f02-8186-55937ccaa2e8> <http://arcos.certgate/LM#uuid> "62daa8b9-92a1-4f15-923d-4d264d9c41f8 " .

Doesn't seem to load as valid turtle through semtk. It does however load via the :3030 "Add Data"

[cuddihyge]

Bonus question: can we stream through javascript instead of reading in the whole file.

[weisenje]

Confirmed can successfully load TTL file with 3 triples above via Fuseki UI :3030 "Add Data". When loading the same file via SPARQLgraph, the error is:

[cuddihyge]

Confirmed that we can not load sparqlGraphLibrary src/test/resources/musicTestDataset_2017.q2.ttl via the python client.

Suggest we try to straighten this out starting with:

1. junit test in java
2. semtk3-python test

[weisenje]

The primary error was: [line: 1, col: 1 ] Content is not allowed in prolog. Fixed in couple different places to send Fuseki a filename with a ttl extension (which it needs to recognize the file as valid). Also added various client functions and JUnit tests.

• This commit enables FusekiSparqlEndpointInterface to successfully upload turtle (send filename instead of “something.owl”).
• This commit enables the uploadTurtle/ endpoint to successfully upload TTL (use the multipart file’s originalFileName to get the .ttl extension).
• This commit adds a working Python upload_turtle test

Can now successfully upload TTL files from Java client, Python client, and SPARQLgraph.