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 "SBVR-MRV Diagrams"
m |
m |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
| + | >> '''[[SBVR Tools Metamodel]]''' | ||
| + | |||
= SBVR Meaning and Representation Vocabulary (MRV) = | = SBVR Meaning and Representation Vocabulary (MRV) = | ||
== Top-Level Container == | == Top-Level Container == | ||
| − | Every concept defined in the SBVR specification is a specialization of '''Thing'''. But there is no container that can hold any kind of Thing. A '''Package''' metaclass was added for this purpose. We also allow nested Packages to enable modelers to organize vocabulary and rule modules. All of these packages and nested packages are removed when a model is saved to the SBVR exchange document XMI format, where all model elements are owned directly by the EMF Resource container. | + | Every concept defined in the SBVR specification is a specialization of '''Thing'''. But there is no container that can hold any kind of Thing. A '''Package''' metaclass was added for this purpose. We also allow nested Packages to enable modelers to organize vocabulary and rule modules. All of these packages and nested packages are removed when a model is saved to the SBVR exchange document XMI format, where all model elements are owned directly by the EMF Resource container. When an SBVR exchange document file is imported to the tools metamodel, a Package is created to contain the contents of each XMI file. |
[[Image:SBVR-MRV_Package.png]] | [[Image:SBVR-MRV_Package.png]] | ||
Latest revision as of 13:46, 16 June 2008
Contents
SBVR Meaning and Representation Vocabulary (MRV)
Top-Level Container
Every concept defined in the SBVR specification is a specialization of Thing. But there is no container that can hold any kind of Thing. A Package metaclass was added for this purpose. We also allow nested Packages to enable modelers to organize vocabulary and rule modules. All of these packages and nested packages are removed when a model is saved to the SBVR exchange document XMI format, where all model elements are owned directly by the EMF Resource container. When an SBVR exchange document file is imported to the tools metamodel, a Package is created to contain the contents of each XMI file.
Meanings
About Concepts
Representations
Fact Type Forms
Namespaces
Reference Schemes
Conceptual Schemas and Models
Elementary Concepts
