Re: Escaping control characters in SPARQL/XML or, why doesn't SPARQL/XML use XML 1.1?

On 21/07/15 13:35, Gary King wrote:
> Thanks Andy and Bob,
>
> My plan was indeed to go with SPARQL/JSON output for the reasons you suggest. Is there a move afoot to switch SPARQL/XML to XML 1.1 in some future version?

In Jena or for the W3C specs?

For Jena - send a pull request - at a guess, changes to 
XMLOutputResultSet.  Some &# encoding and setting 1.1.

Reading devolves to

For efficiency and streaming reasons, the writer is directly outputing XML.

https://issues.apache.org/jira/browse/JENA-942

for workarounds for the Java/STaX issue.

For the W3C specs - no plans as far as I know.  W3C haven't hinted at 
anything.  The most there is an errata process.

An agreement amongst users and implementers (stores and client 
libraries) to deal with XML 1.0/1.1 is probably the way to go.

There is talk of a community activity to maintain the (RDF|SPARQL) tests.

	Andy

>
>> There is a real raw control-Z in that line (which is illegal in XML 1.0).  It just displays as a space character in some fonts.  if I cut&paste the line into emacs it displays as ^Z.
>
> Ah, my bad. Thanks for catching that.
>
>> Emit XML 1.1 if you need to.
>
> Okay.
>
> thanks again,
> --
> Gary Warren King, metabang.com
> Cell: (413) 559 8738
> Fax: (206) 338-4052
> gwkkwg on Skype * garethsan on AIM * gwking on twitter
>

Received on Tuesday, 21 July 2015 13:04:35 UTC