- From: goodb via GitHub <sysbot+gh@w3.org>
- Date: Wed, 24 Mar 2021 19:53:05 +0000
- To: public-shex-dev@w3.org
Hi @andrawaag when faced with a similar situation for the gene ontology folks, I opened up the java shex so I could access failure information directly, rather than parsing output files. You might have more luck that way as the information you need is by definition in there somewhere. For that project, I returned 1) the node(s) that failed, 2) the properties that disagreed with the schema applied. I think this was enough to make a start on human readable error reporting, but maybe touch base with team GO to see how that is going now. The hard part we didn't really work on yet was the error cascade - e.g. when one node fails and then that failure causes another node to fail etc.. In those models, which are pretty small, human understanding can usually find the root of a problem but this will be an issue over larger models. Work was related to this issue: https://github.com/geneontology/minerva/issues/212 -- GitHub Notification of comment by goodb Please view or discuss this issue at https://github.com/shexSpec/shex/issues/115#issuecomment-806135769 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 24 March 2021 19:53:06 UTC