Skip to content
This repository has been archived by the owner on Sep 24, 2019. It is now read-only.

bel2rdf: a more "graceful" way to fail? #38

Open
juliakozlovsky opened this issue Apr 13, 2015 · 2 comments
Open

bel2rdf: a more "graceful" way to fail? #38

juliakozlovsky opened this issue Apr 13, 2015 · 2 comments

Comments

@juliakozlovsky
Copy link

At the moment, when bel2rdf conversion fails, it stops processing. So, for example, if it's converting a file of a 100 BEL statements and the first statement has issues, the remaining 99 won't get converted either. I think it would be considerably more useful, if the code could go one statement at a time, converting the "good" statements to RDF and writing the "bad" ones into an error/log file.

@abargnesi
Copy link
Member

Thanks for reporting!

This result is due to the existing BEL parser not recovering from recognition errors. I opened #39 to handle short-term changes to the ruby BEL parser to capture recognition errors.

Longer-term #22 will provide a line-based, C parser with more accurate errors.

@abargnesi abargnesi added this to the 0.4.0 milestone Jun 23, 2015
@abargnesi abargnesi added the RDF label Feb 23, 2016
@abargnesi
Copy link
Member

This will need to be addressed after #122 is complete.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants