I am currently writing a software requirements document. It is supposed to be modified and updated by the software developers. I would like to categorize the possible changes. To do this, I introduce several entities:
- The text of the standard, i.e. the letters written in the document
- The actual meaning of the text, i.e. how a reader would interpret it
- The supposed meaning of the text, i.e. what the writer wanted to say
There might be three levels of changes to the document:
- Change the text, but do not change the actual or the supposed meaning
- Change the text and the actual meaning, but not the supposed meaning
- Change the text and both actual and supposed meaning
Let me give an example.
- The text: "No food is better that ours" (note the typo "that" is used instead of "than")
- The actual meaning: either "There is no food that is better than our food" or "The absence of any food is better than our food", it is ambiguous
- The supposed meaning: "There is no food that is better than our food"
An example of a level 1 change: "No food is better than ours" (just fixed the typo "that" to "than", but it was obvious it was a typo)
An example of a level 2 change: "There is no food that is better than our food" (I changed the text but clearly expressed the supposed meaning)
An example of a level 3 change: "The absence of any food is better than our food" (I changed the text and the supposed meaning)
I am quite sure some philosophical branch like hermeneutics explored this kind of stuff. I wonder, are there any better names or frameworks for what I do?