Just trying to verify consistency of a system, I need to have a list types of inconsistency to look out for, so far I have the followings:

1.Anachronistic inconsistency (e.g. trying to read a file before it is been written).

2.Type inconsistency (e.g. treating an object as a type that is incompatible with the assumed type, e.g. treating lead as steel is inconsistent (lead can not replace still in all the contexts), but treating lead and steel as metal is consistent. (where ever lead or steel is used just as a metal they are interchangeable)).

3.Interface inconsistency : Trying to interact with an object through an interface that it does not support ( e.g. trying to plug in a charger designed for electrical outlets of Australia, in US ). How ever if we could even plug them in, the difference in voltage(?current) would blow up the charger due to type inconsistency ( can not treat electrical US electrical current same as Australian electrical current or vice verse)

4.Causal Consistency : Maybe this is same as Anachronistic inconsistency, e.g. a Glass cannot break midair before it hits the floor. Although the after effects of both are indistinguishable from the consistent version, there is an inconsistency in mid process.

I have tried googling, but Physical paradox was the only useful topic so far when googling : "list of physical inconsistencies".

Any alternative searches or topics to look up would be greatly appreciated

  • 1
    I think you are going to run into a problem that you are looking for a particular taxonomy of inconsistencies which maps to your particular task. I would not be surprised if there are thousands of named types of inconsistencies in philosophy, but you need them in a taxonomy which is helpful to you. Given your choice of programmer verbiage, might this be better suited for programmer SE? – Cort Ammon Jul 27 '15 at 5:20
  • @CortAmmon : Thank you, I be happy with any taxonomy of inconsistencies, although I grabbed a problem from programming, I am more interested in philosophical inconsistencies. I highly doubt that programmers have even pondered about listing inconsistencies in programming let alone classify them. – jimjim Jul 27 '15 at 5:39

There is are a number of books by Graham Priest on this; the general term is dialethism: the proposition that there are true contradictions.

  • I am sorry, I can not see how does this relates to my question. I like this concept, taught me a new concept +1. – jimjim Aug 2 '15 at 10:14
  • 1
    @arjang: you might want to take a closer look at Cort Ammons comment; the kinds of inconsistency you're discussing in your question aren't philosophical types of inconsistency – Mozibur Ullah Aug 2 '15 at 12:24
  • I dont know more I can do with Cort Ammons comment, I am open to suggestions. – jimjim Aug 2 '15 at 12:26
  • Well, your notion of 'inconsistency', say for your first point, the 'anachronistic inconsistency' appears to be relying on the ordinary language use; in this case it just means doing things out of order in time; but this can go for many things; in which case the closest analogy I can think of is knowing how to use a tool well; it's a form of practical knowledge; not knowing how to use a tool well isn't inconsistency, merely lack of practical knowledge. – Mozibur Ullah Aug 2 '15 at 12:38
  • 1
    Let us continue this discussion in chat. – Mozibur Ullah Aug 2 '15 at 12:41

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.