Results for area 2.3 Variables, data and protocols
association where the target class is an aggregate; therefore the source class is a part
NOTE 1 to entry This characteristic is expressed in UML with an attribute named “aggregation” on the target side Association End being set to “aggregate”
NOTE 1 to entry It is additional information about a piece of data (element). Often attributes are used to pass information about the element and hence can be said to provide metadata for the element. An attribute is a value indicator (=) and the attribute value is specified within the tag (i.e. <H3 align=""centre"">). Attribute in XML is a name=""value"" pair that can be placed in the start tag of an element. For XML, all values have to be quoted with single or double quotes.
association that connects exactly two classes
string consisting of one or more words, where each word within the string, except for the first, starts with an upper-case letter and all other letters are lowercase; the words follow each other without any
space; hyphens and numbers may be used, but the first character of the string must be a lower case alphabetic character; a hyphen may not be the last character or occur multiple times in sequence
string of one or more words where each word within the string starts with an upper-case letter and the remainder of each word is in lowercase; the words follow each other without any space; hyphens and numbers may be used, but the first character of the string must be an upper case alphabetic character; a hyphen may not be the last character or occur multiple times in sequence
data element, class, value domain, data frame, message or interface dialogue defined, at a minimum, with an unambiguous identifier and a definition
NOTE 1 to entry In order to exchange a value corresponding to a data concept, more information than an identifier, a name and a definition can be needed. For a property, a data type is needed. Depending on the kind of property, other data elements such as unit of measure, and language, can be needed as well. The additional information can be given in the data dictionary, in a data specification that references the data concept or associated with the data themselves.
collection of data concepts that allows lookup by entity identifier
<XML> create new types (both simple and complex)
<UML> diagram that shows a collection of declarative (static) model elements, such as classes, types, and their contents and relationships
XML document that conforms to a schema
EXAMPLE If the schema is WSDL, the XML document is an WSDL instance document.
formal set of production rules that comprise a grammar defining language, such as XML
XML based specification for the interoperable exchange of metadata
NOTE It is today most commonly used to exchange UML models between UML tools. XMI is specified in ISO/IEC 19503:2005.
Identifier that is unique in and time, i.e. no other object will ever have the same identifier at any other place and at any time
identifier that uniquely identifies the document
instance of an object identifier type which relates to an associated module
NOTE In ISO/IEC 8824 a module identifier is defined as: ModuleIdentifier::= modulereference DefinitiveIdentifier If the “DefinitiveIdentifier” is not empty, the denoted object identifier value unambiguously and uniquely identifies the module being defined. No defined value may be used in defining the object identifier value.
globally unique value associated with an object to unambiguously identify it
reference identifiers which relate to prescribed Sub Modules determined in subordinate Standards
IRI compact string of characters for identifying an abstract or physical resource
scheme for the arrangement or division of objects into groups by functional area
association where the target class is a composite; therefore the source class is a part that is strongly owned by the composite and may not be part of any other composite
NOTE This characteristic is expressed in UML with an attribute named “aggregation” on the target side Association End being set to “composite”.
<UML> endpoint of an association, which connects the association to a classifier
individual occurrence of a data concept
<XML> set of valid literals for a data type
documenting characteristic of a data concept that is stored in a data dictionary
<XML> set of unique identifiers
NOTE 1 to entry Namespace is a mechanism to resolve naming conflicts between elements in an XML document when each comes from a different vocabulary. It allows the commingling of like tag names from different namespaces. A namespace identifies an XML vocabulary defined within a URN. An attribute on an element, attribute, or entity reference associates a short name with the URN that defines the namespace; that short name is then used as a prefix to the element, attribute, or entity reference name to uniquely identify the namespace.
Namespace references have scope. All child nodes beneath the node that specifies the namespace inherit that namespace. This allows nonqualified names to use the default namespace.
data concept that contains the formal syntactic definition, and optionally the semantic definition, of a defined set of other data concepts that are all version-controlled as a single unit; a module can be represented in multiple languages (e.g., ASN.1 or XML Schema) and compiled by computer systems
object class that the data concept describes
indexical term used by humans as a means of identifying data elements and other data concepts
name of a data concept expressed as a valid “typereference” as defined by ISO/IEC 8824-1
identifier that represents a version number that the data concept is more generally known by
inter ORB protocol that defines the message formats between ORBs in a distributed environment
<UML> semantic condition or restriction
NOTE 1 to entry Certain constraints are predefined in the UML, others may be user defined. Constraints are one of three extensibility mechanisms in UML.
notation which can be used in association with a type, to define a subtype of that type
graphical section of a UML class box positioned directly under the class name compartment
mechanism that allows metaclasses from existing metamodels to be extended to adapt them for different purposes
expression of what a stakeholder wants the ITS implementation to provide, usually written in the language of the stakeholder and thus possibly having little or no formal structure
NOTE There could be many aspirations for each ITS implementation, depending on its scope and the number of stakeholders that are involved.
atomic constituent of the UML model logical data structure within an XML document, a piece of data within a file [XML]
NOTE An XML element consists of a start tag, and end tag, and the information between the tags, which is often referred to as the contents. Start tags and end tags show the beginning and end of an element. A schema that can provide a description of the structure of the data describes elements used in an XML file.
<XML> short name to uniquely identify the namespace profile
<UML> stereotyped package that contains model elements, which have been customized for a specific domain or purpose using extension mechanisms, such as stereotypes, tagged definitions and constraints
NOTE 1 to entry A profile may also specify model libraries on which it depends and the metamodel subset that it extends.
string of the lower case application/toolkit abbreviation as defined in the UML tagged value “ApplicationAbbreviation”
information flow from a physical object acting as an information provider and sent to another physical object acting as an information consumer
NOTE 1 to entry The term “information flow triple” is used extensively in the Architecture Reference for Cooperative and Intelligent Transportation (ARC-IT; see Reference [25]).
type which is used only for defining the value and subtype notation for a type
NOTE Associated types are defined when it is necessary to make it clear that there may be a significant difference between how the type is defined in ASN.1 and how it is encoded. Associated types do not appear in user specifications.
an identifier for a component of an architecture which indicates the component shall be elaborated in a subsequent architecture
integer that represents the number of edits that have been made to the data concept since the last update to the major version number
<XML, UML> system of representing an information model that defines the data’s elements and attributes
definition of the content and structure of data using an ASN.1 type definition
a formal description of the allowed content of an XML document that claims compliance to the schema
NOTE 1 to entry XML Schema Definitions allow for formal validation of syntactical compliance of instance documents.
electronic data dictionary that follows precise documented rules for the registration and management of stored data concepts
NOTE 1 to entry The data concept registry contains meta-attributes about data concepts in terms of their names and representational forms as well as the semantics associated with the data concepts. A data concept registry may contain metadata that assists information interchange and re-use, both from the perspective of human users and for machine-interpretation of data concepts.
NOTE 2 to entry A data concept registry typically includes advanced features for adding retrieving, and working with its contents.
<UML> new type of modelling element that extends the semantics of the metamodel
NOTE 1 to entry Stereotypes have to be based on certain existing types or classes in the metamodel. Stereotypes may extend the semantics, but not the structure of pre-existing types and classes. Certain stereotypes are predefined in the UML, others may be user defined. Stereotypes are one of three extensibility mechanisms in UML.
NOTE 2 to entry The stereotype may specify additional constraints and tag definitions that apply to model elements. In addition, a stereotype may be used to indicate a difference in meaning or usage between two model elements with identical structure.
<UML> explicit definition of a property as a name-value pair
NOTE 1 to entry Certain tags are predefined in the UML; others MAY be user defined. Tagged values are one of three extensibility mechanisms in UML.
NOTE 2 to entry In a tagged value, the name is referred as the tag.
<UML> description of a set of objects that share the same attributes, operations, methods, relationships, and semantics
data type (or type for short) that represents in a formalised way a class of information (for example, numerical, textual, still image or video information); the representation is conformant to definitions given in ISO/IEC 8824-1
simple type whose values are the set of all object identifiers allocated in accordance with the rules of the ISO/IEC 9834 series
type definition that does not conform to ISO/IEC 8824
integer that represents the number of normative changes that have been made to approved versions of
the associated data concept
types defined by directly specifying the set of its values
data element that cannot be further subdivided meaningfully within the context of ASN.1
<XML> identification of element types and structure within a document
NOTE 1 to entry The mark-up is not actually part of the content, but identifies the components and their roles.
inter ORB protocol that allows ORBs to use the Internet as a communications bus by mapping inter ORB messages onto TCP/IP