This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
document_management [2018/11/03 23:50] andries [2. Storage of textual information] |
document_management [2018/11/04 00:00] (current) andries [5. References to physical copies] |
||
---|---|---|---|
Line 9: | Line 9: | ||
Qualitative information can be included in a Gellish in two ways: as a text string that is the description of an "information object" or by a reference to a physical file or object that contains the information. The next paragraphs describe both ways. | Qualitative information can be included in a Gellish in two ways: as a text string that is the description of an "information object" or by a reference to a physical file or object that contains the information. The next paragraphs describe both ways. | ||
- | ===== 2. Storage of textual information ===== | + | ===== 2. Modeling of textual information ===== |
Every object (represented by a UID) is normally related to two text strings: a name and a description (which may be a definition). A name is maximally 255 characters long (Unicode, nvarchar(255)). A description has an unlimited length (Unicode, ntext) in Gellish, although an application system might impose a field length limitation for the name and therefore may require that short named synonyms or abbreviations are specified. A piece of text is an 'information object' (also called 'qualitative information') that is represented by its own UID and which also has a name, whereas the text itself is expressed as the description of the information object. For example, assume that a document about road design expresses requirements for motorways. And assume that the document is decomposed in fragments that are expressed a Gellish so that the knowledge can be made available for designers of roads who might search for requirements about motorways, thus searching for 'motorway'. Assume that Paragraph 3.1 of that document consists of the text: "A motorway shall have ...". Such a description shall be provided in a Gellish expression table on the line that defines the information object, being the line that specifies what kind of information it is (or on a line where a translation of the name is specified). Thus it shall be given on the line that specifies that the information object is a qualitative subtype of some kind of information. \\ | Every object (represented by a UID) is normally related to two text strings: a name and a description (which may be a definition). A name is maximally 255 characters long (Unicode, nvarchar(255)). A description has an unlimited length (Unicode, ntext) in Gellish, although an application system might impose a field length limitation for the name and therefore may require that short named synonyms or abbreviations are specified. A piece of text is an 'information object' (also called 'qualitative information') that is represented by its own UID and which also has a name, whereas the text itself is expressed as the description of the information object. For example, assume that a document about road design expresses requirements for motorways. And assume that the document is decomposed in fragments that are expressed a Gellish so that the knowledge can be made available for designers of roads who might search for requirements about motorways, thus searching for 'motorway'. Assume that Paragraph 3.1 of that document consists of the text: "A motorway shall have ...". Such a description shall be provided in a Gellish expression table on the line that defines the information object, being the line that specifies what kind of information it is (or on a line where a translation of the name is specified). Thus it shall be given on the line that specifies that the information object is a qualitative subtype of some kind of information. \\ | ||
Line 18: | Line 18: | ||
| 111 | Paragraph 3.1 | 211 | 1726 | is a qualitative subtype of | 970007 | requirement | A motorway shall have a …| | | 111 | Paragraph 3.1 | 211 | 1726 | is a qualitative subtype of | 970007 | requirement | A motorway shall have a …| | ||
- | Note that the paragraph (object 111) has a name (Paragraph 3.1), whereas the content of the paragraph is specified in the description of the object on the line where it is defined as being a qualitative subtype of requirement (idea 211). | + | Note that the paragraph (object 111) has a name (Paragraph 3.1), whereas the content of the paragraph is specified in the description of the object on the line where it is defined as being a qualitative subtype of requirement (idea 211).\\ |
+ | Thus software can enable that people who search for 'requirement' about 'motorway' will retrieve all requirements about motorways. | ||
===== 3. Documents about objects ===== | ===== 3. Documents about objects ===== | ||
Line 36: | Line 37: | ||
^UID of left hand object^Name of left hand object^UID of idea^UID of kind of relation^Name of kind of relation^UID of right hand object^Name of right hand object^ | ^UID of left hand object^Name of left hand object^UID of idea^UID of kind of relation^Name of kind of relation^UID of right hand object^Name of right hand object^ | ||
- | | 120 | T-12345 | 220 | 1726 | is a qualification of | 490196 | drawing| | + | | 120 | T-12345 | 220 | 1726 | is a qualitative subtype of | 490196 | drawing| |
| 120 | T-12345 | 221 | 4996 | is presented on | 121 | 002.pdf| | | 120 | T-12345 | 221 | 4996 | is presented on | 121 | 002.pdf| | ||
| 121 | 002.pdf | 222 | 1225 | is classified as a | 40153 | electronic data file| | | 121 | 002.pdf | 222 | 1225 | is classified as a | 40153 | electronic data file| | ||
Line 44: | Line 45: | ||
===== 5. References to physical copies ===== | ===== 5. References to physical copies ===== | ||
- | The original master copy of a document may be a sheet of paper that is located in archive A. The additional expressions that describe that are expressed as follows: | + | The original master copy of a document may be a sheet of paper that is located in archive A. The additional statements that describe that are expressed as follows: |
^UID of left hand object^Name of left hand object^UID of idea^UID of kind of relation^Name of kind of relation^UID of right hand object^Name of right hand object^ | ^UID of left hand object^Name of left hand object^UID of idea^UID of kind of relation^Name of kind of relation^UID of right hand object^Name of right hand object^ | ||
- | | 120 | T-12345 | 225 | 4996 | is presented on | 123 | T-12345 sheet | + | | 120 | T-12345 | 225 | 4996 | is presented on | 123 | T-12345 sheet| |
- | | 123 | T-12345 sheet | 226 | 1225 | is classified as a | 492033 | sheet of paper | + | | 123 | T-12345 sheet | 226 | 1225 | is classified as a | 492033 | sheet of paper| |
- | | 123 | T-12345 sheet | 227 | 5138 | is located in | 124 | archive A | + | | 123 | T-12345 sheet | 227 | 5138 | is located in | 124 | archive A| |
- | | 124 | archive A | 228 | 1225 | is classified as a | 970492 | archive | + | | 124 | archive A | 228 | 1225 | is classified as a | 970492 | archive| |