Github user hartig commented on the issue:
https://github.com/apache/jena/pull/299
Agreed.
---
Github user afs commented on the issue:
https://github.com/apache/jena/pull/299
Looks like we're done here for now with parsers at
https://github.com/RDFstar/RDFstarTools/ .
---
Github user hartig commented on the issue:
https://github.com/apache/jena/pull/299
Add the PR #418
---
Github user hartig commented on the issue:
https://github.com/apache/jena/pull/299
> That does not work because the `ParserProfileStd` supplied to
`TurtleStarReaderRIOT` has already been created, which is why the suggestion is
to use a forwarding proxy object (the wrapper) with
Github user hartig commented on the issue:
https://github.com/apache/jena/pull/299
I agree. Making `checkTriple` protected in `ParserProfileStd` would be an
even better idea. Please do it.
While we are at it, can you add another constructor to `TurtleShell` that
allows me to
Github user ajs6f commented on the issue:
https://github.com/apache/jena/pull/299
+1 on keeping the "default" check as-is, but making the choice of calling
it / changing it available via a wrapper.
---
Github user afs commented on the issue:
https://github.com/apache/jena/pull/299
@hartig - I'm ambivalent on changing `ParserProfileStd` because that
guarantee on `checkTriple` (and `checkQuad`) checks a condition that a lot of
code assumes is valid and does not check again. Hence the
Github user hartig commented on the issue:
https://github.com/apache/jena/pull/299
Ah, one more thing: @afs, would it be possible to extend the `checkTriple`
method of `ParserProfileStd` to permit the subject and the object of a triple
to be `Node_Triple`?
This is the only thing
Github user hartig commented on the issue:
https://github.com/apache/jena/pull/299
I finally have implemented a Turtle* parser that hooks into Jena's RIOT
parser framework and uses the `Node_Triple` class that @afs had added to Jena
in PR #327. Find the code at
Github user hartig commented on the issue:
https://github.com/apache/jena/pull/299
Great Andy, thanks! I will check it out after the holidays. (I'm a bit
overloaded here at the moment)
---
Github user afs commented on the issue:
https://github.com/apache/jena/pull/299
@mschroeder-github, @hartig
Apache Jena 3.6.0 is out and has `Node_Triple` for you. Feedback etc
welcome - this is an experimental feature and can be revised. Note - this does
not mean parsers
Github user afs commented on the issue:
https://github.com/apache/jena/pull/299
PR #327 adds an RDFTerm for a triple.
---
Github user afs commented on the issue:
https://github.com/apache/jena/pull/299
Every chance if the Jena committers and PMC agree.
Developing as a separate module, outside Jena, to start with helps the work
by not getting entangled in timing and release issues of Jena
Github user hartig commented on the issue:
https://github.com/apache/jena/pull/299
Thanks Andy! I agree with what you write.
Do you think there is a chance for such a separate maven module to become
part of the official family of Apache Jena maven modules?
---
Github user afs commented on the issue:
https://github.com/apache/jena/pull/299
Executing SPARQL over the id-specific standard RDF representation of RDF*,
could be done with without needing to modify the core algebra by expansion of
`<<:s :p :o>>` in BGPs.
For `BIND(<<:s :p
Github user hartig commented on the issue:
https://github.com/apache/jena/pull/299
Thanks @mschroeder-github for taking the initiative of writing an RDF*
parser for Jena!
@afs Before responding to some of your comments, I should mentioned that I
am still actively working on
Github user afs commented on the issue:
https://github.com/apache/jena/pull/299
Sorry for the delay getting round to this - Jena had a release which
takes time. It would be interesting to see some support for RDF*.
Comments in two areas : the parser and about RDF*.
17 matches
Mail list logo
