Difference between revisions of "Contract"
Megankatsumi (talk | contribs) m (Text replacement - "Value=Agreement" to "Value=5087-1:Agreement") |
Megankatsumi (talk | contribs) m (Text replacement - "iso5087-1:Agreement" to "ISO5087-1:Agreement") |
||
| (One intermediate revision by the same user not shown) | |||
| Line 16: | Line 16: | ||
|Property=SpecifiesAgreement | |Property=SpecifiesAgreement | ||
|Restriction=some | |Restriction=some | ||
| − | |Value= | + | |Value=ISO5087-1:Agreement |
}}{{Manchester Row | }}{{Manchester Row | ||
|Property=HasParty | |Property=HasParty | ||
Latest revision as of 02:54, 16 December 2022
Pattern
This class has been associated with the following pattern:
Subclass Of
Description
An English description of the definition (what distinguishes this sense of the term?).
A contract is a legal document that specifies some agreement(s) between two or more parties. The aim of the Contract Ontology is not to formalize the semantics of all possible involved legal concepts, but rather to enable to representation of the general structure and contents of a particular contract. The Contract Ontology adopts the definition of Contract specified in the Financial Business Ontology (FIBO) specified at: https://spec.edmcouncil.org/fibo/ontology/FND/Agreements/Contracts/ with a key modification that a Contract is defined as a type of Document and is distinct from an Agreement (not a subclass, as specified in FIBO).
A Contract is a document with the additional following properties: • specifiesAgreement: identifies the Agreement(s) that are specified by some Contract. • hasParty: identifies the person(s) and/or organization(s) that are involved in the Contract. • hasSignatory: identifies the Person(s) responsible for signing the Contract. • hasContractualElement: identifies the decomposition of a Contract into more precise parts. • isValidFor: identifies the Interval in time over which the Contract is valid for, if applicable. • isExecutedOn: identifies the Interval or Instant in time at which the terms in the Contract are executed, if applicable.
Class Diagram Description
Required by Use Case(s)
(why is this specialized definition needed?)
CDM References
What other classes or properties reference this term?
Interface Specification References
This class has been associated with the following interface specification items:
Sources
Sources considered when developing the class:
Status
Pending Approval
Has Subclass(es)
Annotations
| Annotation | Value |
|---|
Manchester Syntax Specification
| Property | Restriction | Value |
|---|---|---|
| SpecifiesAgreement | some | ISO5087-1:Agreement |
| HasParty | min 2 | (Person or Organization) |
| HasSignatory | min 2 | Person |
| HasContractualElement | some | ContractualElement |
| IsValidFor | only | Interval |
| IsExecutedOn | only | TemporalEntity |
Supplementary Figures
| Figure | Caption |
|---|