Yes a later version of the content model but not the storage model
Bobj
Yes a later version of the content model but not the storage model
Bobj
The content model can be changed at any time with no change to the storage model or coding. The entities on the diagram are stored as entity_types and the relationships as allowed_relationships
@pmario I have scanned the paper I mentioned above and it is available from here https://turtlelane.com.au/Papers/KBS89.pdf
bobj
For those interested, here are some diagrams detailing the Knowledge Dictionary storage and conceptual models.
This is the storage model diagram
and this is its implementation in Hypercard. For those who remember Hypercard, each entity in the model was implemented as a Hypercard stack, the equivalent of a relational database table. The relationships were recorded using foreign keys between the table records.
The ‘allowed’ entities were used to ensure only valid data elements were stored in the related three tables. So the dictionary’s conceptual model was recorded using the ‘allowed’ tables.