- From: Steve Harris <steve.harris@garlik.com>
- Date: Mon, 21 Nov 2011 10:37:27 +0000
- To: SPARQL Working Group <public-rdf-dawg@w3.org>
From Nick Lamb of Garlik, who implemented most of our HTTP Server. -- The removal of WSDl definitions throughout has improved clarity. -- ...However 3.1.9 still refers to MalformedQuery, which no longer appears in this way elsewhere in the document. The same for QueryRequestRefused in 3.1.10 -- Some internal links such as: http://www.w3.org/2009/sparql/docs/protocol-1.1/Overview.xml#SparqlProtocol ... don't function in the document. -- Some guidance for how a SPARQL server can report diagnostics in 2XX responses to UPDATE operations would be valuable. Right now the standard ducks the issue. If it's too late to fix in this document, a future WG might be tasked with addressing it? -- Section 4.1 seems a bit thin. Perhaps someone from the security community could be invited to help write more here? Existing best practice documents for query languages such as SQL might offer some insight too. -- A.2 lists IETF RFC 2781 (UTF-16) but nowhere else in the standard is this encoding mentioned or implicitly used. Yet in contrast UTF-8 is used throughout, but RFC 3629 (the current Internet standard for UTF-8) is not referenced in A.2 -- Steve Harris, CTO, Garlik Limited 1-3 Halford Road, Richmond, TW10 6AW, UK +44 20 8439 8203 http://www.garlik.com/ Registered in England and Wales 535 7233 VAT # 849 0517 11 Registered office: Thames House, Portsmouth Road, Esher, Surrey, KT10 9AD
Received on Monday, 21 November 2011 10:38:14 UTC