The ORM Foundation

Hello Ken, You say: "However, in the arithmetic paradigm, the proposition 2=2 is true and what makes it true are the rules of arithmetic that have been invented by humans and nothing else."  Depending on the exact meaning of "invented" I may agree or disagree with you on this one. The rules of arithmetic have been ...

Hi Terry, At the risk of being a little bit off topic here, the communication contexts are a point of interest to me with regard to fact based modelling. We already touched on it in the thread about Postgresql's exclusion constraints and how that can be used for example with respect to temporal information.  There are however other ...

Hello Ken, Without propositional equivalence there would be no logic. In fact, every logic starts with certain axioms that are written as equivalence relations. This document lists the axioms of propositional logic. You may disagree with some of these axioms, and feel more at ease with something like intuitionistic logic, but there too the ...

 Hello Matt,  Thank you for your kind words. I liked learning the evolution from NIAM to ORM from you.  Niels 

 Hello Ken, It was not my intention to trick you, my question was meant as rhetorical device, and I am glad upon clarification you picked up on that. It was an attempt to demonstrate that two propositions, either written in different languages or formulated using different symbol sets, can in fact be completely equivalent. I assume, you ...

 Are you sure it's two and not 2?

A quick question, Ken. Are there 2 posts preceding this one in this thread, or are there two posts preceding this one in this thread? Niels 

 Hello Ken, Having had a night to think about our discussion yesterday, I realized my argument wasn't as precise as it should have been. Let's start again with the statement "Lee Harvey Oswald  killed John F. Kennedy". In the thread you referred to, I wanted to make clear that the question whether it is a proposition ...

Hello Ken, Bitemporal modelling is closely related to exclusion constraints, a feature not directly supported in ORM. The bitemporal example I gave in this thread, uses two ranges, one to indicate the validity period of a fact and one to indicate the transaction period of a fact. As we established earlier in this thread, ranges are not ...

  Both your descriptions are more accurate than mine. I tend to be a bit hand wavy at times when dealing with people.  That said, I would like to see the discussion return to how we model bi-temporal fact (a fact having a validity period and a transaction period) in ORM, such that a mapping procedure has all the necessary information ...