DATA-GRID
The figure below calls out a set of requirements characteristic of Web 2.0 applications. Listed at the bottom of the figure are the DBMS 2.0™ features that meet those requirements. Click on a feature name for a brief explanation of that feature.
ontology
DBMS 3.0™ provides built-in support for ontologies. Classes within the database schema are concepts from the ontology. Queries select objects that are instances of these classes. Selection may be based on the properties of an object, or by its relationships to other objects.
DBMS 3.0™ provides built-in support for ontologies. Classes within the database schema are concepts from the ontology. Queries select objects that are instances of these classes. Selection may be based on the properties of an object, or by its relationships to other objects.
class-specific-representations
Instead of trying to force-fit everything into tuples, or have awkward add-on facilities (Oracle 'Blobs' or 'Clobs') completely outside the relational data model, an OWL class has a high-level semantic 'interface', and a separate 'representation'. That representation can be any data structure that is efficient for storing instances of the class, or that is required by a predefined external standard (i.e., MPEG-4).
Instead of trying to force-fit everything into tuples, or have awkward add-on facilities (Oracle 'Blobs' or 'Clobs') completely outside the relational data model, an OWL class has a high-level semantic 'interface', and a separate 'representation'. That representation can be any data structure that is efficient for storing instances of the class, or that is required by a predefined external standard (i.e., MPEG-4).
high-level semantics
OWL's high-level semantic model allows integration of applications and their underlying data, at the 'semantic' level — something which is simpler, and faster than attempting to integrate at a lower 'tuple' level.
OWL's high-level semantic model allows integration of applications and their underlying data, at the 'semantic' level — something which is simpler, and faster than attempting to integrate at a lower 'tuple' level.
internet-wide reach
Object-identifiers in DBMS 3.0™ are URLs. This means that an object in one OWL DBMS can refer to an object in another OWL DBMS anywhere in the Web. It also means that an object in an OWL database can reference information on pages anywhere in the Web, not just in a single database.
Object-identifiers in DBMS 3.0™ are URLs. This means that an object in one OWL DBMS can refer to an object in another OWL DBMS anywhere in the Web. It also means that an object in an OWL database can reference information on pages anywhere in the Web, not just in a single database.
fit with Web 2.0 programming languages
OWL is an object model. The DBMS is designed as a set of object classes just like the user interface and business logic portions of the program. In fact, the Ruby programmer sees the DBMS as something that stores instances of his Ruby classes in a data store that outlives the process in which his application is running.
OWL is an object model. The DBMS is designed as a set of object classes just like the user interface and business logic portions of the program. In fact, the Ruby programmer sees the DBMS as something that stores instances of his Ruby classes in a data store that outlives the process in which his application is running.