Topic Map Database Management System axioms

I have been thinking lately about how a Topic Map Database Management System might be designed, so I made this list of axioms:

1. The Topic Map Database Management System (TMDBMS) is computer software executed on a Database Server which purpose is to manage databases based on a Topic Map Data Model as defined in ISO/IEC 13250-2.
2. A TMDBMS must allow for organization, storage, management, and retrieval of Entities and/or Relationships in databases based on a Topic Map Data Model as defined in ISO/IEC 13250-2.
3. A TMDBMS must include a Database Engine that is in it self or includes a Topic Map Engine.
4. A database in a TMDBMS must be the Logical View equivalent of a Topic Map as defined in ISO/IEC 13250-2.
5. A TMDBMS database may include Meta Data that goes beyond the scope of a Topic Map Data Model for internal use as long as this is part of the Physical View and not the Logical View.
6. A TMDBMS Database Entity must relate directly to a Topic Map Topic and/or Topic Map Association a Topic Map Construct, all as defined in ISO/IEC 13250-2.
7. A TMDBMS Database Relationship must relate directly to any kind of Topic Map relationship, all as defined in ISO/IEC 13250-2.
8. A TMDBMS Database must relate directly to a Topic Map as defined in ISO/IEC 13250-2.
9. A TMDBMS must be able to contain several databases.
10. A TMDBMS must be able to merge databases as defined in ISO/IEC 13250-2.
11. A TMDBMS database must be able to contain several Entities and/or Relationships.
12. A TMDBMS must be able to accept requests for data from the Application Program and instruct the Operating System to transfer the appropriate data.
13. TMDBMS may have implemented the Topic Map Constraint Language (TMCL) to define schemas and constraints for the Topic Map Data Models and work as Rule Enforcement for the Logical View of the databases.
14. A TMDBMS must store the database Entities and/or Relationships in External Storage System.
15. A TMDBMS must include database Persistence in such a manner that an unexpected TMDBMS shutdown will not cause data to be lost.
16. A TMDBMS must have implemented a Topic Map Query Language (TMQL) processor, as defined in ISO/IEC 18048, to allow users to interactively interrogate the database and analyze its data according to the user’s privileges on data.
17. A TMDBMS must have implemented a Topic Map Compact Syntax (CTM) processor, as defined in ISO/IEC 19756, to allow users to interactively interrogate the database, analyze its data and update it according to the user’s privileges on data.
18. A TMDBMS must include Indexing of Entities and/or Relationships for faster inserting, retrieving and deleting of Entities and/or Relationships in an External Storage System.
19. A TMDBMS may include Full Text Indexing of the database Topic Map Information Resource Data, as defined in ISO/IEC 13250-2, for faster inserting, retrieving and deleting of Entities and/or Relationships in an External Storage System.
20. A TMDBMS must include a Connectivity Application Programming Interface, for example like Open Database Connectivity (ODBC), to enable Application Programs to access the TMDBMS and its databases over a computer network like a Local Area Network (LAN), a Wide Area Network (WAN), and over the Internet.