...

• Occurrence and OccurrenceKind are not clearly distinct. Why is a Transaction event not just a subclass of Occurrence? It fits the definition. 

Payment and Payment Event

• What is the difference - the English definition does not adequately distiguish the meanings of these two. 

Recommended Changes

Definition not match axioms 

• oc:Occurrence definition says there is both a date and a location, but there is no restriction for a date. Should be added.
  "An Occurrence is a happening of an OccurrenceKind. Each Occurrence has a DateTimeStamp, which identifies when the Occurrence happened, and a Location" 

Making things simpler

Contract and ContractTermsSet

...

Make corp:hasDateOfIncorporation a subproperty of (a new property called hasCreationDate which is a subproperty of) fd:hasStartDate  

Recommended Additions

Chunks of ontology

1. for representing communication, which includes request, reponse, from/to and content of the communication. MU has some clear ideas abou this to be shared at a future date.
2. ordering products is a special kind of request., link with FND products and services. 

Classes

MarketCategory: 

Definition: Specifies the market domain in which a product is offered.  This is a superclass of LoanMarketCategory which is: specifies the market domain in which the loan product is offered. 

RiskAssessment

A subclass of oc:Occurrence that means the event of determining the risk of something. For loans, we have a subclass called CreditRiskAssessment, which entails among other things, getting a credit report.

InformationProduct

For things like credit reports. A Product that is informational in nature, rather than physical.

PostalAddress

There needs to be a way to spell out details of an address, city, street etc, ideally beyond just a string. Cities and zip codes are real things.

...