On 3.0.1
RDFWriter w = model.getWriter("RDF/XML");
w.setProperty("allowBadURIs", true);
does not work -- calls RDFWriterRIOT.setProperty() instead of
BaseXMLWriter.setProperty(), so "allowBadURIs" has no effect.
Any workaround ideas?
On Tue, Jul 26, 2016 at 11:23 AM, Martynas Jusevičius
<[email protected]> wrote:
> Andy,
>
> "allowBadURIs" was my next move, I will try that later today and report back.
>
> Any reason why this cannot be exposed uniformly on the WriterRIOT
> level? Like it is on ReaderRIOT.
>
> On Tue, Jul 26, 2016 at 11:15 AM, Andy Seaborne <[email protected]> wrote:
>> Turtle-class syntaxes print bad URIs.
>>
>> For RDF/XML, does setting "allowBadURIs" work?
>>
>> https://jena.apache.org/documentation/io/rdfxml_howto.html#advanced-rdfxml-output
>>
>> Andy
>>
>>
>> On 26/07/16 09:34, Martynas Jusevičius wrote:
>>>
>>> RDF/XML (plain) in this case. I would of course prefer a
>>> format-agnostic solution.
>>>
>>> On Tue, Jul 26, 2016 at 10:21 AM, Andy Seaborne <[email protected]> wrote:
>>>>
>>>> Which serialization format are you working with?
>>>>
>>>> Andy
>>>>
>>>>
>>>> On 25/07/16 22:44, Martynas Jusevičius wrote:
>>>>>
>>>>>
>>>>> Hey,
>>>>>
>>>>> I was planning to set an ErrorHandler on WriterGraphRIOT instance, but
>>>>> it turns such setter does not exist.
>>>>>
>>>>> My ErrorHandler allows invalid URIs to be read without throwing
>>>>> exceptions. However model.write() throws BadURIException when writing
>>>>> them. So round-tripping such Model currently does not work. How do I
>>>>> handler writer errors?
>>>>>
>>>>> I think it would make sense to reuse the error handler between RIOT
>>>>> readers and writers.
>>>>> For example, if it is set to strict, both throw exceptions on invalid
>>>>> URIs.
>>>>> If it is set to lax, invalid URIs are allowed during both during
>>>>> parsing and writing.
>>>>> That would make round-tripping easy.
>>>>>
>>>>> Martynas
>>>>> atomgraph.com
>>>>>
>>>>
>>
