rvesse commented on issue #2102: URL: https://github.com/apache/jena/issues/2102#issuecomment-1824114601
Jena 4.x more strictly enforces certain tests around URI validity because allowing base URIs into the system always leads to problems down the road. Since this is a URI it should be URL encoded appropriately (i.e. Java/SPARQL backslash escapes are not suitable here), and that needs to happen in both your data and your queries. In general the way your URIs are structured looks strange. You seem to be trying to put a lot of "structure" into the URI fragment (the portion after the `#`) when you should really be using `/` based URL construction to achieve this, and your URIs seem to conflate schema concepts with instances of those concepts. Your data should probably have URIs more like `https://yourdata.com/building/gtc/rooms/1.H.1/room` with appropriate `rdf:type`'s declared as you do in your example where `yourdata.com` is substituted for some appropriate URI for the instances of the data, rather than the schema concept URI as you do currently -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
