- From: Jeen Broekstra <jeen@fastmail.com>
- Date: Wed, 19 May 2021 15:05:21 +1000
- To: public-rdf-dawg-comments@w3.org
- Message-Id: <ba988fc7-5a4c-416b-80b2-8f113f3d1c19@beta.fastmail.com>
I agree that it's annoying that such things can't be "just fixed", but generally speaking, I believe errata of official Recommendations can only be processed into a revision of the spec when a new Working Group is chartered. The errata document is specifically intended to capture the known issues until such time as that happens. The problem is that there hasn't been such a group in the past 8 years. IMO the most logical group to pick this up would be the SPARQL 1.2 Community Group (see https://www.w3.org/community/sparql-12/) if/when they ever transform into an official Working Group. Not being an official W3C member myself, I have no idea how likely that is, to be honest. Cheers, Jeen On Tue, 18 May 2021, at 22:26, John Walker wrote: > Hello, > > Is there any possibility that someone at W3C is able to address the discrepancy between the namespace give in the SPARQL Query Results XML Format [1] as compared to the XSD [2]? > > It has been in the errata list [3] already 8 years. > > [1] https://www.w3.org/TR/rdf-sparql-XMLres/#docElement > [2] http://www.w3.org/2007/SPARQL/result.xsd > [3] https://www.w3.org/2013/sparql-errata > > Regards, > > John Walker > Principal Consultant & co-founder > > Semaku B.V. | Torenallee 20 (SFJ 3.065) | 5617 BC Eindhoven | T +31 6 42590072 | https://semaku.com/ > KvK: 58031405 | BTW: NL852842156B01 | IBAN: NL94 INGB 0008 3219 95 >
Received on Wednesday, 19 May 2021 05:06:16 UTC