Dear Simon, all, I'm the developer of the SEAS ontology and want to report this issue is solved --> one can now load the entire SEAS ontology with all of its modules in TBC
There was two issues actually: 1. There was a HTTPS -> HTTP redirection that was known to be problematic for some clients (the body of the redirection caused the bad XML processing instruction Andy was referring to) 2. The SEAS website parses the Accept header to choose the most appropriate representation. And for some reason I was receiving Accept headers such as the following: Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 Where '*; q=.2' will make my call of javax.ws.rs.core.MediaType.valueOf() trigger an error. This was causing the "500 Internal Server Error" Andy was referring to. Best, Maxime Lefrançois http://maxime-lefrancois.info/ @INPROCEEDINGS {seassisiot, author = "Lefran\c{c}ois, Maxime", title = "{Planned ETSI SAREF Extensions based on the W3C\\&OGC SOSA/SSN-compatible SEAS Ontology Patterns}", booktitle = "Proceedings of Workshop on Semantic Interoperability and Standardization in the IoT, SIS-IoT,", year = "2017", month = "July", city = "Amsterdam, Netherlands" } Le mardi 15 août 2017 12:47:57 UTC+2, Simon Cox a écrit : > > 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.
