Re: parsing and matching triples

That's a great idea. +1 From: ajs6f Sent: Tuesday, May 8, 2018 10:55 AM To: dev@jena.apache.org Subject: Re: parsing and matching triples Forking a thread off to dev@: Do we have a global policy about where null is accepted as a

Re: parsing and matching triples

Forking a thread off to dev@: Do we have a global policy about where null is accepted as a wildcard? I know it works in at least some places... I would love to (over an appropriate period of time and with lots of warnings and deprecation and so forth) stop letting it be a wildcard and require

[jira] [Commented] (JENA-1545) Add ParserProfileWrapper; expose checkTriple/checkQuad.

[ https://issues.apache.org/jira/browse/JENA-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467246#comment-16467246 ] ASF GitHub Bot commented on JENA-1545: -- Github user afs commented on the issue:

[GitHub] jena issue #416: JENA-1545: ParserProfileWrapper and public checkTruple, che...

Github user afs commented on the issue: https://github.com/apache/jena/pull/416 Extensively revised : calling `checkTriple` inside `createTriple` doesn't delegate properly in the proxy pattern. Instead, and in the interests of simplicity, any `ParserProfile` exposes enough setup