You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by afs <gi...@git.apache.org> on 2017/04/06 10:55:05 UTC
[GitHub] jena pull request #234: Changes to jena-elephas to update it for RIOT/RDFPar...
GitHub user afs opened a pull request:
https://github.com/apache/jena/pull/234
Changes to jena-elephas to update it for RIOT/RDFParser changes.
This PR is some changes to jena-elephas, around I/O, to keep it in step with the evolution of RIOT.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/afs/jena elephas-parser
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/jena/pull/234.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #234
----
commit 22fbc5ef72387c68ec1839e2e8f4b7cdfc9ad338
Author: Andy Seaborne <an...@apache.org>
Date: 2017-04-05T21:19:43Z
Move way from ParserProfile: use RDFParserBuilder
commit 099bf53fb191a759fff87855b61a8e25518152aa
Author: Andy Seaborne <an...@apache.org>
Date: 2017-04-05T21:21:03Z
Clean up warnings
commit 1130130a6580b686f09bb885c0f359e3b0b0b8a2
Author: Andy Seaborne <an...@apache.org>
Date: 2017-04-06T10:53:30Z
Align to fromString being in Jena itself
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] jena pull request #234: Changes to jena-elephas to update it for RIOT/RDFPar...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/jena/pull/234
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] jena issue #234: Changes to jena-elephas to update it for RIOT/RDFParser cha...
Posted by rvesse <gi...@git.apache.org>.
Github user rvesse commented on the issue:
https://github.com/apache/jena/pull/234
Thanks for starting on this, one of the first things I thought of when you started on the API improvements was that it would make life much easier for components like Elephas that need to manipulate the parser set up
Looks great so far
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] jena issue #234: Changes to jena-elephas to update it for RIOT/RDFParser cha...
Posted by afs <gi...@git.apache.org>.
Github user afs commented on the issue:
https://github.com/apache/jena/pull/234
This is now complete.
The build full passes.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] jena issue #234: Changes to jena-elephas to update it for RIOT/RDFParser cha...
Posted by afs <gi...@git.apache.org>.
Github user afs commented on the issue:
https://github.com/apache/jena/pull/234
Ping/FYI @rvesse.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] jena issue #234: Changes to jena-elephas to update it for RIOT/RDFParser cha...
Posted by afs <gi...@git.apache.org>.
Github user afs commented on the issue:
https://github.com/apache/jena/pull/234
Now recorded as JENA-1315.
https://issues.apache.org/jira/browse/JENA-1315
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] jena issue #234: Changes to jena-elephas to update it for RIOT/RDFParser cha...
Posted by afs <gi...@git.apache.org>.
Github user afs commented on the issue:
https://github.com/apache/jena/pull/234
The main change is gradual removal of `ParserProfile` to be replaced by a builder pattern around `RDFPaserBuilder`.
At this point, the use of pull parsing (N-Quads and N-Triple parers as iterators) is not done so this PR is not yet ready to merge but is available for initial review.
This has been a useful exercise to validate the `RDFParser` design and it shows that the design needs to cope with the iterator-parsing style.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] jena issue #234: Changes to jena-elephas to update it for RIOT/RDFParser cha...
Posted by afs <gi...@git.apache.org>.
Github user afs commented on the issue:
https://github.com/apache/jena/pull/234
This has become multi-purpose.
To clear up Elephas, some intended widespread clear up in RIOT is necessary to avoid doing changes twice.
Therefore, this PR has general RIOT evolution and also Elephas changes (in separate commits).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---