Hello, I have a SHACL validation report <https://www.w3.org/TR/shacl/#validation-report>. Of course it makes sense the report doesn't mention line and column of the "source" since the triples can come from anywhere (constructed programmatically, from memory, etc. My question is if there's any suggested way to track file and line, perhaps through some implementation detail of a parser (Jena Riot?).
Alternatively I was wondering what's a good pattern to use to display errors under this circumstances. A lot of examples I saw of validations seem to revolve around forms where the components of the triples live in known places, and so the focus node and path could be used to locate the "input field" that caused the problem, but when validating from a source RDF file in some serialization format, is less clear to me how to point to the errors (I guess I go back to needing line and column in a textual buffer). Thanks! -- 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 topbraid-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/910cd6f0-ed7a-4850-8b1f-d6fa306e3ebbn%40googlegroups.com.
