"... In PAGE 10: ...Table 1: Some Example ROSE Spatial Operations in ROCK amp; ROLL Table1 shows part of the outcome of these integration steps. The distinguished argument type follows the `@ apos;, and the type of the returned value follows the colon.... In PAGE 11: ... The relational slant in [21] has led to the assumption that the DQL and the DML are one single SQL-like language, which explains the need in their proposal for built-in aggregation functions. However, ROCK is a computationally-complete language in which not only can the operations discussed in [21] be built using the constructs in ROCK amp; ROLL and spatial operations like those in Table1 , but other operations that wrap around primitive spatial operations as well. For this reason, the operations that are rst introduced at the OMI level of [21] are not embedded as ROCK amp; ROLL built-ins.... In PAGE 12: ...elaxed, e.g., for built-in arithmetic operations, if certain safeness conditions [10] hold. Similarly, when a spatial operation like those in Table1 that yields a non-boolean value (e.g.... ..."

"... In PAGE 10: ...Table 1: Some Example ROSE Spatial Operations in ROCK amp; ROLL Table1 shows part of the outcome of these integration steps. The distinguished argument type follows the `@ apos;, and the type of the returned value follows the colon.... In PAGE 11: ... The relational slant in [21] has led to the assumption that the DQL and the DML are one single SQL-like language, which explains the need in their proposal for built-in aggregation functions. However, ROCK is a computationally-complete language in which not only can the operations discussed in [21] be built using the constructs in ROCK amp; ROLL and spatial operations like those in Table1 , but other operations that wrap around primitive spatial operations as well. For this reason, the operations that are rst introduced at the OMI level of [21] are not embedded as ROCK amp; ROLL built-ins.... In PAGE 12: ...elaxed, e.g., for built-in arithmetic operations, if certain safeness conditions [10] hold. Similarly, when a spatial operation like those in Table1 that yields a non-boolean value (e.g.... ..."

"... In PAGE 9: ... mapping each signature onto a method-invoking expression. Table1 shows the outcome of these integration steps. The distinguished argument type follows the `@ apos;, and the type of the returned value follows the colon.... In PAGE 11: ... The relational slant in [18] has led to the assumption that the DQL and the DML are one single SQL-like language, which explains the need in their proposal for built-in aggregation functions. However, ROCK is a computationally-complete language in which not only can the operations discussed in [18] be built using the constructs in ROCK amp; ROLL and the spatial operations in Table1 , but other operations that wrap around primitive spatial operations as well. For this reason, the operations that are rst introduced at the OMI level of [18] are not embedded as ROCK amp; ROLL built-ins.... In PAGE 11: ....g., for built-in arithmetic operations, if certain safeness conditions [9] hold. Similarly, when a spatial operation in Table1 that yields a non-boolean value (e.g.... ..."