Add detailed description for types

Following brian's PR on docs I added a similar section besides the one
describing in detail.

Author: perrito666

def/README.ticketing.md renamed to docs/ticketing.md

@@ -1,6 +1,83 @@
-# Ticketing The Agony and the Ecstasy of Event planning.
+# Definitions
 
-### Capacity and stock
+## Event Slot
+
+An slot in an event for an activity such as general track attendance, workshop, etc.
+
+### Attributes
+
+* Name
+* Description
+* Cost     (in amount of dollars)
+* Capacity (in amount of humans) 
+* Start Date   
+* End Date
+* Purchseable From
+* Purchaseable Until
+* Available to public (displayed on the ticket buying page)
+
+* Depends on (another slot)
+	
+## Slot Claim
+
+A slot claim is a claim from an attendee to a place in an activity.
+
+### Attributes
+
+* Event Slot (the aforementioned Event Slots)
+* Ticket ID
+* Redeemed
+
+## Attendee
+
+An attendee is a person attending an event.
+
+### Attributes
+
+* Email
+* CoC Accepted
+* Claims (a list of the slot claims for this attendee)
+
+## Claim Payment
+
+A Claim payment represents payment for one or more Slot Claims
+
+### Attributes
+
+* Claims Payed (which slot claims are payed by this payment)
+* Payment (various payments to cover total are accepted)
+* Invoice
+
+## Payment Method Money
+
+A Payment Method Money item is a payment in credit card.
+
+### Attributes
+
+* Payment Reference (to our payment processor)
+* Amount 
+
+## Payment Method Discount
+
+A Payment Method Discount item is a discount issued by the orgaization to an attendee for a claim
+
+### Attributes
+
+* Description
+* Amount
+
+## Payment Method Credit Note
+
+A Payment Method Credit Note item is a note of credit issued by the orgaization to an attendee for a claim
+
+### Attributes
+
+* Description
+* Amount
+
+# Usage
+
+## Capacity and stock
 
 The entry point for thi model are `EventSlot` items, one of these specifies Slot of Event time for which we ask an admitance ticket, these can overlap, for instance **General Admitance** Will be required to enter the general meeting area of one Event and it is a precondition to be able to obtain a **Free Workshop Ticket** which grants participation to a worhkshop that happens in the same time frame as the general event for which we granted admittance.
 
@@ -12,7 +89,7 @@ The entry point for thi model are `EventSlot` items, one of these specifies Slot
  * 100 Regular Tickets, Cost 4U$D, Sold from March to August, available to public and valid to redeem from 1st to last day of the conference
  * 50 Sponsor Tickets, Cost 0U$D, Sold from January to August, not available to public and valid to redeem from 1st to last day of the conference
 
-### Actors
+## Actors
 
 Our main actor is the `Attendee` which is a human being (or entity? entity rep?) that will buy and optionally use these Slot tickets (they could buy and transfer or just be a sponsor representative and transfer the tickets to their employees assisting the `Event`)
 
@@ -29,7 +106,7 @@ Redeeming a ticket requires 3 piece of Information:
  * Said attendee having accepted a Code of Conduct.
  * The ticket (or tickets) claimed by the attendee.
 
-### The vile metal
+## The vile metal
 
 Events cost money and so we need to charge admittance to them.
 
@@ -48,7 +125,7 @@ Currently we have the following `FinancialInstrument`:
  * Credit (`PaymentMethodCreditNote`) this is, in few words, a debt from the attendee to the event. Typically this is used when invoicing needs to happen before the payment i processed (like with large corporation sponsors).
  * Discount (`PaymentMethodConferenceDiscount`) the event organizer can discount the price of an item by giving someone scholarships or benefits or whatever kind of discount in a `SlotClaim`
 
-#### Balances
+### Balances
 
 A couple of simplifications were added as sample operations to our use of money.
 
@@ -59,7 +136,7 @@ A couple of simplifications were added as sample operations to our use of money.
 
 A `ClaimPayment` is `Fulfulled` when `DebtBalanced` and `PaymentBalanced` of `ClaimPayment.Total()` are true.
 
-#### Invoices
+### Invoices
 
 Invoces will be generated by... something, which we do not know, if it has an API and returns references, all the best.