Modeling database view in EDG?

[Fan Li]

In EDG Data Asset ontology, the following definition is provided for the "View" class:

    A 'View' is typically a database construct for exposing a specific set of data fomr one or more database tables along with computed variables.

However, while the view can be traceable to a logical entity or a class, I don't see how it is associated with a "database".

I would like to describe a view such as it is derived from a relational database (or NoSQL), it contains several columns and their datatypes etc., much like a data table. 

Please let me know if you have any guidance. Thank you!

[Irene Polikoff]

In a relational database, a view is a virtual table. Much like a real table is connected to a database it belongs to via edg:tableOf property, a database view is connected to a database via edg:viewOf property.

Columns of a view can be connected to it via edg:columnOf property. 

There are several examples of the above in the Northwind sample.

If you want to go beyond this and describe how a view is composed from the underlying physical tables, you can use edg:viewInputColumn property to point to specific columns in the specific tables that are used to create a view.

If you want to go into more details of the view derivation, for example, if some of the view columns are calculated by applying some formulas, then look at my answer to your prior question about mappings.

--
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to topbraid-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/1d2ad6fd-339c-4675-9e96-8d7a9688acf1n%40googlegroups.com.