This seems to be a bit of a moving target. The site seems to be changing because things happen different to a few days ago. I got the same XML parse error because XML processing instruction was bad, now I get the RDF, or a "500 Internal Server Error" for bad conneg.
TBC 5.2.1 used Apache Jena 3.1.0 and, for me, at the moment, Jena (3.1.0 or current development or anything but 3.4.0) fetches and parses the top level https://w3id.org/seas/ <https://www.google.com/url?q=https%3A%2F%2Fw3id.org%2Fseas%2F&sa=D&sntz=1&usg=AFQjCNFf-Iq4N2qd6PfwyX3wvpvRfZgSxw> There are then a lot of imports, each of which is a redirection. Are you behind any sort of cache? Maybe an old version of an import is cached. Downloading https://w3id.org/seas/seas-1.0.ttl gets the Turtle ... but following the imports will get RDF/XML. Andy On Saturday, 19 August 2017 07:35:39 UTC+1, Simon Cox wrote: > > Running TBC 5.2.1 > > No improvement even if trying to import the .ttl version - looks like an > XML error, so maybe something is going wrong in the redirects. > And then even if I grab a copy and put it local, then the same error is > triggered by all the imports (which is essentially all this top graph > does). > > On Tuesday, 15 August 2017 20:47:57 UTC+10, Simon Cox wrote: >> >> I'm trying to load the SEAS ontologies from >> https://w3id.org/seas/ or https://w3id.org/seas/seas-1.0 or >> >> HTTP GET appears to work (tested using PostMan), but TBC is consistently >> throwing an error while trying to import >> " ERROR [ModalContext] (ErrorHandlerFactory.java:84) - [line: 1, col: >> 50] White spaces are required between publicId and systemId." >> >> Any clue what the issue is? >> >> Simon >> > -- You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
