Added Determination class.

[uscholdm]

Closes #317.

I made the class a direct subclass of Event because a Determination need not be historical, it may be planned but unscheduled, or scheduled, in the process of happening, or already happened.

[marksem]

I like the work done so far.

Q: Is there any property that would always be the case on a determination? Otherwise this is just a named class.

[uscholdm]

@marksem In real world terms, a determination

• will always have an entity that does the determining (maybe inverse of produces) with the doer being a person, machine or program
• will generally have an outcome (in the past I have used hasOutput for this)
• will often have a method (min 0).

I'm ok with it just being a named class.

[rjyounes]

I like your proposed definition, so will approve this once you've added it and removed the scope note.

[rjyounes]

@uscholdm I'm leaving this unmerged to consider whether we want to name it DeterminationEvent rather than Determination. Looks like it also needs to be updated with latest changes on develop.

[uscholdm]

@uscholdm I'm leaving this unmerged to consider whether we want to name it DeterminationEvent rather than Determination. Looks like it also needs to be updated with latest changes on develop.

Lets leave it as it is. Its a subclass of Event.