Major Description
Currently an XML parsing error may occur on a hasNext() call on a Sparql service query. The result is that the entire query (not just the service call) fails.
The goal of this improvement is to capture the XML parsing error and return false for the hasNext(). The result being that data errors will be silently ignored. This should be done on a per endpoint basis. Perhaps as an onParseErrorCancel flag.
I think there is an interplay of several flags in this request:
1) SILENT service parameter. If silent is true should this also be true by default? (I think not, but perhaps a system setting to make that the case)
2) cancelAllowDrain. If the error occurs should the cancel flag be raised? (I think not, but again perhaps a per service call flag to enable this)
3) JENA-93 discusses changing cancelAllowDrain to be a per endpoint setting. If that is the case it may apply here as well.