Skip to content

Act of Motion and boomerangs #606

@michaelrabenberg

Description

@michaelrabenberg

Act of Motion. A Planned Act by which an Agent causes the position or location of some Object to change.

I throw a boomerang with perfect out-and-back accuracy, so it ends up precisely where it started. Was my act an Act of Motion? I can see an argument for a "no" answer and an argument for a "yes" answer:

No: The location of the boomerang was not ultimately different from its starting location as a result of my act, so I didn't cause the location of the boomerang to change (i.e., to change ultimately), so my act wasn't an Act of Motion.

Yes: The location of the boomerang was at some times different from its starting location as a result of my act, so I did cause the location of the boomerang to change (though non-ultimately), so my act was an Act of Motion.

The heart of the matter is of course how "change" is to be interpreted in the definition.

Is there an official(-ish) correct answer to this? Note that how one answers this also affects how one understands at least some of Act of Motion's subclasses, such as Act of Location Change.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions