uml.PlasmaSDO.profile_v1_2.uml Maven / Gradle / Ivy
Adding profile fixes specific for Papyrus.
This stereotype tags or annotates a UML package as an SDO namespace.
The namespace URI used to reference all SDO Types contained within the UML package, and the namespace URI used link or map this UML package to SDO namespace specific configuration information.
This stereotype provides modeling-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. modeling context specific names or aliases are particularly important as they often differ greatly between modeling 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.
Annotates or tags properties as applicable 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. Generic SDO Data Access Services (DAS) are faced with the problem of determining at runtime for any data-object within a modified data-graph, which properties are useful for various checks and operations under a particular concurrency control type or strategy. Properties tagged as concurrent at the model level are made available to Data Access Services within the PlasmaSDOâ„¢ runtime and build-time environments.
Specifies the general category of concurrency or concurrency control under which a property participates
Denotes or provides a hint as to the nature of the data instructive to vaious checks and operations under a particular concurrency control type or category.
This enumeration specifies the set of key types possible for any UML Property tagged with the SDOKey stereotype.
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
Tags a property as a key used as an internal identifier for a Class
A key used as a primary identifier for the UML Class of the UML Property tagged with the SDOKey stereotype.
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 constraint to be specified for a class attribute.
Specifies the lower bounds for numeric values (the value must be greater than or equal to this value). Note: the data type is currently string to support bioinformatics and other scientific models, as no long or real primitive type exists in the current UML version and restrictions in these models often involves very, very large integral or real numbers.
Specifies the upper bounds for numeric values (the value must be less than or equal to this value). Note: the data type is currently string to support bioinformatics and other scientific models, as no long or real primitive type exists in the current UML version and restrictions in these models often involves very, very large integral or real numbers.
Specifies the minimum number of characters or list items allowed. Must be equal to or greater than zero. Note: the data type is currently string to support bioinformatics and other scientific models, as no long or real primitive type exists in the current UML version and restrictions in these models often involves very, very large integral or real numbers.
Specifies the maximum number of characters or list items allowed. Must be equal to or greater than zero. Note: the data type is currently string to support bioinformatics and other scientific models, as no long or real primitive type exists in the current UML version and restrictions in these models often involves very, very large integral or real numbers.
Specifies the exact number of digits allowed. Must be greater than zero. The total number of digits for the Property value must be below or equal to the specified total. Note: the data type is currently string to support bioinformatics and other scientific models, as no long or real primitive type exists in the current UML version and restrictions in these models often involves very, very large integral or real numbers.
Specifies the maximum number of decimal places allowed. Must be equal to or greater than zero. Note: the data type is currently string to support bioinformatics and other scientific models, as no long or real primitive type exists in the current UML version and restrictions in these models often involves very, very large integral or real numbers.
The Property value must match the specified regular expression. The regular expression follows the Java regular expression conventions. Defines the exact sequence of characters that are acceptable
Specifies the lower bounds for numeric values (the value must be greater than this value). Note: the data type is currently string to support bioinformatics and other scientific models, as no long or real primitive type exists in the current UML version and restrictions in these models often involves very, very large integral or real numbers.
Specifies the upper bounds for numeric values (the value must be less than this value). Note: the data type is currently string to support bioinformatics and other scientific models, as no long or real primitive type exists in the current UML version and restrictions in these models often involves very, very large integral or real numbers.
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 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
Used to associate one or more properties within a class under a single grouping or category.
An identifier which denotes the ordering of the property witin a key. Not an indicator related to key structure. See KeyStructure
Whether a key is automatically generated and maintained
Indicates the key arrangement or organization
Links a property element which supplies the actual data for the key where multiple possible targets exist. Where a key property is a reference SDO property and the target entity has multiple primary keys, the supplier is used by services to disambiguate which target key actually supplies the data.
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.
This stereotype annotates or tags a UML owned comment for any UML element in a model providing hints as to the nature of the comment and how it might be presented.
Specifies the various notions of time which are relevant for temporal data stores
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
Specifies the various notions of time which are relevant for temporal data stores
Restricts a property to a single concept or set of concepts within a knowledge domain
The name of a specific term within a knowledge domain
The root term within a knowledge domain
The identifier of a specific term within a knowledge domain
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.
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.
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.
This stereotype provides modeling-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. modeling context specific names or aliases are particularly important as they often differ greatly between modeling 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
Specifies the set of arrangements or organizations for any UML Property tagged with the SDOKey stereotype.
no specified structural organization
an integral identifier unique within a single column of an extent
a universally unique identifier as specified in ISO/IEC 11578
a specific compression algorithm from among those either written natively in Java or with a JNI integration available
The Lempel–Ziv–Oberhumer (LZO) algorithm, a lossless data compression algorithm that is focused on decompression speed
offers compression and decompression routines using the Lempel-Ziv (LZ) algorithm
lossless data-compression library for use on virtually any computer hardware and operating system. The zlib data format is itself portable across platforms
Java port of the snappy http://code.google.com/p/snappy/, a fast C++ compresser/decompresser developed by Google