MyWikiBiz, Author Your Legacy — Sunday December 01, 2024
Jump to navigationJump to search
2,125 bytes removed
, 21:32, 20 November 2012
| Line 3,896: |
Line 3,896: |
| | # The first strategy is called the ''literal coding'', because it sticks to obvious features of each syntactic element to contrive its code, or the ''<math>\mathcal{O}(n)\!</math> coding'', because it uses a number on the order of <math>n\!</math> logical features to represent a domain of <math>n\!</math> elements. | | # The first strategy is called the ''literal coding'', because it sticks to obvious features of each syntactic element to contrive its code, or the ''<math>\mathcal{O}(n)\!</math> coding'', because it uses a number on the order of <math>n\!</math> logical features to represent a domain of <math>n\!</math> elements. |
| | # The second strategy is called the ''analytic coding'', because it attends to the nuances of each sign's interpretation to fashion its code, or the ''<math>\log (n)\!</math> coding'', because it uses roughly <math>\log_2 (n)\!</math> binary features to represent a domain of <math>n\!</math> elements. | | # The second strategy is called the ''analytic coding'', because it attends to the nuances of each sign's interpretation to fashion its code, or the ''<math>\log (n)\!</math> coding'', because it uses roughly <math>\log_2 (n)\!</math> binary features to represent a domain of <math>n\!</math> elements. |
| − |
| |
| − | <br>
| |
| − |
| |
| − | <p align="center">'''Fragments'''</p>
| |
| − |
| |
| − | In the formalized examples of IRs to be presented in this work, I will keep to the level of logical reasoning that is usually referred to as ''propositional calculus'' or ''sentential logic''.
| |
| − |
| |
| − | The contrast between ERs and IRs is strongly correlated with another dimension of interest in the study of inquiry, namely, the tension between empirical and rational modes of inquiry.
| |
| − |
| |
| − | This section begins the explicit discussion of ERs by taking a second look at the sign relations <math>L(\text{A})\!</math> and <math>L(\text{B}).\!</math> Since the form of these examples no longer presents any novelty, this second presentation of <math>L(\text{A})\!</math> and <math>L(\text{B})\!</math> provides a first opportunity to introduce some new material. In the process of reviewing this material, it is useful to anticipate a number of incidental issues that are on the point of becoming critical, and to begin introducing the generic types of technical devices that are needed to deal with them.
| |
| − |
| |
| − | Therefore, the easiest way to begin an explicit treatment of ERs is by recollecting the Tables of the sign relations <math>L(\text{A})\!</math> and <math>L(\text{B})\!</math> and by finishing the corresponding Tables of their dyadic components. Since the form of the sign relations <math>L(\text{A})\!</math> and <math>L(\text{B})\!</math> no longer presents any novelty, I can use the second presentation of these examples as a first opportunity to examine a selection of their finer points, previously overlooked.
| |
| − |
| |
| − | Starting from this standpoint, the easiest way to begin developing an explicit treatment of ERs is to gather the relevant materials in the forms already presented, to fill out their missing details and expand the abbreviated contents of these forms, and to review their full structures in a more formal light.
| |
| − |
| |
| − | Because of the perfect parallelism that the literal coding contrives between individual signs and grammatical categories, this arrangement illustrates not so much a code transformation as a re-interpretation of the original signs under different headings.
| |
| | | | |
| | ===6.24. Literal Intensional Representations=== | | ===6.24. Literal Intensional Representations=== |
