This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
verification_of_designs [2011/11/18 20:16] peterbuenk [1. The verification process] |
verification_of_designs [2017/11/15 11:15] (current) |
||
---|---|---|---|
Line 13: | Line 13: | ||
| vessel | shall have as aspect a | length between tangent lines| | | vessel | shall have as aspect a | length between tangent lines| | ||
- | Furthermore, assume that a piece of equipment, called V-1206, is delivered to the above facility owner and that V-1206 is classified as a vessel. Then the database system of the receiving party can automatically ‘know’ from the above described specification of requirements that the delivered data is only complete when V-1205 has a length between tangent lines with a value. Furthermore, assume that the data about the equipment is delivered in the form of a Gellish Database table as follows: // | + | Furthermore, assume that a piece of equipment, called V-1206, is delivered to the above facility owner and that V-1206 is classified as a vessel. Then the database system of the receiving party can automatically ‘know’ from the above described specification of requirements that the delivered data is only complete when V-1205 has a length between tangent lines with a value. Furthermore, assume that the data about the equipment is delivered in the form of a Gellish Database table as follows: \\ |
^UID of left hand object^Name of left hand object^UID of fact^UID of relation type^Name of relation type^UID of right hand object^Name of right hand object^UID of UoM^UoM^ | ^UID of left hand object^Name of left hand object^UID of fact^UID of relation type^Name of relation type^UID of right hand object^Name of right hand object^UID of UoM^UoM^ | ||
| 1 | V-1206 | 101 | 1225 | is classified as a | 520243 | vessel | | | 1 | V-1206 | 101 | 1225 | is classified as a | 520243 | vessel | |