Procedure (one-time):
ORDB is the ontology about relational databases: "a table is built of columns, column values have a particular type, tables contain any number of rows, rows contain column values, ..."
bring the database schema into the framework:
translate it into AsTMa! => resource ontology OR
OR contains all application-specific concepts (students, names, SID, ...)
define connections between concepts in the OR and those in OI: tables, columns
this results in a set of constraints, CIR
example: "for all database rows s in table 'students', if the attribute value of 'SID' is 1234567, then there must be a topic of class 'student' with an occurrence of type 'SID' with that value in the interface ontology"
merge together: OR + CIR + OI + ORDB