.plasma-metamodel.2.2.1.source-code.metamodel.xsd Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of plasma-metamodel Show documentation
Show all versions of plasma-metamodel Show documentation
The Plasma Metamodel Module
The newest version!
The PlasmaSDO™ metamodel is an intermediate staging or marshaling model which represents a simplified and "merged" view of any number of linked XMI/UML documents as XML. It accommodates basic UML structural and behavioral elements along with profile stereotype elements from the PlasmaSDO™ UML Profile. The goal is to provide an XML representation that more readily supports the use of "templating" languages such as XSLT. It resolves common problems associated with the XML representation of stereotyped UML models, such as representation of graph structures and linkage of stereotype instances to respective targets. Representation of graph structures is accommodated using reference or "ref" elements which are namespace qualified. And as a convenience, profile stereotypes are represented as child "delegate" objects directly under the target element being annotated, rather than placing the burden on processors to locate stereotypes at the root (XMI) level and link them.
A common superclass for all elements
A UUID or other ID passed from source models or generated at runtime
A container for packages
Application specific information for a model element
A package
A reference to a package
Application specific information for a package element
The code generation meta data associated with a namespace
The qualified Java package for generated classes for this namespace
The qualified Java package for the originating package, if any
Provides documentation for elements
A type abstraction used for both datatypes, classes, enumerations etc..
A reference to a type abstraction used for both datatypes and classes
A class definition
The code generation meta data associated with a class
The class name for the generated class
The class name for the originating class, if any
Application specific information for a class element
References a class property and serves as a property abstraction to avoid circular references within XML marshaling
The property name, unique within a class
References a class and serves as a type abstraction to avoid circular references within XML marshaling
A property definition
Application specific information for a property element
The code generation meta data associated with a property
The property name for the originating enum or other property, if any
An enumeration definition
Application specific information for an enumeration element
References an enumeration and serves as a type abstraction to avoid circular references within XML marshaling
An enumeration literal definition
Application specific information for an enumeration literal element
An SDO datatype reference
A container for content
This stereotype annotates or tags UML properties for use within various operations involving concurrency control. Concurrency control deals with handling collisions and other issues which arise when allowing multiple users or processes simultaneous access to shared entities within a data store. UML properties tagged with this stereotype contain metadata instructive, for example to an SDO Data Access Service (DAS) during commit operations for modified data graphs.
Specifies the general category of concurrency or concurrency control under which a UML property participates
For a UML property, denotes or provides a hint as to the nature of the data with respect concurrency or concurrency control
Assigns ordering and other related information to properties within an entity.
A key used to determine the ordering of properties within a class or entity.
Property value must be a number whose value must be higher or equal to the specificed minimum
Property value must be a number whose value must be lower or equal to the specified maximum
Specifies the lower bounds for numeric values (the value must be greater than this value)
Specifies the upper bounds for numeric values (the value must be less than this value)
Property value must be above or equal to the specified minimum boundary
Property value must be below or equal to the specified maximum boundary
The total number of digits for the Property value must be below or equal to the specified total
The number of fraction digits for the Property value must be below or equal to the specified total
The Property value must match the specified regular expression. The regular expression follows the Java regular expression conventions.
This stereotype constrains a UML property by means of a given UML enumeration. It enables use of UML Enumerations which are <b>part</b> of the UML model when specifying a constraint on class properties. UML Enumerations used with this stereotype must be tagged with the SDOEnumeration stereotype.
The UML enumeration class with which to restrict a UML property. UML Enumerations used with this stereotype must be tagged with the SDOEnumeration stereotype.
This stereotype provides modelling-context specific alternative names for UML named elements within a model. While a UML logical model often differs greatly from a physical model for example, the intent is to provide enough naming and other context specific information to make the physical model entirely reflective or derivitive of the UML logical model. In other words support the generation of multiple context-specific models from a single UML logical model. Modelling context specific names or aliases are particularly important as they often differ greatly between modelling contexts due to various standard naming conventions or technology limitations such as name length.
Associates a given UML element with a physical data store element. Where the physical data store is a relational database, this tag contains the name of a relational database table, schema, column or other relational database element.
Associates a given UML element with a data transfer or transient storage element. Where the transfer medium is XML, this tag contains the name of an XML element or attribute.
Associates a given UML element with a business specific, human readable name.
This stereotype tags or annotates a UML property as representing some type of key within a data store, data transfer or transient storage medium.
Specifies the type of key
This enumeration specifies the set of key types possible for any UML Property tagged with the SDOKey stereotype.
A key used as a primary identifier for the UML Class of the UML Property tagged with the SDOKey stereotype.
Tags a property as a key used as an internal identifier for a Class
Tags a property as a key used as an external identifier for a Class. An external identifier may be used by external systems and processes to uniquely idendify an object within the source system without significant central coordination. An external key is typically a universally unique identifier (UUID), globally unique identifier (GUID) or variant
Specifies the nature of the data with respect to concurrency for a UML Property
Indicates the data is an integral version number, typically incremented for every successful update of the owning entity.
Indicates the data represents a system username, typically reset to the current system user on successful update of the owning entity.
Indicates the data is temporal in nature typically reset to the system data or time for every successful update of the owning entity.
Indicates the category of concurrency or concurrency control strategy under which a UML Property participates.
Indicates a UML Property stores information related optimistic concurrency for its containing UML Class and participates in optimistic concurrency control operations and strategies. Informs SDO Data Access Services performing optimistic concurrency control checks and operations.
Indicates a UML Property stores information related to a pessimistic concurrency control strategy (often termed locking) and participates in pessimistic concurrency control operations. Informs SDO Data Access Services performing pessimistic concurrency control checks and operations.
Indicates a UML Property stores origination information for its containing UML Class. Informs Data Access Services (DAS) performing concurrent operations involving origination.
This stereotype allows a value set constraint to be specified for a class attribute. Attributes that have a coded type may be constrained such that the code value in an instance should be taken from the specified value set. The coding strength determines whether exceptions are allowed.
The globally unique identifier for the value set
The descriptive name associated with the value set
The value which identifies a specific version of the value set. Used when performing static references to a value set
The date on which a specific version of the value set was created. Used when performing static references to a value set
The time when a specific version of the value set was created. Used when performing static references to a value set
Indicates whether or not codes are restricted to those expressed in the value set
Defines the set of codes within the overall value set that must be supported by an implementer to be considered compliant
Defines the set of codes within the overall value set that the implementer is willing to accept without raising an error, but whose content will be ignored and not processed in any useful manner
Allows conveying the root code of the value set. Only usable for key structural attributes.
Defines whether the specified element is restricted to only using the identified coding system for the element
If not null, the element must be coded and must be drawn from the value set specified in the binding
If not null, the element must be coded if there is an appropriate value in the value set specified in the binding. If no appropriate code is available, a local code may be used, or the value may be populated with only original text.
Specifies the various notions of time which are relevant for temporal databases
Transaction time is the time period during which a fact is stored in the database
Valid start time denotes the beginning of a time period during which a fact is true with respect to the real world
Valid end time denotes the ending of a time period during which a fact is true with respect to the real world
This stereotype tags a UML property as unique within its UML class and resulting SDO Type. if the unique constraint 'name' is valued, the name is used all or in part as the final physical constraint id within a physical data store. Where multiple properties within a class are tagged with this stereotype, if the unique constraint 'name' is valued for more than one UML property, these properties will be used together in the resulting physical constraint.
Used to associate one or more UML properties within a class with a single constraint definition.
Indicates that a property utilizes the atomic increment operation or capability of the underlying data store
This UML stereotype is applied to a consumer UML named-element that is computed from the supplier element.
The supplier element or set of supplier elements which represent the derivation source.
The supplier element or set of supplier elements which represent the derivation source.
The supplier element or set of supplier elements which represent the derivation source.
The supplier element or set of supplier elements which represent the derivation source.
This stereotype provides modelling-context specific alternative names for UML named elements within a model. While a UML logical model often differs greatly from a physical model for example, the intent is to provide enough naming and other context specific information to make the physical model entirely reflective or derivitive of the UML logical model. In other words support the generation of multiple context-specific models from a single UML logical model. Modelling context specific names or aliases are particularly important as they often differ greatly between modelling contexts due to various standard naming conventions or technology limitations such as name length.
Associates a given UML element with a physical data store element. Where the physical data store is a relational database, this tag contains the name of a relational database table, schema, column or other relational database element.
Qualifies an XML node
An XML element
An XML attribute