There are two different arities for the projects_onto relation

[GoogleCodeExporter]

"ELUCIDATION: To say that each spatiotemporal region r projects_onto some 
temporal region t is to say that t serves as the temporal extension of r. 
[080-001]
ELUCIDATION: To say that spatiotemporal region r projects_onto spatial region s 
at t is to say that s serves as the spatial extent of r at t. [081-001]
"

so we have projects_onto spatiotemporal region -> temporal region
and
projects_onto spatiotemporal region -> spatial region at t

As in other such cases, we need two separately named relations in this case.

Original issue reported on code.google.com by alanruttenberg@gmail.com on 22 May 2012 at 3:20

[GoogleCodeExporter]

I agree. 
I suggest 

projects spatially onto for spatiotemporal region onto spatial region
projects temporally onto for spatiotemporal region onto temporal region

located_in for continuant in spatial region
occupies for occurrent in spatiotemporal region
spans for occurrent on temporal region

Original comment by ifo...@gmail.com on 22 May 2012 at 3:27

[GoogleCodeExporter]

projects spatially onto for spatiotemporal region onto spatial region
yes
projects temporally onto for spatiotemporal region onto temporal region
yes

located_in for continuant in spatial region
We already have located_at defined for this. located_in is 
continuant->continuant

occupies for occurrent in spatiotemporal region
the current definition of occupies covers both spatiotemporal region and 
temporal region. I'm fine splitting to two cases by making occupies only to 
spatiotemporal regions and making spans (not keen on the label) being only for 
temporal regions. I'm also fine leaving them as one relation and not including 
spans (since it is easily defined as a shortcut relation should we want it 
later). 

spans for occurrent on temporal region

Original comment by alanruttenberg@gmail.com on 22 May 2012 at 4:52

[GoogleCodeExporter]

Original comment by alanruttenberg@gmail.com on 23 May 2012 at 3:49

• Changed state: Started

[GoogleCodeExporter]

Fixed

Original comment by alanruttenberg@gmail.com on 15 Jun 2012 at 4:53

• Changed state: Fixed