Plasma is a data store agnostic, object mapping and object query framework written in a Java™ with Maven tools for metadata ingestion and conversion
TerraMeta Software, Inc.
PlasmaSDO® and PlasmaQuery® are registered
Trademarks of TerraMeta Software
Revision History
Revision | Date | Description | Author |
1.1.7 | November 26, 2011 | Plasma Team Members |
Table of Figures |
Figure 1. UML Enumeration Extension Stereotypes Diagram 2 |
Figure 2. UML Property Extension Stereotypes Diagram 3
Figure 3. UML Comment Extension Stereotypes Diagram 3
Figure 4. UML Package Extension Stereotypes Diagram 4
Figure 5. UML NamedElement Extension Stereotypes Diagram 4
Figure 11. SDOEnumerationConstraint 10
Figure 14. SDOSemanticConstraint 12
Figure 16. SDOUniqueConstraint 14
Figure 17. SDOValueConstraint 15
Figure 18. SDOValueSetConstraint 17
Figure 19. DocumentationType 20
Figure 20. UML Comment Extension Stereotypes 29
Figure 21. UML Enumeration Extension Stereotypes 29
Figure 22. UML NamedElement Extension Stereotypes 30
Figure 23. UML Package Extension Stereotypes 30
Figure 24. UML Property Extension Stereotypes 31 |
The Service Data Objects (SDO) 2.1 specification provides an extensible, lightweight runtime-available metadata API. It is through extensions to the SDO metadata API that the PlasmaSDO™ implementation provides more than just standard structural metadata elements, but numerous other context specific elements instructive at build-time as well as run-time to SDO Data Access Services and other consumers at various enterprise technology layers and various parts of a technology stack. The PlasmaSDO™ metadata extensions are described this UML profile which contains UML stereotypes, enumerations and other elements used to enrich UML models for use within the PlasmaSDO™ core as well as third party Data Access Service (DAS) providers.
Particular design consideration has been focused on leaving each stereotype granular with only a few tightly related attributes/tags, rather than more monolithic stereotype groupings. This approach lets each stereotype convey far more meaning and maps well to metadata oriented extensions in various target languages, such as Java™ annotations. This granular approach can however have the effect of making UML diagrams more cluttered depending on the presentation settings of the UML diagramming tool.
Description
The PlasmaSDO™ Platform UML profile contains stereotypes used to enrich UML models for use within the PlasmaSDO™ Service Data Objects 2.1 implementation and associated platform. Particular design consideration has been focused towards leaving each stereotype granular with only a few tightly related attributes/tags. This approach lets each stereotype convey far more meaning, but can have the effect of making UML diagrams more cluttered depending on the presentation settings of the UML diagramming tool. A single UML logical model enriched or annotated with this UML profile provides enough context specific information to support various technology-specific runtime environments and the generation of numerous context or platform-specific models as well as many other related source-code and other artifacts. The Service Data Objects 2.1 specification provides an extensible, lightweight runtime-available metadata API. It is through the SDO metadata API that the PlasmaSDO™ implementation provides more than just standard structural metadata elements, but for models annotated with this UML profile, provides numerous other context specific metadata elements instructive at build-time as well as run-time to various enterprise technology layers and various parts of the platform technology stack.
Table 1 - Plasma SDO Profile Package Detail
Name | Plasma SDO Profile |
Qualified Name | Plasma SDO Profile |
Description
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.
Table 2 - SDOAlias Stereotype Detail
Name | SDOAlias |
Qualified Name | Plasma SDO Profile::SDOAlias |
Visibility | public |
Abstract | false |
Base Stereotypes | |
Metaclass | UML Standard Profile::UML2 Metamodel::Classes::Kernel::NamedElement |
Following are the attributes for stereotype, SDOAlias.
Table 3 – SDOAlias Attribute Detail
Attribute Name | Description | Type | Cardinality | Visibility |
businessName | Associates a given UML element with a business specific, human readable name. | String | 1:0 | private |
localName | 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. | String | 1:0 | private |
physicalName | 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. | String | 1:0 | private |
Following are the relations for class, SDOAlias.
Table 5 – SDOAlias Relation Detail
Relation Type | Related Elements |
Extension | - NamedElement |
SDOAlias |
Description
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.
Table 2 - SDOConcurrent Stereotype Detail
Name | SDOConcurrent |
Qualified Name | Plasma SDO Profile::SDOConcurrent |
Visibility | public |
Abstract | false |
Base Stereotypes | |
Metaclass | UML Standard Profile::UML2 Metamodel::Classes::Kernel::Property |
Following are the attributes for stereotype, SDOConcurrent.
Table 3 – SDOConcurrent Attribute Detail
Attribute Name | Description | Type | Cardinality | Visibility |
dataFlavor | For a UML property, denotes or provides a hint as to the nature of the data with respect concurrency or concurrency control | ConcurentDataFlavor | 1:1 | private |
type | Specifies the general category of concurrency or concurrency control under which a UML property participates | ConcurrencyType | 1:1 | private |
Following are the relations for class, SDOConcurrent.
Table 5 – SDOConcurrent Relation Detail
Relation Type | Related Elements |
Extension | - Property |
SDOConcurrent |
Description
This UML stereotype is applied to a consumer UML named-element that is computed from the supplier element.
Table 2 - SDODerivation Stereotype Detail
Name | SDODerivation |
Qualified Name | Plasma SDO Profile::SDODerivation |
Visibility | public |
Abstract | false |
Base Stereotypes | |
Metaclass | UML Standard Profile::UML2 Metamodel::Classes::Kernel::NamedElement |
Following are the attributes for stereotype, SDODerivation.
Table 3 – SDODerivation Attribute Detail
Attribute Name | Description | Type | Cardinality | Visibility |
supplier | The supplier element or set of supplier elements which represent the derivation source. | NamedElement | 1:1 | private |
Following are the relations for class, SDODerivation.
Table 5 – SDODerivation Relation Detail
Relation Type | Related Elements |
Extension | - NamedElement |
SDODerivation |
Description
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.
Table 2 - SDODocumentation Stereotype Detail
Name | SDODocumentation |
Qualified Name | Plasma SDO Profile::SDODocumentation |
Visibility | public |
Abstract | false |
Base Stereotypes | |
Metaclass | UML Standard Profile::UML2 Metamodel::Classes::Kernel::Comment |
Following are the attributes for stereotype, SDODocumentation.
Table 3 – SDODocumentation Attribute Detail
Attribute Name | Description | Type | Cardinality | Visibility |
type | DocumentationType | 1:1 | private |
Following are the relations for class, SDODocumentation.
Table 5 – SDODocumentation Relation Detail
Relation Type | Related Elements |
Extension | - Comment |
SDODocumentation |
Description
This stereotype tags or annotates a UML enumeration for use within the PlasmaSDO™ implementation
Table 2 - SDOEnumeration Stereotype Detail
Name | SDOEnumeration |
Qualified Name | Plasma SDO Profile::SDOEnumeration |
Visibility | public |
Abstract | false |
Base Stereotypes | |
Metaclass | UML Standard Profile::UML2 Metamodel::Classes::Kernel::Enumeration |
Following are the attributes for stereotype, SDOEnumeration.
Table 3 – SDOEnumeration Attribute Detail
Attribute Name | Description | Type | Cardinality | Visibility |
Following are the relations for class, SDOEnumeration.
Table 5 – SDOEnumeration Relation Detail
Relation Type | Related Elements |
Extension | - Enumeration |
SDOEnumeration |
Description
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.
Table 2 - SDOEnumerationConstraint Stereotype Detail
Name | SDOEnumerationConstraint |
Qualified Name | Plasma SDO Profile::SDOEnumerationConstraint |
Visibility | public |
Abstract | false |
Base Stereotypes | |
Metaclass | UML Standard Profile::UML2 Metamodel::Classes::Kernel::Property |
Following are the attributes for stereotype, SDOEnumerationConstraint.
Table 3 – SDOEnumerationConstraint Attribute Detail
Attribute Name | Description | Type | Cardinality | Visibility |
value | The UML enumeration class with which to restrict a UML property. UML Enumerations used with this stereotype must be tagged with the SDOEnumeration stereotype. | Enumeration | 1:1 | private |
Following are the relations for class, SDOEnumerationConstraint.
Table 5 – SDOEnumerationConstraint Relation Detail
Relation Type | Related Elements |
Extension | - Property |
SDOEnumerationConstraint |
Description
This stereotype tags or annotates a UML property as representing some type of key within a data store, data transfer or transient storage medium.
Table 2 - SDOKey Stereotype Detail
Name | SDOKey |
Qualified Name | Plasma SDO Profile::SDOKey |
Visibility | public |
Abstract | false |
Base Stereotypes | |
Metaclass | UML Standard Profile::UML2 Metamodel::Classes::Kernel::Property |
Following are the attributes for stereotype, SDOKey.
Table 3 – SDOKey Attribute Detail
Attribute Name | Description | Type | Cardinality | Visibility |
type | Specifies the type of key | KeyType | 1:1 | private |
Following are the relations for class, SDOKey.
Table 5 – SDOKey Relation Detail
Relation Type | Related Elements |
Extension | - Property |
SDOKey |
Description
This stereotype tags or annotates a UML package as an SDO namespace.
Table 2 - SDONamespace Stereotype Detail
Name | SDONamespace |
Qualified Name | Plasma SDO Profile::SDONamespace |
Visibility | public |
Abstract | false |
Base Stereotypes | |
Metaclass | UML Standard Profile::UML2 Metamodel::Classes::Kernel::Package |
Following are the attributes for stereotype, SDONamespace.
Table 3 – SDONamespace Attribute Detail
Attribute Name | Description | Type | Cardinality | Visibility |
uri | 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. | String | 1:1 | private |
Following are the relations for class, SDONamespace.
Table 5 – SDONamespace Relation Detail
Relation Type | Related Elements |
Extension | - Package |
SDONamespace |
Description
Table 2 - SDOSemanticConstraint Stereotype Detail
Name | SDOSemanticConstraint |
Qualified Name | Plasma SDO Profile::SDOSemanticConstraint |
Visibility | public |
Abstract | false |
Base Stereotypes | |
Metaclass | UML Standard Profile::UML2 Metamodel::Classes::Kernel::Property |
Following are the attributes for stereotype, SDOSemanticConstraint.
Table 3 – SDOSemanticConstraint Attribute Detail
Attribute Name | Description | Type | Cardinality | Visibility |
conceptDomain | String | 1:0 | private | |
conceptId | String | 1:0 | private | |
conceptName | String | 1:0 | private |
Following are the relations for class, SDOSemanticConstraint.
Table 5 – SDOSemanticConstraint Relation Detail
Relation Type | Related Elements |
Extension | - Property |
SDOSemanticConstraint |
Description
Table 2 - SDOTemporal Stereotype Detail
Name | SDOTemporal |
Qualified Name | Plasma SDO Profile::SDOTemporal |
Visibility | public |
Abstract | false |
Base Stereotypes | |
Metaclass | UML Standard Profile::UML2 Metamodel::Classes::Kernel::Property |
Following are the attributes for stereotype, SDOTemporal.
Table 3 – SDOTemporal Attribute Detail
Attribute Name | Description | Type | Cardinality | Visibility |
state | TemporalState | 1:1 | private | |
type | TemporalType | 1:1 | private |
Following are the relations for class, SDOTemporal.
Table 5 – SDOTemporal Relation Detail
Relation Type | Related Elements |
Extension | - Property |
SDOTemporal |
Description
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.
Table 2 - SDOUniqueConstraint Stereotype Detail
Name | SDOUniqueConstraint |
Qualified Name | Plasma SDO Profile::SDOUniqueConstraint |
Visibility | public |
Abstract | false |
Base Stereotypes | |
Metaclass | UML Standard Profile::UML2 Metamodel::Classes::Kernel::Property |
Following are the attributes for stereotype, SDOUniqueConstraint.
Table 3 – SDOUniqueConstraint Attribute Detail
Attribute Name | Description | Type | Cardinality | Visibility |
group | Used to associate one or more UML properties within a class with a single constraint definition. | String | 1:0 | private |
Following are the relations for class, SDOUniqueConstraint.
Table 5 – SDOUniqueConstraint Relation Detail
Relation Type | Related Elements |
Extension | - Property |
SDOUniqueConstraint |
Description
Table 2 - SDOValueConstraint Stereotype Detail
Name | SDOValueConstraint |
Qualified Name | Plasma SDO Profile::SDOValueConstraint |
Visibility | public |
Abstract | false |
Base Stereotypes | |
Metaclass | UML Standard Profile::UML2 Metamodel::Classes::Kernel::Property |
Following are the attributes for stereotype, SDOValueConstraint.
Table 3 – SDOValueConstraint Attribute Detail
Attribute Name | Description | Type | Cardinality | Visibility |
fractionDigits | The number of fraction digits for the Property value must be below or equal to the specified total | Integer | 1:0 | private |
maxInclusive | Property value must be a number whose value must be lower or equal to the specified maximum | Integer | 1:0 | private |
maxLength | Property value must be below or equal to the specified maximum boundary | Integer | 1:0 | private |
minInclusice | Property value must be a number whose value must be higher or equal to the specificed minimum | Integer | 1:0 | private |
minLength | Property value must be above or equal to the specified minimum boundary | Integer | 1:0 | private |
pattern | The Property value must match the specified regular expression. The regular expression follows the Java regular expression conventions. | String | 1:0 | private |
totalDigits | The total number of digits for the Property value must be below or equal to the specified total | Integer | 1:0 | private |
Following are the relations for class, SDOValueConstraint.
Table 5 – SDOValueConstraint Relation Detail
Relation Type | Related Elements |
Extension | - Property |
SDOValueConstraint |
Description
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.
Table 2 - SDOValueSetConstraint Stereotype Detail
Name | SDOValueSetConstraint |
Qualified Name | Plasma SDO Profile::SDOValueSetConstraint |
Visibility | public |
Abstract | false |
Base Stereotypes | |
Metaclass | UML Standard Profile::UML2 Metamodel::Classes::Kernel::Property |
Following are the attributes for stereotype, SDOValueSetConstraint.
Table 3 – SDOValueSetConstraint Attribute Detail
Attribute Name | Description | Type | Cardinality | Visibility |
codingStrength | Indicates whether or not codes are restricted to those expressed in the value set | CodingStrength | 1:0 | private |
id | The globally unique identifier for the value set | String | 1:0 | private |
ignoredValueSetId | 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 | String | 1:0 | private |
minimumValueSetId | Defines the set of codes within the overall value set that must be supported by an implementer to be considered compliant | String | 1:0 | private |
name | The descriptive name associated with the value set | String | 1:0 | private |
rootCode | Allows conveying the root code of the value set. Only usable for key structural attributes. | String | 1:0 | private |
versionDate | The date on which a specific version of the value set was created. Used when performing static references to a value set |
String | private | |
versionIdentifier | The value which identifies a specific version of the value set. Used when performing static references to a value set |
String | private | |
versionTime | The time when a specific version of the value set was created. Used when performing static references to a value set |
String | 1:0 | private |
Following are the relations for class, SDOValueSetConstraint.
Table 5 – SDOValueSetConstraint Relation Detail
Relation Type | Related Elements |
Extension | - Property |
SDOValueSetConstraint |
Description
Defines whether the specified element is restricted to only using the identified coding system for the element
Table 9 - CodingStrength Detail
Name | CodingStrength |
Qualified Name | Plasma SDO Profile::CodingStrength |
Visibility | public |
Base Classifier |
Following are the literals for enumeration, CodingStrength.
Table 10 – CodingStrength Literal Detail
Literal Name | Description |
CNE | If not null, the element must be coded and must be drawn from the value set specified in the binding |
CWE | 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. |
Description
Specifies the nature of the data with respect to concurrency for a UML Property
Table 9 - ConcurentDataFlavor Detail
Name | ConcurentDataFlavor |
Qualified Name | Plasma SDO Profile::ConcurentDataFlavor |
Visibility | public |
Base Classifier |
Following are the literals for enumeration, ConcurentDataFlavor.
Table 10 – ConcurentDataFlavor Literal Detail
Literal Name | Description |
time | Indicates the data is temporal in nature typically reset to the system data or time for every successful update of the owning entity. |
user | Indicates the data represents a system username, typically reset to the current system user on successful update of the owning entity. |
version | Indicates the data is an integral version number, typically incremented for every successful update of the owning entity. |
Description
Indicates the category of concurrency or concurrency control strategy under which a UML Property participates.
Table 9 - ConcurrencyType Detail
Name | ConcurrencyType |
Qualified Name | Plasma SDO Profile::ConcurrencyType |
Visibility | public |
Base Classifier |
Following are the literals for enumeration, ConcurrencyType.
Table 10 – ConcurrencyType Literal Detail
Literal Name | Description |
optimistic | 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. |
origination | Indicates a UML Property stores origination information for its containing UML Class. Informs Data Access Services (DAS) performing concurrent operations involving origination. |
pessimistic | 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. |
Description
Table 9 - DocumentationType Detail
Name | DocumentationType |
Qualified Name | Plasma SDO Profile::DocumentationType |
Visibility | public |
Base Classifier |
Following are the literals for enumeration, DocumentationType.
Table 10 – DocumentationType Literal Detail
Literal Name | Description |
appendix | |
appInfo | |
definition | |
designComments | |
documentation | |
openIssues | |
other | |
rationale | |
references | |
requirements | |
usageNotes | |
walkthrough |
Description
This enumeration specifies the set of key types possible for any UML Property tagged with the SDOKey stereotype.
Table 9 - KeyType Detail
Name | KeyType |
Qualified Name | Plasma SDO Profile::KeyType |
Visibility | public |
Base Classifier |
Following are the literals for enumeration, KeyType.
Table 10 – KeyType Literal Detail
Literal Name | Description |
embedded | A key used as an internal identifier for the UML Class of the UML Property tagged with the SDOKey stereotype. |
primary | A key used as a primary identifier for the UML Class of the UML Property tagged with the SDOKey stereotype. |
Description
Table 9 - TemporalState Detail
Name | TemporalState |
Qualified Name | Plasma SDO Profile::TemporalState |
Visibility | public |
Base Classifier |
Following are the literals for enumeration, TemporalState.
Table 10 – TemporalState Literal Detail
Literal Name | Description |
actual | |
plan | |
proposal |
Description
Specifies the various notions of time which are relevant for temporal databases
Table 9 - TemporalType Detail
Name | TemporalType |
Qualified Name | Plasma SDO Profile::TemporalType |
Visibility | public |
Base Classifier |
Following are the literals for enumeration, TemporalType.
Table 10 – TemporalType Literal Detail
Literal Name | Description |
transaction | Transaction time is the time period during which a fact is stored in the database |
validEnd | Valid end time denotes the ending of a time period during which a fact is true with respect to the real world |
validStart | Valid start time denotes the beginning of a time period during which a fact is true with respect to the real world |
Description
This UML package contains UML data type definitions. The name of each UML data type maps directly to a Service Data Objects (SDO) 2.1 datatype found in the SDO 2.1.0 Specification. The term SDO data type refers to an SDO Type where isDataType() = true and where none of the types have any SDO Properties unless noted. Each UML class (data) attribute within a model intended to be used with PlasmaSDO, must have one of the SDO datatypes set as it’s UML type. The SDO Types are applicable across all languages mapped into SDO. For example the SDO Java Types are additional types specifically used in Java representing the object wrappers for primitive Java types. When an SDO Type is used in a mapping from another technology to SDO, implementations in Java specify one of the corresponding Java types. Each DataType has a String representation and may be converted to and from the String representation to its instance class, if that instance class is different from String. Numeric DataTypes have a precision in terms of a number of bits. For example, 32 bits signed indicates 1 sign bit and 31 value bits, with a range of -2^31 to 2^31-1. The String representation of DateTime, Duration, Time, Day, Month, MonthDay, Year, YearMonth, and YearMonthDay follows the lexical representation defined in XML Schema for the corresponding data types: dateTime, duration, time, gDay, gMonth, gMonthDay, gYear, gYearMonth, and Date respectively.
Table 1 - Plasma SDO Profile::datatypes Package Detail
Name | datatypes |
Qualified Name | Plasma SDO Profile::datatypes |
Description
This UML data type maps directly to the Service Data Objects (SDO) 2.1 Boolean data type. For language specific mappings for this data type, see the language-specific SDO 2.1.0 Specification.
Table 12 - Boolean Detail
Name | Boolean |
Qualified Name | Plasma SDO Profile::datatypes::Boolean |
Visibility | public |
Description
This UML data type maps directly to the Service Data Objects (SDO) 2.1 Byte data type. For language specific mappings for this data type, see the language-specific SDO 2.1.0 Specification.
Table 12 - Byte Detail
Name | Byte |
Qualified Name | Plasma SDO Profile::datatypes::Byte |
Visibility | public |
Description
This UML data type maps directly to the Service Data Objects (SDO) 2.1 Bytes data type. For language specific mappings for this data type, see the language-specific SDO 2.1.0 Specification.
Table 12 - Bytes Detail
Name | Bytes |
Qualified Name | Plasma SDO Profile::datatypes::Bytes |
Visibility | public |
Description
This UML data type maps directly to the Service Data Objects (SDO) 2.1 Character data type. For language specific mappings for this data type, see the language-specific SDO 2.1.0 Specification.
Table 12 - Character Detail
Name | Character |
Qualified Name | Plasma SDO Profile::datatypes::Character |
Visibility | public |
Description
This UML data type maps directly to the Service Data Objects (SDO) 2.1 Date data type. For language specific mappings for this data type, see the language-specific SDO 2.1.0 Specification.
Table 12 - Date Detail
Name | Date |
Qualified Name | Plasma SDO Profile::datatypes::Date |
Visibility | public |
Description
This UML data type maps directly to the Service Data Objects (SDO) 2.1 DateTime data type. For language specific mappings for this data type, see the language-specific SDO 2.1.0 Specification.
Table 12 - DateTime Detail
Name | DateTime |
Qualified Name | Plasma SDO Profile::datatypes::DateTime |
Visibility | public |
Description
This UML data type maps directly to the Service Data Objects (SDO) 2.1 Day data type. For language specific mappings for this data type, see the language-specific SDO 2.1.0 Specification.
Table 12 - Day Detail
Name | Day |
Qualified Name | Plasma SDO Profile::datatypes::Day |
Visibility | public |
Description
This UML data type maps directly to the Service Data Objects (SDO) 2.1 Decimal data type. For language specific mappings for this data type, see the language-specific SDO 2.1.0 Specification.
Table 12 - Decimal Detail
Name | Decimal |
Qualified Name | Plasma SDO Profile::datatypes::Decimal |
Visibility | public |
Description
This UML data type maps directly to the Service Data Objects (SDO) 2.1 Decimal data type. For language specific mappings for this data type, see the language-specific SDO 2.1.0 Specification.
Table 12 - Double Detail
Name | Double |
Qualified Name | Plasma SDO Profile::datatypes::Double |
Visibility | public |
Description
This UML data type maps directly to the Service Data Objects (SDO) 2.1 Duration data type. For language specific mappings for this data type, see the language-specific SDO 2.1.0 Specification.
Table 12 - Duration Detail
Name | Duration |
Qualified Name | Plasma SDO Profile::datatypes::Duration |
Visibility | public |
Description
This UML data type maps directly to the Service Data Objects (SDO) 2.1 Float data type. For language specific mappings for this data type, see the language-specific SDO 2.1.0 Specification.
Table 12 - Float Detail
Name | Float |
Qualified Name | Plasma SDO Profile::datatypes::Float |
Visibility | public |
Description
This UML data type maps directly to the Service Data Objects (SDO) 2.1 Int data type. For language specific mappings for this data type, see the language-specific SDO 2.1.0 Specification.
Table 12 - Int Detail
Name | Int |
Qualified Name | Plasma SDO Profile::datatypes::Int |
Visibility | public |
Description
This UML data type maps directly to the Service Data Objects (SDO) 2.1 Integer data type. For language specific mappings for this data type, see the language-specific SDO 2.1.0 Specification.
Table 12 - Integer Detail
Name | Integer |
Qualified Name | Plasma SDO Profile::datatypes::Integer |
Visibility | public |
Description
This UML data type maps directly to the Service Data Objects (SDO) 2.1 Long data type. For language specific mappings for this data type, see the language-specific SDO 2.1.0 Specification.
Table 12 - Long Detail
Name | Long |
Qualified Name | Plasma SDO Profile::datatypes::Long |
Visibility | public |
Description
This UML data type maps directly to the Service Data Objects (SDO) 2.1 Month data type. For language specific mappings for this data type, see the language-specific SDO 2.1.0 Specification.
Table 12 - Month Detail
Name | Month |
Qualified Name | Plasma SDO Profile::datatypes::Month |
Visibility | public |
Description
This UML data type maps directly to the Service Data Objects (SDO) 2.1 MonthDay data type. For language specific mappings for this data type, see the language-specific SDO 2.1.0 Specification.
Table 12 - MonthDay Detail
Name | MonthDay |
Qualified Name | Plasma SDO Profile::datatypes::MonthDay |
Visibility | public |
Description
This UML data type maps directly to the Service Data Objects (SDO) 2.1 Object data type. For language specific mappings for this data type, see the language-specific SDO 2.1.0 Specification.
Table 12 - Object Detail
Name | Object |
Qualified Name | Plasma SDO Profile::datatypes::Object |
Visibility | public |
Description
This UML data type maps directly to the Service Data Objects (SDO) 2.1 Short data type. For language specific mappings for this data type, see the language-specific SDO 2.1.0 Specification.
Table 12 - Short Detail
Name | Short |
Qualified Name | Plasma SDO Profile::datatypes::Short |
Visibility | public |
Description
This UML data type maps directly to the Service Data Objects (SDO) 2.1 String data type. For language specific mappings for this data type, see the language-specific SDO 2.1.0 Specification.
Table 12 - String Detail
Name | String |
Qualified Name | Plasma SDO Profile::datatypes::String |
Visibility | public |
Description
This UML data type maps directly to the Service Data Objects (SDO) 2.1 Strings data type. For language specific mappings for this data type, see the language-specific SDO 2.1.0 Specification.
Table 12 - Strings Detail
Name | Strings |
Qualified Name | Plasma SDO Profile::datatypes::Strings |
Visibility | public |
Description
This UML data type maps directly to the Service Data Objects (SDO) 2.1 Time data type. For language specific mappings for this data type, see the language-specific SDO 2.1.0 Specification.
Table 12 - Time Detail
Name | Time |
Qualified Name | Plasma SDO Profile::datatypes::Time |
Visibility | public |
Description
This UML data type maps directly to the Service Data Objects (SDO) 2.1 URI data type. For language specific mappings for this data type, see the language-specific SDO 2.1.0 Specification.
Table 12 - URI Detail
Name | URI |
Qualified Name | Plasma SDO Profile::datatypes::URI |
Visibility | public |
Description
This UML data type maps directly to the Service Data Objects (SDO) 2.1 Year data type. For language specific mappings for this data type, see the language-specific SDO 2.1.0 Specification.
Table 12 - Year Detail
Name | Year |
Qualified Name | Plasma SDO Profile::datatypes::Year |
Visibility | public |
Description
This UML data type maps directly to the Service Data Objects (SDO) 2.1 YearMonth data type. For language specific mappings for this data type, see the language-specific SDO 2.1.0 Specification.
Table 12 - YearMonth Detail
Name | YearMonth |
Qualified Name | Plasma SDO Profile::datatypes::YearMonth |
Visibility | public |
Description
This UML data type maps directly to the Service Data Objects (SDO) 2.1 YearMonthDay data type. For language specific mappings for this data type, see the language-specific SDO 2.1.0 Specification.
Table 12 - YearMonthDay Detail
Name | YearMonthDay |
Qualified Name | Plasma SDO Profile::datatypes::YearMonthDay |
Visibility | public |
Description
Description
Description
Description
Description