Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "TPTPModel"
(→Data analysis and reporting layer) |
m |
||
| (8 intermediate revisions by the same user not shown) | |||
| Line 26: | Line 26: | ||
Most of the model's code resides in the [http://dev.eclipse.org/viewcvs/index.cgi/platform/org.eclipse.tptp.platform.models/?cvsroot=TPTP_Project org.eclipse.tptp.platform.models] plugin. | Most of the model's code resides in the [http://dev.eclipse.org/viewcvs/index.cgi/platform/org.eclipse.tptp.platform.models/?cvsroot=TPTP_Project org.eclipse.tptp.platform.models] plugin. | ||
| + | |||
| + | The class diagrams of most of the models is available at [http://www.eclipse.org/tptp/platform/documents/resources/models/index.htm TPTP EMF model]. | ||
The model infrastructure covers areas like event loading (input data normalization), data manipulation, query, analysis and persistence. | The model infrastructure covers areas like event loading (input data normalization), data manipulation, query, analysis and persistence. | ||
| Line 33: | Line 35: | ||
''This section is under construction. Here are some quick notes.'' | ''This section is under construction. Here are some quick notes.'' | ||
| + | |||
| + | This section should cover the loader infrastructure. | ||
== Data persistence layer == | == Data persistence layer == | ||
| Line 38: | Line 42: | ||
The [[TPTP data persistence layer]] uses today (in [[TPTP 4.3]]) extensions of the XML and XMI [[EMF]] resources and also provides a generic mechanism to store [[EMF]] instances in a database ([http://db.apache.org/derby/ Derby] being the one supported by default), mechanism leveraged in the large log scenario. | The [[TPTP data persistence layer]] uses today (in [[TPTP 4.3]]) extensions of the XML and XMI [[EMF]] resources and also provides a generic mechanism to store [[EMF]] instances in a database ([http://db.apache.org/derby/ Derby] being the one supported by default), mechanism leveraged in the large log scenario. | ||
| − | == Data analysis and reporting | + | == Data analysis and reporting requirements == |
''This section is under construction. Here are some quick notes.'' | ''This section is under construction. Here are some quick notes.'' | ||
| − | This | + | This section should cover the support provided by the model components required by the view and reporting capability. |
Latest revision as of 16:29, 2 January 2007
Contents
Overview
This page is the entry point for informations and discussions around TPTP data models and model infrastructure.
TPTP project provides several data models (for the different domains covered by TPTP) and mechanisms to populate, query, analyze and report on those models.
Here is the list of models currently available, please follow the links to get more information for each model:
- Logging model (Common base event)
- Hierachy model (contains root objects and their relationships)
Most of the model's code resides in the org.eclipse.tptp.platform.models plugin.
The class diagrams of most of the models is available at TPTP EMF model.
The model infrastructure covers areas like event loading (input data normalization), data manipulation, query, analysis and persistence. Since TPTP 4.0 till current version TPTP 4.3, EMF has been used for the meta-model, model and persistence layer implementation.
Event loading layer
This section is under construction. Here are some quick notes.
This section should cover the loader infrastructure.
Data persistence layer
The TPTP data persistence layer uses today (in TPTP 4.3) extensions of the XML and XMI EMF resources and also provides a generic mechanism to store EMF instances in a database (Derby being the one supported by default), mechanism leveraged in the large log scenario.
Data analysis and reporting requirements
This section is under construction. Here are some quick notes.
This section should cover the support provided by the model components required by the view and reporting capability.