Github user fpservant commented on the issue:
https://github.com/apache/jena/pull/203
Hi,
there are very different points in the discussion, all around one test that
attempts to connect to an external resource.
1) It must first be noted that the test in question actually doesn't have
anything to do with the functionality that the PR proposes. It can as well be
removed, and that wouldn't change anything about the object of the PR (the
functionality that it proposes to add), nor about the completeness of the
testing of that functionality.
If you want, I can remove it.
2) this test attempts to parse some JSON-LD whose @context contains the URI
of schema.org - probably the most obvious use-case for reading JSON-LD
- BTW, I didn't see any test about reading JSON-LD. Are there any?
- If this test cannot connect to schema.org because there are no
external connection, (or for whatever reason) the test won't fail, because the
RiotException is catched. Just one line is written to the console (and it is
not by the test itself, but by the code that it calls). So this test with this
external connection doesn't really cause trouble to the integration process
(maybe a few seconds delay - the time for the HTTP client to stop trying to
connect)
- it shows me that I'm not able to read such JSON-LD on my machine (I
get on the console: ```org.apache.jena.riot.RiotException: loading remote
context failed: http://schema.org/```) - this, in a setting where it should
work (standard jena 3.1.1, run from eclipse where I can connect to external
resources from java, for instance using jersey client)
So: as far as I can tell (thanks to this test), current jena has a problem
reading JSON-LD with @context set to a URI (at least, I have such a problem
using current jena)
- it is probably possible to write a test that simulates connecting to an
external resource without connecting to it (cf. "cache" mechanism in JSON-LD
java), but
- such a test would probably not detect a problem such as the one we
seem to have here
- it's out of the scope of current PR
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
