- From: Seaborne, Andy <andy.seaborne@hp.com>
- Date: Mon, 25 Sep 2006 11:30:45 +0100
- To: Fred Zemke <fred.zemke@oracle.com>
- CC: RDF Data Access Working Group <public-rdf-dawg@w3.org>
Fred Zemke wrote: > SolutionModifier consists of three optional parts: > > [14] SolutionModifier ::= OrderClause? LimitClause? OffsetClause? > > Section 10.1 "Solution sequences and result forms" > says that OffsetClause is processed before LimitClause. > Therefore it would seem more natural to rearrange this rule like this: > > [14] SolutionModifier ::= OrderClause? OffsetClause? LimitClause? > > Fred This continues the thread from http://lists.w3.org/Archives/Public/public-rdf-dawg/2006AprJun/0116 to http://lists.w3.org/Archives/Public/public-rdf-dawg/2006AprJun/0154 SQL has the order as currently in SPARQL. We could allow both orders; limit and offset go together. [14] SolutionModifier ::= OrderClause? OffsetLimitClause? [14a] OffsetLimitClause ::= (LIMIT (OFFSET)?) | (OFFSET (LIMIT)?) Andy
Received on Monday, 25 September 2006 10:31:15 UTC