captureOf vs Capture

[nickdrummond]

What distinguishes the participation properties from the Event type? eg captureOf/Capture and escapeOf/Escape

If we can untangle the use of 'of' as being the main subject in an Event then we can remove these unnecessary properties?

[nickdrummond]

Can 'of' simply be a subproperty of participant? If it is only used as the subject of an Event then yes..

Counter examples:

• Sabotage -> of only (...Object) - can an object be a participant? Yes, Actor, Object, Place several examples including... Sabotaging Thrawns Star Map -> included some (Sabotage and (of some Map))
• Standoff at the fuel depot ->participant some (Crew and (of some Glider) ... Need to get rid of this inconsistent usage of 'of' - it should be ofShip (we could make that broader)

It would also need an inverse?

[nickdrummond]

This still leaves multiple ways to model the murder - using 'of' or 'killingOf' If we have a mix then it complicates querying. Murder of A does not imply killingOf A

We might have Killing event but that's going to introduce a lot more class assertions: eventA killingOf ind becomes eventA -> includes some (Killing and (of value ind))

[nickdrummond]

And potentially adding a lot of nesting

included some 
    (Fight and (killingOf value Proach) and (participant value Garazeb_Orrelios) and (stunningOf value Kanan_Jarrus))

We've so far avoided nesting included

[nickdrummond]

This treatment of of works for the following Events which all have a primary subject:

• [x] - Arrival
• [x] - Birth
• [x] - Capture
• [x] - Chase (?)
• [x] - Crash (of Vehicle)
• [x] - Departure
• [x] - Escape
• [x] - Evacuation (of Place)
• [x] - Healing
• [x] - Hiding (of Object or Person or Vehicle)
• [x] - Murder + Execution
• [x] - Repair
• [x] - Rescue
• [x] - Sabotage
• [x] - Surrender
• [x] - Torture
• [x] - Transfer + Defectionsubproperties (transferOf??)
• [x] - Wedding
• [x] - Trading - implement as Transfer?
• [x] - Stealing - implement as Transfer?

[nickdrummond]

That's quite a lot of refactoring!

[nickdrummond]

Going to need some transformation code

[nickdrummond]

So, what are the transforms?

1) Property assertion:

    eventA killingOf personB
    eventA -> included some (Killing and (of value personB))

2) Class assertion:

    eventA -> killingOf some Droid
    eventA -> included some (Killing and (of some Droid))

3) Subevent - "merge" the types of the subevent - a fight and a killing?

    eventA -> included some (Fight and (killingOf value personB))
    eventA -> included some (Fight and (Killing and (of value personB)))

or make the killing a sub event?

    eventA -> included some (Fight and (included some (Killing and (of value personB))))

4) Subevent generic killing of some folk - same as 3)

    eventA -> included some (Fight and (killingOf some (hadRole some RoleC))
    eventA -> included some (Fight and (Killing and (of some (hadRole some RoleC)))

[nickdrummond]

Written a reifier to transform based on these rules. Applied to the ontologies. Made Killing an Event and Murder is a subclass.

Classification times are not ~8s Ontologies processed in 8072 ms by Pellet

Before this refactor: Ontologies processed in 7474 ms by Pellet

[nickdrummond]

Reifying Death(of) adds even more time to classification. Ontologies processed in 9097 ms by Pellet

[nickdrummond]

Replaced all diedInYear with events

[nickdrummond]

Just need to update the docs/examples/sparql

[nickdrummond]

"Attack of" doesn't scan so leaving for now.