This XML Schema Definition (XSD) defines syntax with concrete semantics for describing space or remote device telemetry and commanding in a platform and program independent manner. The top-level SpaceSystem is the root element for the set of metadata necessary to monitor and command a space device, such as a satellite. A SpaceSystem defines a namespace. Metadata areas include: packets/minor frames layout, telemetry, calibration, alarm, algorithms, streams and commands. A SpaceSystem may have child SpaceSystems, forming a SpaceSystem tree. See SpaceSystemType. This key ensures a unique parameter name at the system level. This key ensures a unique parameter type name at the system level. This key ensures a unique metaCommand name at the system level. This key ensures a unique algorithm name at the system level. This key ensures a unique stream name at the system level. This key ensures a unique service name at the system level. This key ensures a container stream name at the system level. This key ensures a unique argument type name at the system level. This key ensures a unique BlockMetaCommand name at the system level. SpaceSystem is a collection of SpaceSystem(s) including space assets, ground assets, multi-satellite systems and sub-systems. A SpaceSystem is the root element for the set of data necessary to monitor and command an arbitrary space device - this includes the binary decomposition the data streams going into and out of a device. The Header element contains optional descriptive information about this SpaceSystem or the document as a whole when specified at the root SpaceSystem. This element contains descriptions of the telemetry created on the space asset/device and sent to other data consumers. This element contains descriptions of the commands and their associated constraints and verifications that can be sent to the space asset/device. Additional SpaceSystem elements may be used like namespaces to segregate portions of the space asset/device into convenient groupings or may be used to specialize a product line generic SpaceSystem to a specific asset instance. Optional descriptive attribute for document owner convenience. Describe command related metadata. Items defined in this area may refer to items defined in TelemetryMetaData. See TelemetryMetaDataType. A list of parameter types. Parameters referenced by MetaCommands. This Parameter Set is located here so that MetaCommand data can be built independently of TelemetryMetaData. A list of argument types. MetaCommand definitions can contain arguments and parameters. Arguments are user provided to the specific command definition. Parameters are provided/calculated/determined by the software creating the command instance. As a result, arguments contain separate type information. In some cases, arguments have different descriptive characteristics. A list of command definitions with their arguments, parameters, and container encoding descriptions. Similar to the ContainerSet for telemetry, the CommandContainerSet contains containers that can be referenced/shared by MetaCommand definitions. Contains an unordered set of Streams. Contains an unordered set of Algorithms. All the data about telemetry is contained in TelemetryMetaData A list of parameter types A list of Parameters for this Space System. Holds the list of all potential container definitions for telemetry. Containers may parts of packets or TDM, and then groups of the containers, and then an entire entity -- such as a packet. In order to maximize re-used for duplication, the pieces may defined once here, and then assembled as needed into larger structures, also here. Messages are an alternative method of uniquely identifying containers within a Service. A message provides a test in the form of MatchCriteria to match to a container. A simple example might be: [When minorframeID=21, the message is the 21st minorframe container. The collection of messages to search thru will be bound by a Service. This schema defines the dictionary for containers, which in turn describe the physical composition of data in a communication system Identical to ArgumentRefEntryType but supports argument instance references. Identical to ArrayParameterRefEntryType but supports argument instance references. Only used for subsetting an array. The array's true dimension sizes are set in the Type. The dimension here if used for subsetting must be less than the ones in the type. It's not a subset if its the same size. Identical to ArrayParameterRefEntryType but supports argument instance references. Only used for subsetting an array. The array's true dimension sizes are set in the Type. The dimension here if used for subsetting must be less than the ones in the type. It's not a subset if its the same size. Identical to ContainerRefEntryType but supports argument instance references. Identical to ContainerSegmentRefEntryType but supports argument instance references. Identical to FixedValueEntryType but supports argument instance references. An optional name for the fixed/constant field in the sequence. The fixed/constant value that should be encoded into the sequence. This value provided should have sufficient bit length to accomodate the size in bits. If the value is larger, the most significant unnecessary bits are dropped. The value provided should be in network byte order for encoding. The number of bits that this fixed/constant value should occupy in the sequence. Identical to IndirectParameterRefEntryType but supports argument instance references. Identical to ParameterRefEntryType but supports argument instance references. Identical to ParameterSegmentRefEntryType but supports argument instance references. Identical to StreamRefEntryType but supports argument instance references. Describe an entry that is an array parameter. Specify the dimension sizes if you subsetting the array (the number of dimensions shall match the number defined in the parameter’s type definition), otherwise the ones in the ParameterType are assumed. See SequenceEntryType. Only used for subsetting an array. The array's maximum dimension sizes are set in the type. When a DimensionList is not used, the array is the full size provided in the type. The dimension here if used for subsetting must be less than the ones in the type. It's not a subset if its the same size. Supplies an optional non-reference-able name and short description for alarms. Also includes an optional ancillary data for any special local flags, note that these may not necessarily transfer to another recipient of an instance document. The alarm definition may be named. An optional brief description of this alarm definition. Describe a child/parent container inheritance relationship. Describe constraints with RestrictionCriteria, conditions that must be true for this container to be an extension of the parent container. A constraint can be used to convey the identifying features of the telemetry format such as the CCSDS application id or minor-frame id. See RestrictionCriteriaType and SequenceContainerType. Contains the conditions that must evaluate to true in order for this container to be an extension of the parent container. Reference to the container that this container extends. An abstract block of data; used as the base type for more specific container types RateInStream is used to: a) generate alarms when the Container is updated too frequently or too infrequently, b) provide some 'guidelines' for generating forward link containers, c) provide some guidelines for spacecraft simulators to generate telemetry containers. If necessary, these rates may be defined on a per stream basis. The software should check that any Stream names referenced in the RateInStreamSet actually exist. May be used to indicate error detection and correction, change byte order, provide the size (when it can't be derived), or perform some custom processing. Holds a reference to a container name of container An entry that is simply a reference to another container. An entry that is only a portion of a container indicating that the entire container must be assembled from other container segments. It is assumed that container segments happen sequentially in time, that is the first part of a container is first, however (and there's always a however), if this is not the case the order of this container segment may be supplied with the order attribute where the first segment order="0". Each instance of a container cannot overlap in the overall sequence with another instance Unordered Set of Containers SequenceContainers define sequences of parameters or other containers. Contains an ordered list of Entries. Used in Sequence Container Specify a Parameter to be a part of this container layout definition. Specify a portion of a Parameter to be a part of this container layout definition. This is used when the Parameter is reported in fractional parts in the container before being fully updated. Specify the content of another Container to be a part of this container layout definition. Specify a portion of another Container to be a part of this container layout definition. Specify a portion of a Stream to be a part of this container layout definition. Specify a previous (not last reported) value of a Parmeter to be a part of this container layout definition. Specify an Array Type Parameter to be a part of this container layout definition when the Container does not populate the entire space of the Array contents. If the entire space of the Array is populated, a tolerant implementation will accept ParameterRefEntry also. An entry whose name is given by the value of a ParamameterInstance. This entry may be used to implement dwell telemetry streams. The value of the parameter in ParameterInstance must use either the name of the Parameter or its alias. If it's an alias name, the alias namespace is supplied as an attribute. Describe the absolute or relative bit location of an entry in a container. The "referenceLocation" attribute specifies the starting bit anchor. If no referenceLocation value is given, the entry is assumed to begin at the first bit position after the previous entry. Each container starts at bit 0, thus "containerStart" is an offset from 0. Negative container start bits are before the container and are implementation dependent – these should be flagged as likely errors. "containerEnd" is given as a positive offset from the end of the container, thus a container end of 0 is exactly at the end of the container. Negative container end addresses are after the container and are implementation dependent – these should be flagged as likely errors. Positive "previouEntry" values are offsets from the previous entry – zero (0) is the default which means it follows contiguously from the last occupied bit of the previous entry. A value of one means it is offset 1-bit from the previous entry, and a value of negative 1 (-1) means it overlaps the previous entry by one bit, and so forth. The "nextEntry" attribute value is proposed for deprecation and should be avoided. See SequenceEntryType. Defines the relative reference used to interpret the start bit position. The default is 0 bits from the end of the previousEntry, which makes the entry contiguous. Identical to LocationInContainerInBitsType but supports argument instance references. Holds a reference to a message name of message An entry that is a single Parameter An entry that is only a portion of a parameter value indicating that the entire parameter value must be assembled from other parameter segments. It is assumed that parameter segments happen sequentially in time, that is the first part if a telemetry parameter first, however (and there's always a however), if this is not the case the order of this parameter segment may be supplied with the order attribute where the first segment order="0". Describes the binary layout/packing of data and also related properties, including an entry list of parameters, parameter segments, array parameters, stream segments, containers, and container segments. Sequence containers may extend other sequence containers (see BaseContainerType). The parent container’s entries are placed before the entries in the child container forming one entry list. An inheritance chain may be formed using this mechanism, but only one entry list is being created. Sequence containers may be marked as "abstract", when this occurs an instance of it cannot itself be created. The idle pattern is part of any unallocated space in the container. See EntryListType. List of item entries to pack/encode into this container definition. Optional inheritance for this container from another named container. Abstract container definitions that are not instantiated, rather only used as bases to inherit from to create specialized container definitions. The idle pattern is part of any unallocated space in the container. This is uncommon. Defines an abstract schema type used to create other entry types. Describe an entry’s location in the container (See LocationInContainerInBitsType). The location may be fixed or dynamic, absolute or relative. Entries may be included depending on the value of a condition (See IncludeConditionType), and entries may also repeat (see RepeatEntryType). The entry’s IncludeCondition resolves to true, it is fully-resolved when its size is computable after RepeatEntry has been accounted for and then offset by LocationInContainer. See EntryListType, IncludeConditionType, RepeatEntryType and LocationInContainerInBitsType. The start bit 0 position for each container is local to the container, but does include space occupied by inherited containers. When a container is "included", as opposed to inherited, then the interpreting implementation takes into account the start bit position of the referring container when finally assembling the start bits for the post-processed entry content. The default start bit for any entry is 0 bits from the previous entry, making the content contiguous when this element is not used. May be used when this entry repeats itself in the sequence container. When an entry repeats, it effectively specifies that the same entry is reported more than once in the container and has the same physical meaning. This should not be construed to be equivalent to arrays. This entry will only be included in the sequence when this condition is true, otherwise it is always included. When the include condition evaluates to false, it is as if the entry does not exist such that any start bit interpretations cannot take into account the space that would have been occupied if this included condition were true. Optional timing information associated with this entry. Optional ancillary data associated with this element. Optional short description for this entry element. Identical to a SequenceEntryType but supports argument instance references. The start bit 0 position for each container is local to the container, but does include space occupied by inherited containers. When a container is "included", as opposed to inherited, then the interpreting implementation takes into account the start bit position of the referring container when finally assembling the start bits for the post-processed entry content. The default start bit for any entry is 0 bits from the previous entry, making the content contiguous when this element is not used. May be used when this entry repeats itself in the sequence container. When an entry repeats, it effectively specifies that the same entry is reported more than once in the container and has the same physical meaning. This should not be construed to be equivalent to arrays. This entry will only be included in the sequence when this condition is true, otherwise it is always included. When the include condition evaluates to false, it is as if the entry does not exist such that any start bit interpretations cannot take into account the space that would have been occupied if this included condition were true. Ancillary data associated with this entry. Optional short description for this entry element. Holds a set of services, logical groups of containers OR messages (not both). An entry that is a portion of a stream (streams are by definition, assumed continuous) It is assumed that stream segments happen sequentially in time, that is the first part if a steam first, however, if this is not the case the order of the stream segments may be supplied with the order attribute where the first segment order="0". The ContainerRef should point to ROOT container that will describe an entire packet/minor frame or chunk of telemetry. Define the expected appearance (rate) of a container in a stream where the rate is defined on either a perSecond or perContainer update basis. Many programs and platforms have variable reporting rates for containers and these can be commanded. As a result, this element is only useful to some users and generally does not affect the processing of the received containers themselves. See ContainerType. The measurement unit basis for the minimum and maximum appearance count values. The minimum rate for the specified basis for which this container should appear in the stream. The maximum rate for the specified basis for which this container should appear in the stream. Define the expected appearance (rate) of a container in a named stream where the rate is defined on either a perSecond or perContainer update basis. Many programs and platforms have variable reporting rates for containers and these can be commanded. As a result, this element is only useful to some users and generally does not affect the processing of the received containers themselves. See ContainerType and RateInStreamType. Reference to a named stream for which this rate specification applies. The location may be relative to the start of the container (containerStart), relative to the end of the previous entry (previousEntry), relative to the end of the container (containerEnd), or relative to the entry that follows this one (nextEntry). If going forward (containerStart and previousEntry) then the location refers to the start of the Entry. If going backwards (containerEnd and nextEntry) then, the location refers to the end of the entry. Define one or more conditions (constraints) for container inheritance. A container is instantiable if its constraints are true. Constraint conditions may be a comparison, a list of comparisons, a boolean expression, or a graph of containers that are instantiable (if all containers are instantiable the condition is true). See BaseContainerType, ComparisonType, ComparisonListType, BooleanExpressionType and NextContainerType. Reference to the named container that must follow this container in the stream sequence. This schema defines the dictionary for telemetry Describe an absolute time parameter type relative to a known epoch (such as TAI). The string representation of this time should use the [ISO 8601] extended format CCYY-MM-DDThh:mm:ss where "CC" represents the century, "YY" the year, "MM" the month and "DD" the day, preceded by an optional leading "-" sign to indicate a negative number. If the sign is omitted, "+" is assumed. The letter "T" is the date/time separator and "hh", "mm", "ss" represent hour, minute and second respectively. Additional digits can be used to increase the precision of fractional seconds if desired i.e. the format ss.ss... with any number of digits after the decimal point is supported. See TAIType, IntegerDataEncoding and AbsoluteTimeDataType. Describe a complex data type analogous to a C-struct. Each field of the data type is called a Member. Each Member is part of the MemberList which forms the list of items to be placed under this data type’s name. The MemberList defines a data block and block’s size is defined by the DataEncodings of each Member’s type reference. The data members are ordered and contiguous in the MemberList element (packed). Each member may be addressed by the dot syntax similar to C such as P.voltage if P is the referring parameter and voltage is of a member of P’s aggregate type. See MemberType, MemberListType, DataEncodingType, NameReferenceType, and AggregateDataType. Describe an array parameter type. The size and number of dimensions are described here. See ArrayParameterRefEntryType, NameReferenceType and ArrayDataType. Describe the dimensions of this array. Describe a binary engineering/calibrated parameter type (sometimes called a “blob type”). It may be of fixed or variable length, and has an optional encoding and decoding algorithm that may be defined to transform the data between space and ground. See BinaryDataEncodingType, IntegerValueType, InputAlgorithmType and BinaryDataType. Optionally describe an alarm monitoring specification that is effective whenever a contextual alarm definition does not take precedence. Optionally describe one or more alarm monitoring specifications that are effective whenever a contextual match definition evaluates to true. The first match that evaluates to true takes precedence. Describe a boolean parameter type which has two values only: ‘True’ (1) or ‘False’ (0). The values one and zero may be mapped to a specific string using the attributes oneStringValue and zeroStringValue. This type is a simplified form of the EnumeratedDataType. See IntegerDataEncoding and BooleanDataType. Optionally describe an alarm monitoring specification that is effective whenever a contextual alarm definition does not take precedence. Optionally describe one or more alarm monitoring specifications that are effective whenever a contextual match definition evaluates to true. The first match that evaluates to true takes precedence. Describe an enumerated parameter type. The enumeration list consists of label/value pairs. See EnumerationListType, IntegerDataEncodingType and EnumeratedDataType. Describe labels for this parameter that should be in an alarm state. The default definition applies when there are no context alarm definitions or all the context alarm definitions evaluate to false in their matching criteria. Describe labels for this parameter that should be in an alarm state when another parameter and value combination evaluates to true using the described matching criteria. Describe an ordered collection of context enumeration alarms, duplicates are valid. Process the contexts in list order. See EnumerationContextAlarmType. Describe the alarm matching context criteria and the alarm definition itself. Describe a floating point parameter type. Several encodings are supported. Calibrated integer to float relationships should be described with this data type. Use the data encoding to define calibrators. Joins integer as one of the numerics. See FloatDataEncodingType, IntegerDataEncodingType and FloatDataType. Default alarm definitions are those which do not adjust definition logic based on the value of other parameters. Other parameters may participate in the determination of an alarm condition for this parameter, but the definition logic of the alarm on this parameter is constant. If the alarming logic on this parameter changes based on the value of other parameters, then it is a ContextAlarm and belongs in the ContextAlarmList element. Context alarm definitions are those which adjust the definition logic for this parameter based on the value of other parameters. A context which evaluates to being in effect, based on the testing of another parameter, takes precedence over the default alarms in the DefaultAlarm element. If the no context alarm evaluates to being in effect, based on the testing of another parameter, then the default alarm definitions from the DefaultAlarm element will remain in effect. If multiple contexts evaluate to being in effect, then the first one that appears will take precedence. Describe an integer parameter type. Several are supported. Calibrated integer to integer relationships should be described with this data type. Use the integer data encoding to define calibrators. Joins float as one of the numerics. See IntegerDataEncoding and IntegerDataType. Default alarm definitions are those which do not adjust definition logic based on the value of other parameters. Other parameters may participate in the determination of an alarm condition for this parameter, but the definition logic of the alarm on this parameter is constant. If the alarming logic on this parameter changes based on the value of other parameters, then it is a ContextAlarm and belongs in the ContextAlarmList element. Context alarm definitions are those which adjust the definition logic for this parameter based on the value of other parameters. A context which evaluates to being in effect, based on the testing of another parameter, takes precedence over the default alarms in the DefaultAlarm element. If the no context alarm evaluates to being in effect, based on the testing of another parameter, then the default alarm definitions from the DefaultAlarm element will remain in effect. If multiple contexts evaluate to being in effect, then the first one that appears will take precedence. An ordered collection of numeric alarms associated with a context. A context is an alarm definition on a parameter which is valid only in the case of a test on the value of other parameters. Process the contexts in list order. Used by both FloatParameterType and IntegerParameterType. See NumericContextAlarmType. A contextual alarm definition for the parameter that uses this type that is valid when a test against the value of one or more other parameters evaluates to true. A reference to an instance of a Parameter. Used when the value of a parameter is required for a calculation or as an index value. A positive value for instance is forward in time, a negative value for count is backward in time, a 0 value for count means use the current value of the parameter or the first value in a container. Describes extended properties/attributes of Parameter definitions. Optional. Normally used when the database is built in a flat, non-hierarchical format. Optional condition that must be true for this Parameter to be valid. When present, this set of elements describes physical address location(s) of the parameter where it is stored. Typically this is on the data source, although that is not constrained by this schema. This time will override any Default value for TimeAssociation. This attribute describes the nature of the source entity for which this parameter receives a value. Implementations assign different attributes/properties internally to a parameter based on the anticipated data source. A Parameter marked as 'readOnly' true is non-settable by users and applications/services that do not represent the data source itself. Note that a slight conceptual overlap exists here between the 'dataSource' attribute and this attribute when the data source is 'constant'. For a constant data source, then 'readOnly' should be 'true'. Application implementations may choose to implicitly enforce this. Some implementations have both concepts of a Parameter that is settable or non-settable and a Constant in different parts of their internal data model. A Parameter marked to persist should retain the latest value through resets/restarts to the extent that is possible or defined in the implementation. The net effect is that the initial/default value on a Parameter is only seen once or when the system has a reset to revert to initial/default values. Describe the properties of a telemetry parameter, including its data type (parameter type). The bulk of properties associated with a telemetry parameter are in its parameter type. The initial value specified here, overrides the initial value in the parameter type. A parameter may be local, in which case its parameter type would have no data encodings. Ideally such a definition would also set data source in parameter properties to ‘local’ but the syntax does not enforce this. See BaseDataType, BaseTimeDataType, and NameReferenceType. Specify additional properties for this Parameter used by the implementation of tailor the behavior and attributes of the Parameter. When not specified, the defaults on the ParameterProperties element attributes are assumed. Specify the reference to the parameter type from the ParameterTypeSet area using the path reference rules, either local to this SpaceSystem, relative, or absolute. Specify as: integer data type using xs:integer, float data type using xs:double, string data type using xs:string, boolean data type using xs:boolean, binary data type using xs:hexBinary, enum data type using label name, relative time data type using xs:duration, absolute time data type using xs:dateTime. Values must not exceed the characteristics for the data type or this is a validation error. Takes precedence over an initial value given in the data type. Values are calibrated unless there is an option to override it. The value type must match the Parameter type Describe an unordered collection of parameter type definitions. These types named for the engineering/calibrated type of the parameter. See BaseDataType and BaseTimeDataType. Describe a parameter type that has an engineering/calibrated value in the form of a character string. Describe a parameter type that has an engineering/calibrated value in the form of an enumeration. Describe a parameter type that has an engineering/calibrated value in the form of an integer. Describe a parameter type that has an engineering/calibrated value in the form of a binary (usually hex represented). Describe a parameter type that has an engineering/calibrated value in the form of a decimal. Describe a parameter type that has an engineering/calibrated value in the form of a boolean enumeration. Describe a parameter type that has an engineering/calibrated value in the form of a duration in time. Describe a parameter type that has an engineering/calibrated value in the form of an instant in time. Describe a parameter type that has an engineering/calibrated value in the form of an array of a primitive type. Describe a parameter type that has an engineering/calibrated value in the form of a structure of parameters of other types. A reference to a Parameter. Uses Unix ‘like’ naming across the SpaceSystem Tree (e.g., SimpleSat/Bus/EPDS/BatteryOne/Voltage). To reference an individual member of an array use the zero based bracket notation commonly used in languages like C, C++, and Java. One or more physical addresses may be associated with each Parameter. Examples of physical addresses include a location on the spacecraft or a location on a data collection bus. Contains the address (e.g., channel information) required to process the spacecraft telemetry streams. May be an onboard id, a mux address, or a physical location. Contains the address (channel information) required to process the spacecraft telemetry streams Describe the physical address(s) that this parameter is collected from. Examples of physical addresses include a memory location on the spacecraft or a location on a data collection bus, with the source identified with a descriptive name for the region of memory, such as RAM, Flash, EEPROM, and other possibilities that can be adapted for program specific usage. A sub-address may be used to further specify the location if it fractionally occupies the address. Additional possibilities exist for separating partitions of memory or other address based storage mechanisms. This specification does not specify spacecraft specific hardware properties, so usage of addressing information is largely program and platform specific. A descriptive name for the location, such as a memory type, where this address is located. The address within the memory location. This specification does not specify program and hardware specific attributes, such as address size and address region starting location. These are part of the spacecraft hardware properties. A service is a logical grouping of container and/or messages. Describes a string parameter type. Three forms are supported: fixed length, variable length and variable length using a prefix. See StringDataEncodingType and StringDataType. Default alarm definitions are those which do not adjust definition logic based on the value of other parameters. Other parameters may participate in the determination of an alarm condition for this parameter, but the definition logic of the alarm on this parameter is constant. If the alarming logic on this parameter changes based on the value of other parameters, then it is a ContextAlarm and belongs in the ContextAlarmList element. Context alarm definitions are those which adjust the definition logic for this parameter based on the value of other parameters. A context which evaluates to being in effect, based on the testing of another parameter, takes precedence over the default alarms in the DefaultAlarm element. If the no context alarm evaluates to being in effect, based on the testing of another parameter, then the default alarm definitions from the DefaultAlarm element will remain in effect. If multiple contexts evaluate to being in effect, then the first one that appears will take precedence. Describes a relative time parameter type. Relative time parameters are time offsets (e.g. 10 second, 1.24 milliseconds, etc.) See IntegerDataEncodingType, FloatDataEncoding and RelativeTimeDataType. Default alarm definitions are those which do not adjust definition logic based on the value of other parameters. Other parameters may participate in the determination of an alarm condition for this parameter, but the definition logic of the alarm on this parameter is constant. If the alarming logic on this parameter changes based on the value of other parameters, then it is a ContextAlarm and belongs in the ContextAlarmList element. Context alarm definitions are those which adjust the definition logic for this parameter based on the value of other parameters. A context which evaluates to being in effect, based on the testing of another parameter, takes precedence over the default alarms in the DefaultAlarm element. If the no context alarm evaluates to being in effect, based on the testing of another parameter, then the default alarm definitions from the DefaultAlarm element will remain in effect. If multiple contexts evaluate to being in effect, then the first one that appears will take precedence. A telemetered Parameter is one that will have values in telemetry. A derived Parameter is one that is calculated, usually by an Algorithm. A constant Parameter is one that is used as a constant in the system (e.g. a vehicle id). A local Parameter is one that is used purely by the software locally (e.g. a ground command counter). A ground Parameter is one that is generated by an asset which is not the spacecraft. Describes a time association consisting of an instance of an absolute time parameter (parameterRef) and this entry. Because telemetry parameter instances are oftentimes "time-tagged" with a timing signal either provided on the ground or on the space system. This data element allows one to specify which of possibly many AbsoluteTimeParameters to use to "time-tag" parameter instances with. See AbsoluteTimeParameterType. If true, then the current value of the AbsoluteTime will be projected to current time. In other words, if the value of the AbsoluteTime parameter was set 10 seconds ago, then 10 seconds will be added to its value before associating this time with the parameter. The offset is used to supply a relative time offset from the time association and to this parameter Specify the units the offset is in, the default is si_second. This schema defines the dictionary for commanding Describe an absolute time argument type relative to a known epoch (such as TAI). The string representation of this time should use the [ISO 8601] extended format CCYY-MM-DDThh:mm:ss where "CC" represents the century, "YY" the year, "MM" the month and "DD" the day, preceded by an optional leading "-" sign to indicate a negative number. If the sign is omitted, "+" is assumed. The letter "T" is the date/time separator and "hh", "mm", "ss" represent hour, minute and second respectively. Additional digits can be used to increase the precision of fractional seconds if desired i.e. the format ss.ss... with any number of digits after the decimal point is supported. See TAIType, IntegerDataEncoding and AbsoluteTimeDataType. Describe an array argument type. The size and number of dimension are described here. See ArrayParameterRefEntryType, NameReferenceType and ArrayDataType. Describe the dimensions of this array. Describe a complex data type analogous to a C-struct. Each field of the data type is called a Member. Each Member is part of the MemberList which forms the list of items to be placed under this data type’s name. The MemberList defines a data block and block’s size is defined by the DataEncodings of each Member’s type reference. The data members are ordered and contiguous in the MemberList element (packed). Each member may be addressed by the dot syntax similar to C such as P.voltage if P is the referring parameter and voltage is of a member of P’s aggregate type. See MemberType, MemberListType, DataEncodingType, NameReferenceType, and AggregateDataType. Argument Assignments specialize a MetaCommand or BlockMetaCommand when inheriting from another MetaCommand. General argument values can be restricted to specific values to further specialize the MetaCommand. Use it to ‘narrow’ a MetaCommand from its base MetaCommand by specifying values of arguments for example, a power command may be narrowed to a power on’ command by assigning the value of an argument to ‘on’. See ArgumentAssignmentType and MetaCommandType. Specialize this command definition when inheriting from a more general MetaCommand by restricting the specific values of otherwise general arguments. Describe an assignment of an argument with a calibrated/engineering value. See ArgumentAssignmentListType. The named argument from the base MetaCommand to assign/restrict with a value. Specify value as a string compliant with the XML schema (xs) type specified for each XTCE type: integer=xs:integer; float=xs:double; string=xs:string; boolean=xs:boolean; binary=xs:hexBinary; enum=xs:string from EnumerationList; relative time=xs:duration; absolute time=xs:dateTime. Supplied value must be within the ValidRange specified for the type. Identical to ComparisonType but supports argument instance references. This parameter instance is being compared to the value in the parent element using the comparison defined there also. This argument instance is being compared to the value in the parent element using the comparison defined there also. Comparison operator to use with equality being the common default. Specify as: integer data type using xs:integer, float data type using xs:double, string data type using xs:string, boolean data type using xs:boolean, binary data type using xs:hexBinary, enum data type using label name, relative time data type using xs:duration, absolute time data type using xs:dateTime. Values must not exceed the characteristics for the data type or this is a validation error. Takes precedence over an initial value given in the data type. Values are calibrated unless there is an option to override it. Identical to ComparisonCheckType but supports argument instance references. Left hand side parameter instance. Left hand side argument instance. Comparison operator. Right hand side parameter instance. Parameter is assumed to be of the same type as the comparison Argument or Parameter. Right hand side argument instance. Argument is assumed to be of the same type as the comparison Argument or Parameter. Specify as: integer data type using xs:integer, float data type using xs:double, string data type using xs:string, boolean data type using xs:boolean, binary data type using xs:hexBinary, enum data type using label name, relative time data type using xs:duration, absolute time data type using xs:dateTime. Values must not exceed the characteristics for the data type or this is a validation error. Takes precedence over an initial value given in the data type. Values are calibrated unless there is an option to override it. Identical to ComparisonListType but supports argument instance references. List of Comparison elements must all be true for the comparison to evaluate to true. Identical to ArgumentDiscreteLookupType but supports argument instance references. Value to use when the lookup conditions are true. Identical to DiscreteLookupListType but supports argument instance references. Describe a lookup condition set using discrete values from arguments and/or parameters. Identical to DynamicValueType but supports argument instance references. Retrieve the value by referencing the value of an Argument. Retrieve the value by referencing the value of a Parameter. A slope and intercept may be applied to scale or shift the value selected from the argument or parameter. Identical to InputAlgorithmType but supports argument instance references. The InputSet describes the list of arguments and/or parameters that should be made available as input arguments to the algorithm. Identical to InputSetType but supports argument instance references. Reference a parameter to serve as an input to the algorithm. Reference an argument to serve as an input to the algorithm. An argument instance is the name of an argument as the reference is always resolved locally to the metacommand. Give the name of the argument. There is no path, this is a local reference. Typically the calibrated/engineering value is used and that is the default. Defines a list of Arguments for a command definition. Defines an Argument for a command definition. Arguments are local to the MetaCommand, BlockMetaCommand, and those that inherit from the definition. Need to ensure that the named types actually exist Identical to BooleanExpressionType but supports argument instance references. Condition elements describe a test similar to the Comparison element except that the arguments/parameters used have additional flexibility. This element describes tests similar to the ComparisonList element except that the arguments/parameters used are more flexible. This element describes tests similar to the ComparisonList element except that the arguments/parameters used are more flexible. Identical to ANDedConditionsType but supports argument instance references. Condition elements describe a test similar to the Comparison element except that the arguments/parameters used have additional flexibility for the compare. This element describes tests similar to the ComparisonList element except that the arguments/parameters used are more flexible and the and/or for multiple checks can be specified. Identical to ORedConditionsType but supports argument instance references. Condition elements describe a test similar to the Comparison element except that the arguments/parameters used have additional flexibility for the compare. This element describes tests similar to the ComparisonList element except that the arguments/parameters used are more flexible and the and/or for multiple checks can be specified. Identical to MatchCriteriaType but supports argument instance references. A simple comparison check involving a single test of an argument or parameter value. A series of simple comparison checks with an implicit 'and' in that they all must be true for the overall condition to be true. An arbitrarily complex boolean expression that has additional flexibility on the terms beyond the Comparison and ComparisonList elements. An escape to an externally defined algorithm. An Argument has a name and can take on values with the underlying value type described by the ArgumentTypeRef. Describe the properties of a command argument referring to a data type (argument type). The bulk of properties associated with a command argument are in its argument type. The initial value specified here, overrides the initial value in the argument type. See BaseDataType, BaseTimeDataType and NameReferenceType. Specify the reference to the argument type from the ArgumentTypeSet area using the path reference rules, either local to this SpaceSystem, relative, or absolute. Specify as: integer data type using xs:integer, float data type using xs:double, string data type using xs:string, boolean data type using xs:boolean, binary data type using xs:hexBinary, enum data type using label name, relative time data type using xs:duration, absolute time data type using xs:dateTime. Values must not exceed the characteristics for the data type or this is a validation error. Takes precedence over an initial value given in the data type. Values are calibrated unless there is an option to override it. The value type must match the Argument type Describe an unordered collection of argument type definitions. These types named for the engineering/calibrated type of the argument. See BaseDataType and BaseTimeDataType. Describe an argument type that has an engineering/calibrated value in the form of a character string. Describe an argument type that has an engineering/calibrated value in the form of an enumeration. Describe an argument type that has an engineering/calibrated value in the form of an integer. Describe an argument type that has an engineering/calibrated value in the form of a binary (usually hex represented). Describe an argument type that has an engineering/calibrated value in the form of a decimal. Describe an argument type that has an engineering/calibrated value in the form of a boolean enumeration. Describe an argument type that has an engineering/calibrated value in the form of a duration in time. Describe an argument type that has an engineering/calibrated value in the form of an instant in time. Describe an argument type that has an engineering/calibrated value in the form of an array of a primitive type. Describe an argument type that has an engineering/calibrated value in the form of a structure of arguments of other types. When specified, a BaseMetaCommand element identifies that this MetaCommand inherits (extends) another MetaCommand. It’s required ArgumentAssignmentList narrows or this command from the parent. This is typically used when specializing a generic MetaCommand to a specific MetaCommand. See MetaCommandType. Argument Assignments specialize a MetaCommand or BlockMetaCommand when inheriting from another MetaCommand. General argument values can be restricted to specific values to further specialize the MetaCommand. Reference to the MetaCommand definition that this MetaCommand extends. Defines a binary engineering/calibrated argument type (often called “blob type”). The binary data may be of fixed or variable length, and has an optional encoding and decoding algorithm that may be defined to transform the data between space and ground. See BinaryDataEncodingType, IntegerValueType, InputAlgorithmType, and BinaryDataType. Describe an ordered grouping of MetaCommands into a list, duplicates are valid. The block contains argument values fully specified. See MetaCommandStepListType. List of the MetaCommands to include in this BlockMetaCommand. Defines a boolean argument type which has two values only: ‘True’ (1) or ‘False’ (0). The values one and zero may be mapped to a specific string using the attributes oneStringValue and zeroStringValue. This type is a simplified form of the EnumeratedDataType. See IntegerDataEncoding and BooleanDataType. Describe an entry list for a CommandContainer which is associated with a MetaCommand. The entry list for a MetaCommand CommandContainer element operates in a similar fashion as the entry list element for a SequenceContainer element. It adds fixed value and argument entries to the entry list not present in sequence containers. See MetaCommandType, CommandContainerType and EntryListType. Specify a Parameter to be a part of this container layout definition. Specify a portion of a Parameter to be a part of this container layout definition. This is used when the Parameter is reported in fractional parts in the container before being fully updated. Specify the content of another Container to be a part of this container layout definition. Specify a portion of another Container to be a part of this container layout definition. Specify a portion of a Stream to be a part of this container layout definition. Specify a previous (not last reported) value of a Parmeter to be a part of this container layout definition. Specify an Array Type Parameter to be a part of this container layout definition when the Container does not populate the entire space of the Array contents. If the entire space of the Array is populated, a tolerant implementation will accept ParameterRefEntry also. Specify an Argument to be a part of this container layout definition. Specify an Array Type Argument to be a part of this container layout definition when the Container does not populate the entire space of the Array contents. If the entire space of the Array is populated, a tolerant implementation will accept ArgumentRefEntry also. Specify an immutable value to be a part of this container layout definition. Contains an unordered Set of Command Containers Describe a MetaCommand command container. The command container may contain arguments, parameters, other basic containers, and fixed values. Arguments are supplied by the user of a commanding application; parameters are supplied by the controlling system. Parameters and arguments map source data types to encodings. See MetaCommandType. List of item entries to pack/encode into this container definition. When a MetaCommand inherits/extends another MetaCommand, this references the CommandContainer from the BaseMetaCommand. A command verifier is used to check that the command has been successfully executed. Command Verifiers may be either a Custom Algorithm or a Boolean Check or the presence of a Container for a relative change in the value of a Parameter. The CheckWindow is a time period where the verification must test true to pass. Verification is a list of comparisons. Verification is a new instance of the referenced container. For example, sending a command to download memory then receiving a packet with the memory download would be verified upon receipt of the packet. Verification is a telemetry parameter value change on the ground. For example, a command counter. Verification is outside the scope of regular command and telemetry processing. Verification is a boolean expression of conditions. Verification is a single comparison. Define a time window for checking for verification. Define a time window algorithmically for verification. Describes an enumerated argument type. The enumeration list consists of label/value pairs. See EnumerationListType, IntegerDataEncodingType and EnumeratedDataType. Describe a floating point argument type. Several encodings are supported. Calibrated integer to float relationships should be described with this data type. Use the data encoding to define calibrators. Joins integer as one of the numerics. See FloatDataEncodingType, IntegerDataEncodingType and FloatDataType. Provides additional platform/program specific ranging information. Describes an integer argument type. Several encodings supported. Calibrated integer to integer relationships should be described with this data type. Use the integer data encoding to define calibrators. Joins float as one of the numerics. See IntegerDataEncoding and IntegerDataType. Provides additional platform/program specific ranging information. Describes an unordered collection of command definitions. Duplicates are invalid based on the name attribute of MetaCommand and BlockMetaCommand. See MetaCommandType and BlockMetaCommandType. All atomic commands to be sent on this mission are listed here. In addition this area has verification and validation information. Used to include a MetaCommand defined in another sub-system in this sub-system. Used to define a command that includes more than one atomic MetaCommand definition. Describe the list of MetaCommand definitions that form the block command. Contains an ordered list of MetaCommandSteps where each step is a MetaCommand with associated arguments, duplicates are valid. See BlockMetaCommandType. A MetaCommand with specific specified argument values to include in the BlockMetaCommand. Describe a MetaCommand step, consisting MetaCommand reference and argument list. See MetaCommandStepListType and NameReferenceType. Describe a command which consists of an abstract portion (MetaCommand) and an optional packaging portion (MetaCommand CommandContainer). An argument list is provided. MetaCommand may extend other MetaCommands and their CommandContainer may extend other CommandContainer or SequenceContainers. A MetaCommand’s CommandContainer is private except as referred to in BaseMetaCommand (they are not visible to other containers and cannot be used in an entry list). MetaCommands may also define various other behavioral aspects of a command such as command verifiers. See CommandContainerType, ArgumentListType, BaseMetaCommandType and BaseContainerType. Optional inheritance for this MetaCommand from another named MetaCommand. Optional. Normally used when the database is built in a flat, non-hierarchical format. May be used by implementations to group MetaCommands together. Many commands have one or more options. These are called command arguments. Command arguments may be of any of the standard data types. MetaCommand arguments are local to the MetaCommand, but may be referenced in inherited MetaCommand definitions, generally to apply Argument Assignments to the values. Tells how to package/encode this command definition in binary form. List of constraints to check when sending this command. Some Command and Control Systems may require special user access or confirmations before transmitting commands with certain levels. The level is inherited from the Base MetaCommand. Some Command and Control Systems may require special user access or confirmations before transmitting commands with certain levels. In addition to the default, Significance can be defined in contexts where it changes based on the values of parameters. An Interlock is a type of Constraint, but not on Command instances of this MetaCommand; Interlocks apply instead to the next command. An Interlock will block successive commands until this command has reached a certain stage (through verifications). Interlocks are scoped to a SpaceSystem basis. Functional list of conditions/changes to check after sending this command to determine success or failure. List of parameters to set new values upon completion of sending this command. List of parameters to suspend alarm processing/detection upon completion of sending this command. Abstract MetaCommand definitions that are not instantiated, rather only used as bases to inherit from to create specialized command definitions. Describes a relative time argument type. Relative time parameters are time offsets (e.g. 10 second, 1.24 milliseconds, etc.) See IntegerDataEncodingType, FloatDataEncoding and RelativeTimeDataType. Significance provides some cautionary information about the potential consequence of each MetaCommand. If none is supplied, then the current SpaceSystem is assumed to be the one at risk by the issuance of this command Describes a string parameter type. Three forms are supported: fixed length, variable length and variable length using a prefix. See StringDataEncodingType and StringDataType. A verifier that means the SpaceSystem has accepted the command Used by CommandVerifiers to limit the time allocated to check for the verification. See CheckWindowAlgorithmsType. Used by CommandVerifiers to limit the time allocated to check for the verification. See CommandVerifierType. A possible set of verifiers that all must be true for the command be considered completed. Describe a significance level for a MetaCommand definition where the significance level depends on matching a context value. See ContextMatchType and SignificanceType. Describe the context matching value and source that will enable the Significance listed in the Significance element. Describe the signficance of this MetaCommand definition. See SignificanceType. Describe an ordered list of ContextSignificance elements where the significance on the first context match to test true is used as the significance of the MetaCommand. If there is a DefaultSignificance, it is overrideen by the matching context. See ContextSignificantType and MetaCommandType. Describe a significance level for a MetaCommand definition where the significance level depends on matching a context value. See ContextMatchType and SignificanceType. A verifier that indicates that the command is being executed. An optional Element indicates how far along the command has progressed either as a fixed value or an (possibly scaled) ParameterInstance value. When true, indicates that the command failed. timeToWait is how long to wait for the FailedVerifier to test true. Describe a type of constraint on the next command, rather than this command. Interlocks apply only to the next command. An interlock will block successive commands until this command has reached a certain stage of verifier. Interlocks are scoped to a SpaceSystem basis: they by default apply to the SpaceSystem the MetaCommand is defined in but this may be overridden. See MetaCommandType and VerifierSetType. The name of a SpaceSystem this Interlock applies to. By default, it only applies to the SpaceSystem that contains this MetaCommand. The verification stage of the command that releases the interlock, with the default being complete. Only applies when the verificationToWaitFor attribute is 'queued' or 'executing'. A flag that indicates that under special circumstances, this Interlock can be suspended. Sets a Parameter to a new value (either from a derivation or explicitly) after the command has been verified (all verifications have passed). Value type must match Parameter type. Specify a MathOperation to use to set the Parameter value. See MathOperationType. Specify value as a string compliant with the XML schema (xs) type specified for each XTCE type: integer=xs:integer; float=xs:double; string=xs:string; boolean=xs:boolean; binary=xs:hexBinary; enum=xs:string from EnumerationList; relative time= xs:duration; absolute time=xs:dateTime. Supplied value must be within the ValidRange specified for the Parameter and appropriate for the type. This attribute provides more specific control over when the Parameter value is set. By default, it is when the command have all verifications complete. See VerifierEnumerationType. Parameters that are set with a new value after the command has been sent. Appended to the Base Command list Will suspend all Alarms associated with this Parameter for the given suspense time after the given verifier Sometimes it is necessary to suspend alarms - particularly 'change' alarms for commands that will change the value of a Parameter A parameter change in value or specified delta change in value. A verifer that means the command is scheduled for execution by the SpaceSystem. A verifier that simply means the SpaceSystem has received the command. Sent from range means the command has been transmitted to the spacecraft by the network that connects the ground system to the spacecraft. Obviously, this verifier must come from something other than the spacecraft. Time units the time association decimal value is in. Transferred to range means the command has been received to the network that connects the ground system to the spacecraft. Obviously, this verifier must come from something other than the spacecraft. A CommandTransmission constraint is used to check that the command can be run in the current operating mode and may block the transmission of the command if the constraint condition is true. Pause during timeOut, fail when the timeout passes Indicates whether the constraints for a Command may be suspended. Appended to the TramsmissionConstraint List of the base command. Constraints are checked in order. An enumerated list of verifier types Describe a collection of unordered verifiers. A command verifier is a conditional check on the telemetry from a SpaceSystem that that provides positive indication on the processing state of a command. There are eight different verifiers each associated with difference states in command processing: TransferredToRange, TransferredFromRange, Received, Accepted, Queued, Execution, Complete, and Failed. There may be multiple ‘complete’ and 'execution' verifiers. If the MetaCommand is part of an inheritance relation (BaseMetaCommand), the 'complete' and 'execution' verifier sets are appended to any defined in the parent MetaCommand. All others will override a verifier defined in a BaseMetaCommand. Duplicate verifiers in the list of CompleteVerifiers and ExecutionVerifiers before and after appending to the verifiers in BaseMetaCommand should be avoided. See MetaCommandType and BaseMetaCommandType for additional information. This schema defines the structure for an Algorithm. An Algorithm may be one of a growing set of pre-defined algorithms or a named escape into a user defined algorithm where (depending on the system) the name of the algorithm may be a java class, a function in a shared library, an external program or some other reference to an outside algorithm. At some later date, this schema may also allow the logic of the user defined algorithm to be defined within the instance document itself (perhaps using MathML?). This optional element may be used to enter Pseudo or actual code for the algorithm. The language for the algorithm is specified with the language attribute A base type for the various triggers, purely to improve the mappings created by data binding compilers. Describe checksum information. Assumed to return the computed checksum. Qualified list of name checksum algorithms. If custom is chosen, InputAlgorithm must be set. Document a custom checksum algorithm Names and provides a value for a constant input to the algorithm. There are two attributes to Constant, constantName and value. constantName is a variable name in the algorithm to be executed. value is the value of the constant to be used. Describe an ordered list of calibrators with a context match. Useful when different calibrations must be used depending on a matching value. The first context that matches determines which calibrator to use. See IntegerDataEncodingType and FloatDataEncodingType. Describe a calibrator that depends on a matching value using a ContextMatch. When the context matches for the calibrator, the default calibrator is overridden, if it exists. This is the external algorithm. Multiple entries are provided so that the same database may be used for multiple implementation s A set of labeled inputs is added to the SimpleAlgorithmType The InputSet describes the list of parameters that should be made available as input arguments to the algorithm. A set of labeled outputs are added to the SimpleInputAlgorithmType Input output algorithm is extended with a set of labeled triggers. See InputOutputAlgorithmType. First telemetry container from which the output parameter should be calculated. Algorithm processing priority. If more than one algorithm is triggered by the same container, the lowest priority algorithm should be calculated first. Names an input parameter to the algorithm. There are two attributes to InputParm, inputName and parameterName. parameterName is a parameter reference name for a parameter that will be used in this algorithm. inputName is an optional "friendly" name for the input parameter. Describe a postfix (Reverse Polish Notation (RPN)) notation based mathmatical equations. See MathOperationType. The contents of the Math Operation as an algorithm definition in RPN. See TriggeredMathOperationType. Describe a reference to container that triggers an event when the telemetry container referred to is updated (processed). See TriggerSetType. Reference to the Container whose update/receipt triggers this algorithm to evaluate. Describe a periodic time basis to trigger an event. See TriggerSetType. The periodic rate in time in which this algorithm is triggered to evaluate. Describe a reference to parameter that triggers an event when the telemetry parameter referred to is updated (processed) with a new value. See TriggerSetType. Reference to the Parameter whose update triggers this algorithm to evaluate. Names an output parameter to the algorithm. There are two attributes to OutputParm, outputName and parameterName. parameterName is a parameter reference name for a parameter that will be updated by this algorithm. outputName is an optional "friendly" name for the output parameter. The simplest form of algorithm, a SimpleAlgorithmType contains an area for a free-form pseudo code description of the algorithm plus a Set of references to external algorithms. External algorithms are usually unique to a ground system type. Multiple external algorithms are possible because XTCE documents may be used across multiple ground systems. A trigger is used to initiate the processing of some algorithm. A trigger may be based on an update of a Parameter, receipt of a Container, or on a time basis. Triggers may also have a maximum rate that limits how often the trigger can be invoked. This element instructs the trigger to invoke the algorithm evaluation when a Parameter update is received. This element instructs the trigger to invoke the algorithm evaluation when a Container is received. This element instructs the trigger to invoke the algorithm evaluation using a timer. Triggers may optionally be named. This attribute is a maximum rate that constrains how quickly this trigger may evaluate the algorithm to avoid flooding the implementation. The default is once per second. Setting to 0 results in no maximum. Supplies an optional non-reference-able name and short description for calibrators. Also includes an optional ancillary data for any special local flags, note that these may not necessarily transfer to another recipient of an instance document. Optional additional ancillary information for this calibrator/algorithm Optional name for this calibrator/algorithm Optional description for this calibrator/algorithm Describe a calibrator to transform a source data type raw/uncalibrated value (e.g. an integer count from a spacecraft) to an engineering unit/calibrated value for users (e.g. a float). Describes a calibrator in the form of a piecewise defined function Describes a calibrator in the form of a polynomial function Describes a calibrator in the form of a user/program/implementation defined function Describe a change value used to test verification status. See CommandVerifierType. Value as a floating point number. Describe a mathematical function for calibration where the mathematical function is defined using the MathOperationType. Describe a postfix (aka Reverse Polish Notation (RPN)) expression for mathematical equations. It uses a stack where operands (either fixed values or ParameterInstances) are pushed onto the stack from first to last in the XML. As the operators are specified, each pops off operands as it evaluates them, and pushes the result back onto the stack. For example, the stack, 4 8 /, would result as 0.5. In this case postfix is used to avoid having to specify parenthesis. To convert from infix to postfix, use Dijkstra's "shunting yard" algorithm. Use a constant in the calculation. Use the value of this parameter in the calculation. It is the calibrator's value only. If the raw value is needed, specify it explicitly using ParameterInstanceRefOperand. Note this element has no content. All operators utilize operands on the top values in the stack and leaving the result on the top of the stack. Ternary operators utilize the top three operands on the stack, binary operators utilize the top two operands on the stack, and unary operators use the top operand on the stack. This element is used to reference the last received/assigned value of any Parameter in this math operation. Describe a polynomial equation for calibration. This is a calibration type where a curve in a raw vs calibrated plane is described using a set of polynomial coefficients. Raw values are converted to calibrated values by finding a position on the curve corresponding to the raw value. The first coefficient belongs with the X^0 term, the next coefficient belongs to the X^1 term and so on. See CalibratorType. A single term in the polynomial function. Generally only up to second order powers are reflexive. Implementations may limit the maximum number of terms supported. Describe a spline function for calibration using a set of at least 2 points. Raw values are converted to calibrated values by finding a position on the line corresponding to the raw value. The line may be interpolated and/or extrapolated as needed. The interpolation order may be specified for all the points and overridden on individual points. The algorithm triggers on the input parameter. See CalibratorType. Describes a single point of the spline or piecewise function. The interpolation order to apply to the overall spline function. Order 0 is no slope between the points (flat). Order 1 is linear interpolation. Order 2 would be quadratic and in this special case, 3 points would be required, etc. Extrapolation allows the closest outside point and the associated interpolation to extend outside of the range of the points in the spline function. This schema provides a language for defining binary stream data. After searching for the frame sync marker for some number of bits, it may be desirable to invert the incoming data, and then look for frame sync. In some cases this will require an external algorithm A stream type where some level of custom processing (e.g. convolutional, encryption, compression) is performed. Has a reference to external algorithms for encoding and decoding algorithms. Must check to ensure that the attributes encodedStreamRef and decodedStreamRef point to valid Streams Algorithm outputs may be used to set decoding quality parameters. The pattern of bits used to look for frame synchronization. The top level type definition for all data streams that are frame based. This Container (usually abstract) is the container that is in the fixed frame stream. Normally, this is a general container type from which many specific containers are inherited. This is a reference to a connecting stream - say a custom stream. For streams that contain a series of frames with a fixed frame length where the frames are found by looking for a marker in the data. This marker is sometimes called the frame sync pattern and sometimes the Asynchronous Sync Marker (ASM). This marker need not be contiguous although it usually is. Allowed slip (in bits) in either direction for the sync pattern Describe a sync pattern and an optional reference to an algorithm used to invert the stream if the frame sync pattern is not found. See FixedFrameStreamType. The pattern of bits used to look for frame synchronization. See SyncPatternType. A PCM Stream Type is the high level definition for all Pulse Code Modulated (PCM) (i.e., binary) streams. Holds a reference to a stream name of reference stream Contains an unordered set of Streams. A Sync Strategy specifies the strategy on how to find frames within a stream of PCM data. The sync strategy is based upon a state machine that begins in the 'Search' state until the first sync marker is found. Then it goes into the 'Verify' state until a specified number of successive good sync markers are found. Then, the state machine goes into the 'Lock' state, in the 'Lock' state frames are considered good. Should a sync marker be missed in the 'Lock' state, the state machine will transition into the 'Check' state, if the next sync marker is where it's expected within a specified number of frames, then the state machine will transition back to the 'Lock' state, it not it will transition back to 'Search'. Maximum number of bit errors in the sync pattern (marker). The pattern of bits used to look for frame synchronization. CCSDS ASM for non-turbocoded frames = 1acffc1d truncate the mask from the left truncate the pattern from the left For streams that contain a series of frames with a variable frame length where the frames are found by looking for a series of one's or zero's (usually one's). The series is called the flag. in the PCM stream that are usually made to be illegal in the PCM stream by zero or one bit insertion. A base schema type for describing an absolute time data type. Contains an absolute (to a known epoch) time. Use the [ISO 8601] extended format CCYY-MM-DDThh:mm:ss where "CC" represents the century, "YY" the year, "MM" the month and "DD" the day, preceded by an optional leading "-" sign to indicate a negative number. If the sign is omitted, "+" is assumed. The letter "T" is the date/time separator and "hh", "mm", "ss" represent hour, minute and second respectively. Additional digits can be used to increase the precision of fractional seconds if desired i.e. the format ss.ss... with any number of digits after the decimal point is supported. See AbsoluteTimeParameterType and AbsoluteTimeArgumentType. See AbsouteTimeParameterType, AbsoluteTimeArgumentType and BaseTimeDataType. Default/Initial value is always given in calibrated form. A base schema type for describing an absolute time data type. Contains an absolute (to a known epoch) time. Use the [ISO 8601] extended format CCYY-MM-DDThh:mm:ss where "CC" represents the century, "YY" the year, "MM" the month and "DD" the day, preceded by an optional leading "-" sign to indicate a negative number. If the sign is omitted, "+" is assumed. The letter "T" is the date/time separator and "hh", "mm", "ss" represent hour, minute and second respectively. Additional digits can be used to increase the precision of fractional seconds if desired i.e. the format ss.ss... with any number of digits after the decimal point is supported. See AbsoluteTimeParameterType and AbsoluteTimeArgumentType. See AbsouteTimeParameterType, AbsoluteTimeArgumentType and BaseTimeDataType. Default/Initial value is always given in calibrated form. A base schema type for describing a complex data type analogous to a C-struct. Each field of the data type is called a Member. Each Member is part of the MemberList which forms the list of items to be placed under this data type’s name. The MemberList defines a data block and block’s size is defined by the DataEncodings of each Member’s type reference. The data members are ordered and contiguous in the MemberList element (packed). Each member may be addressed by the dot syntax similar to C such as P.voltage if P is the referring parameter and voltage is of a member of P’s aggregate type. See MemberType, MemberListType, DataEncodingType, NameReferenceType, AggregateParameterType and AggregateArgumentType. Ordered list of the members of the aggregate/structure. Members are contiguous. A base schema type for describing an array data type. The number of and size of each dimension is defined in its two child types. See NameReferenceType, ArrayArgumentType and ArrayParameterType. Reference to the data type that represents the type of the elements for this array. An abstract schema type used by within the schema to derive the other simple/primitive engineering form data types: BooleanDataType, BinaryDataType, StringDataType, EnumeratedDataType, FloatDataType and IntegerDataType. The encoding elements are optional because they describe the raw wire encoded form of the data type. Encoding is only necessary when the type is telemetered in some form. Local variables and derived typically do not require encoding. When appropriate, describe the units of measure that are represented by this parameter value. Binary encoding is typically a "pass through" raw encoding form where one of the more common encodings is not required for the parameter. A custom transformation capability is available if needed. Float encoding is a common encoding where the raw binary is in a form that gets interpreted as a decimal numeric value. Integer encoding is a common encoding where the raw binary is in a form that gets interpreted as an integral value, either signed or unsigned. String encoding is a common encoding where the raw binary is in a form that gets interpreted as a character sequence. Must be derived from a like type (e.g,, String from String). No circular derivations. Used to derive one Data Type from another - will inherit all the attributes from the baseType any of which may be redefined in this type definition. Identical to BaseDataType but supports argument instance references. When appropriate, describe the units of measure that are represented by this argument value. Binary encoding is typically a "pass through" raw encoding form where one of the more common encodings is not required for the argument. A custom transformation capability is available if needed. Float encoding is a common encoding where the raw binary is in a form that gets interpreted as a decimal numeric value. Integer encoding is a common encoding where the raw binary is in a form that gets interpreted as an integral value, either signed or unsigned. String encoding is a common encoding where the raw binary is in a form that gets interpreted as a character sequence. Must be derived from a like type (e.g,, String from String). No circular derivations. Used to derive one Data Type from another - will inherit all the attributes from the baseType any of which may be redefined in this type definition. Identical to BaseTimeDataType but supports argument instance references. Describes how the raw base counts of the time type are encoded/decoded. Describes origin (epoch or reference) of this time type. Extend another absolute or relative time type. An abstract schema type used within the schema to derive other time based data types: RelativeTimeDataType and AbsoluteTimeDataType. An absolute time data type is a telemetered source/destination data type. A data encoding must be set. An optional epoch may be set. Time types are an exception to other primitives because, if the time data type is not telemetered, it still must have a data encoding set. See DataEncodingType, AbsoluteTimeDataType and RelativeTimeDataType. Describes how the raw base counts of the time type are encoded/decoded. Describes origin (epoch or reference) of this time type. Extend another absolute or relative time type. Identical to BinaryDataType but supports argument instance references. Default/Initial value is always given in calibrated form. Extra bits are truncated from the MSB (leftmost). A base schema type for describing a binary data engineering/calibrated type (often called “blob type”). The binary data may be of fixed or variable length, and has an optional encoding and decoding algorithm that may be defined to transform the data between space and ground. See BaseDataType, BinaryParameterType and BinaryArgumentType. Default/Initial value is always given in calibrated form. Extra bits are truncated from the MSB (leftmost). Identical to BooleanDataType but supports argument instance references. Initial value must match either the oneStringValue or the zeroStringValue Default/Initial value is always given in calibrated form. Enumeration string representing the 1 value, with the default being 'True'. Enumeration string representing the 0 value, with the default being 'False'. A base schema type for describing a boolean data type which has two values only: ‘True’ (1) or ‘False’ (0). The values one and zero may be mapped to a specific string using the attributes oneStringValue and zeroStringValue. This type is a simplified form of the EnumeratedDataType. See BaseDataType, BooleanParameterType and BooleanArgumentType. Initial value must match either the oneStringValue or the zeroStringValue Default/Initial value is always given in calibrated form. Enumeration string representing the 1 value, with the default being 'True'. Enumeration string representing the 0 value, with the default being 'False'. For partial entries of an array, the starting and ending index for each dimension, OR the Size must be specified. Indexes are zero based. zero based index Identical to DimensionType but supports argument instance references. zero based index Where the Dimension list is in this form: Array[1stDim][2ndDim][lastDim]. The last dimension is assumed to be the least significant - that is this dimension will cycle through its combination before the next to last dimension changes. The order MUST ascend or the array will need to be broken out entry by entry. For an ArrayParameterType of size N, their should be N Dimensions An array made up by multiple Entries should not have indexes that overlap, but should be continuous. Identical to DimensionListType but supports argument instance references. For an ArrayParameterType of size N, their should be N Dimensions An array made up by multiple Entries should not have indexes that overlap, but should be continuous. Identical to EnumeratedDataType but supports argument instance references. Unordered list of label/value pairs where values cannot be duplicated. Check that values do not overlap in the mappings. Default/Initial value is always given in calibrated form. Use the label, it must be in the enumeration list to be valid. Label must be in the enumeration list to be valid. Describes an enumerated parameter type. The enumeration list consists of label/value pairs. See EnumerationListType, EnumeratedParameterType and EnumeratedArgumentType. Unordered list of label/value pairs where values cannot be duplicated. Check that values do not overlap in the mappings. Default/Initial value is always given in calibrated form. Use the label, it must be in the enumeration list to be valid. Label must be in the enumeration list to be valid. Identical to FloatDataType but supports argument instance references. This element provides the implementation with assistance rendering the value as a string for users. Default/Initial value is always given in calibrated form. Optional hint to the implementation about the size of the engineering/calibrated data type to use internally. Generally this can be determined by examination of the space required to capture the full range of the encoding, but it is not always clear when calibrators are in use. A tolerant implementation will endeavor to always make sufficient size engineering data types to capture the entire range of possible values. A base schema type for describing a floating point engineering/calibrated data type. Several encodings are supported. Calibrated integer to float relationships should be described with this data type. Use the data encoding to define calibrators. Joins integer as one of the numerics. See BaseDataType, FloatParameterType and FloatArgumentType. This element provides the implementation with assistance rendering the value as a string for users. The Valid Range provides additional boundary/constraint information beyond that of the data encoding in the range of possible values that are meaningful to this parameter. Not to be construed as an alarm definition, violations of the valid range make a parameter value "unreasonable", as opposed to reasonable to be reported, but in a state which should be of concern. By default and general recommendation, the valid range is specified in engineering/calibrated values, although this can be adjusted. Initial value is always given in calibrated form Optional hint to the implementation about the size of the engineering/calibrated data type to use internally. Generally this can be determined by examination of the space required to capture the full range of the encoding, but it is not always clear when calibrators are in use. A tolerant implementation will endeavor to always make sufficient size engineering data types to capture the entire range of possible values. Identical to IntegerDataType but supports argument instance references. This element provides the implementation with assistance rendering the value as a string for users. Default/Initial value is always given in calibrated form. Default is base 10 form; binary, octal, or hexadecimal values may be given by preceding value with 0[b|B], 0[o|O|, 0[x|X] respectively. Optional hint to the implementation about the size of the engineering/calibrated data type to use internally. Generally this can be determined by examination of the space required to capture the full range of the encoding, but it is not always clear when calibrators are in use. A tolerant implementation will endeavor to always make sufficient size engineering data types to capture the entire range of possible values. Flag indicating if the engineering/calibrated data type used should support signed representation. This should not be confused with the encoding type for the raw value. The default is true. Describe an integer engineering/calibrated data type. Several encodings are supported. See BaseDataType, IntegerParameterType and IntegerArgumentType. This element provides the implementation with assistance rendering the value as a string for users. The Valid Range provides additional boundary/constraint information beyond that of the data encoding in the range of possible values that are meaningful to this parameter. Not to be construed as an alarm definition, violations of the valid range make a parameter value "unreasonable", as opposed to reasonable to be reported, but in a state which should be of concern. By default and general recommendation, the valid range is specified in engineering/calibrated values, although this can be adjusted. Default/Initial value is always given in calibrated form. Default is base 10 form; binary, octal, or hexadecimal values may be given by preceding value with 0[b|B], 0[o|O|, 0[x|X] respectively. Optional hint to the implementation about the size of the engineering/calibrated data type to use internally. Generally this can be determined by examination of the space required to capture the full range of the encoding, but it is not always clear when calibrators are in use. A tolerant implementation will endeavor to always make sufficient size engineering data types to capture the entire range of possible values. Flag indicating if the engineering/calibrated data type used should support signed representation. This should not be confused with the encoding type for the raw value. The default is true. Describe a member field in an AggregateDataType. Each member has a name and a type reference to a data type for the aggregate member name. If this aggregate is a Parameter aggregate, then the typeRef is a parameter type reference. If this aggregate is an Argument aggregate, then the typeRef is an argument type reference. References to an array data type is currently not supported. Circular references are not allowed. See MemberListType. AggregateParameterType and AggregateArgumentType. ensure no circular references Used to set the initial calibrated values of Parameters. Will overwrite an initial value defined for the ParameterType. For integer types base 10 (decimal) form is assumed unless: if proceeded by a 0b or 0B, value is in base two (binary form, if proceeded by a 0o or 0O, values is in base 8 (octal) form, or if proceeded by a 0x or 0X, value is in base 16 (hex) form. Floating point types may be specified in normal (100.0) or scientific (1.0e2) form. Time types are specified using the ISO 8601 formats described for XTCE time data types. Initial values for string types, may include C language style (\n, \t, \", \\, etc.) escape sequences. The value type must match the Parameter type Order is important only if the name of the AggregateParameter or Aggregate Argument is directly referenced in SequenceContainers. In this case the members are assued to be added sequentially (in the order listed here) into the Container. Used to contain a relative time value. Used to describe a relative time. Normally used for time offsets. A Relative time is expressed as PnYn MnDTnH nMnS, where nY represents the number of years, nM the number of months, nD the number of days, 'T' is the date/time separator, nH the number of hours, nM the number of minutes and nS the number of seconds. The number of seconds can include decimal digits to arbitrary precision. For example, to indicate a duration of 1 year, 2 months, 3 days, 10 hours, and 30 minutes, one would write: P1Y2M3DT10H30M. One could also indicate a duration of minus 120 days as: -P120D. An extension of Schema duration type. Used to contain a relative time value. Used to describe a relative time. Normally used for time offsets. A Relative time is expressed as PnYn MnDTnH nMnS, where nY represents the number of years, nM the number of months, nD the number of days, 'T' is the date/time separator, nH the number of hours, nM the number of minutes and nS the number of seconds. The number of seconds can include decimal digits to arbitrary precision. For example, to indicate a duration of 1 year, 2 months, 3 days, 10 hours, and 30 minutes, one would write: P1Y2M3DT10H30M. One could also indicate a duration of minus 120 days as: -P120D. An extension of Schema duration type. Identical to StringDataType but supports argument instance references. Initial values for string types, may include C language style (\n, \t, \", \\, etc.) escape sequences. restriction pattern is a regular expression Defines a base schema type for StringParameterType and StringArgumentType, adding initial value, restriction pattern, character width, and size range in characters. The initial value if set is the initial value of all instances of the child types. The restriction pattern is a regular expression enforcing the string value to this pattern. The character width is on the local data type side. And the size range in character restricts the character set. For telemetered values, if the restriction pattern of size range in character is not met, the item is invalid. See BaseDataType, StringParameterType, StringArgumentType, CharacterWidthType and IntegerRangeType. The size in bits may be greater than or equal to minInclusive. It may be less than or equal to maxInclusive. They both may be set indicating a closed range. Initial values for string types, may include C language style (\n, \t, \", \\, etc.) escape sequences. restriction pattern is a regular expression Describe an ordered collection of units that form a unit-expression. Units may be described for both calibrated/engineering values and also potentially uncalibrated/raw values. See UnitType. Describe the exponent, factor, form, and description for a unit. The attributes are optional because different programs use this element in different ways, depending on vendor support. Numerical ranges that define the universe of valid values for this argument. A single range is the most common, although it is possible to define multiple ranges when the valid values are not contiguous. A valid range constrains the whole set of possible values that could be encoded by the data type to a more "valid" or "reasonable" set of values. This should be treated as a boundary check in an implementation to validate the input or output value. Typically, only 1 range is used. In cases where multiple ranges are used, then the value is valid when it is valid in any of the provided ranges. Implementations may also use these ranges to enhance user interface displays and other visualization widgets as appropriate for the type. By default and general recommendation, the valid range is specified in engineering/calibrated values, although this can be adjusted. Numerical ranges that define the universe of valid values for this argument. A single range is the most common, although it is possible to define multiple ranges when the valid values are not contiguous. A valid range constrains the whole set of possible values that could be encoded by the data type to a more "valid" or "reasonable" set of values. This should be treated as a boundary check in an implementation to validate the input or output value. Typically, only 1 range is used. In cases where multiple ranges are used, then the value is valid when it is valid in any of the provided ranges. Implementations may also use these ranges to enhance user interface displays and other visualization widgets as appropriate for the type. By default and general recommendation, the valid range is specified in engineering/calibrated values, although this can be adjusted. Defines two bit-order types: most significant bit first and least significant bit first. See DataEncodingType. Identical to BinaryDataEncodingType but supports argument instance references. Number of bits this value occupies on the stream being encoded/decoded. Used to convert binary data to an application data type Used to convert binary data from an application data type to binary data Describe binary data that is unmolested in the decoding/encoding or cannot be represented in any of the other data encoding formats. Optionally use the FromBinaryTransformAlgorithm and ToBinaryTransformAlgorithm element to describe the transformation process. See InputAlgorithmType for the transformation structure. Number of bits this value occupies on the stream being encoded/decoded. Used to convert binary data to an application data type Used to convert binary data from an application data type to binary data Cyclic Redundancy Check (CRC) definition. The polynomial coefficients for the CRC are defined as a truncated hex value. The coefficient for the nth bit of an n-bit CRC will always be 1 and is not represented in the truncated hex value. For example, the truncated hex value of CRC-32 (width=32 bits) used in the Ethernet specification is 0x04C11DB7, where each non-zero bit of the truncated hex represents a coefficient of 1 in the polynomial and the bit position represents the exponent. There may also be an initial remainder "InitRemainder" and a final XOR "FinalXOR" to fully specify the CRC. reflectData and reflectRemainder may also be specified to reverse the bit order in the incoming data and/or the result. Describes how a particular piece of data is sent or received from some non-native, off-platform device. (e.g. a spacecraft) Describe the data encoding for a time data type. It includes the units and other attributes scale and offset. Use scale and offset to describe a y=mx+b relationship (where m is the slope/scale and b is the intercept/offset) to make adjustments to the encoded time value so that it matches the time units. For binary encoded time use transform algorithms to convert time data formats that are too difficult to describe in XTCE. See AbsoluteTimeDataType and RelativeTimeDataType. Binary encoding is typically a "pass through" raw encoding form where one of the more common encodings is not required for the parameter. A custom transformation capability is available if needed. Float encoding is a common encoding where the raw binary is in a form that gets interpreted as a decimal numeric value. Integer encoding is a common encoding where the raw binary is in a form that gets interpreted as an integral value, either signed or unsigned. String encoding is a common encoding where the raw binary is in a form that gets interpreted as a character sequence. Time units, with the default being in seconds. Linear slope used as a shorter form of specifying a calibrator to convert between the raw value and the engineering units. Linear intercept used as a shorter form of specifying a calibrator to convert between the raw value and the engineering units. Epochs may be specified as an xs date where time is implied to be 00:00:00, xs dateTime, or string enumeration of common epochs. The enumerations are TAI (used by CCSDS and others), J2000, UNIX (also known as POSIX), and GPS. For common encodings of floating point data Calibrator to be applied to the raw uncalibrated value to arrive at the engineering/calibrated value when no Context Calibrators are provided or evaluate to true, based on their MatchCriteria. Calibrator to be applied to the raw uncalibrated value to arrive at the engineering/calibrated value when a MatchCriteria evaluates to true. Specifies real/decimal numeric value to raw encoding method, with the default being "IEEE754_1985". Number of bits to use for the float raw encoding method, with 32 being the default. Not every number of bits is valid for each encoding method. Verify the number of bits for encoding is valid for the encoding method. A changeThreshold may optionally be specified to inform systems of the minimum change in value that is significant. This is used by some systems to limit the telemetry processing and/or recording requirements. If the value is unspecified or zero, any change is significant. At the time of this writing, 16 bit encoding size is only valid in cases of IEEE754 and vendor specific MILSTD_1750A variation that is not a part of the standard. This is not meant to preclude use in the event that future floating point formats may also define this value. At the time of this writing, 32 bit encoding size is only valid in cases of IEEE754_1985, IEEE754, MILSTD_1750A, DEC, IBM, and TI. This is not meant to preclude use in the event that future floating point formats may also define this value. The IEEE754 enumeration and the IEEE754_1985 enumeration are allowed in this case and the interpretation is the same. At the time of this writing, 40 bit encoding size is only valid in the case of TI. This is not meant to preclude use in the event that future floating point formats may also define this value. At the time of this writing, 48 bit encoding size is only valid in the case of MILSTD_1750A. This is not meant to preclude use in the event that future floating point formats may also define this value. At the time of this writing, 64 bit encoding size is only valid in cases of IEEE754_1985, IEEE754, DEC, and IBM. This is not meant to preclude use in the event that future floating point formats may also define this value. The IEEE754 enumeration and the IEEE754_1985 enumeration are allowed in this case and the interpretation is the same. At the time of this writing, 80 bit encoding size is only valid in the case of IEEE754_1985. This is not meant to preclude use in the event that future floating point formats may also define this value. At the time of this writing, 128 bit encoding size is only valid in the case of IEEE754_1985 and IEEE754. This is not meant to preclude use in the event that future floating point formats may also define this value. The IEEE754 enumeration and the IEEE754_1985 enumeration are allowed in this case and the interpretation is the same. For all major encodings of integer data Calibrator to be applied to the raw uncalibrated value to arrive at the engineering/calibrated value when no Context Calibrators are provided or evaluate to true, based on their MatchCriteria. Calibrator to be applied to the raw uncalibrated value to arrive at the engineering/calibrated value when a MatchCriteria evaluates to true. Specifies integer numeric value to raw encoding method, with the default being "unsigned". Number of bits to use for the raw encoding, with 8 being the default. A changeThreshold may optionally be specified to inform systems of the minimum change in value that is significant. This is used by some systems to limit the telemetry processing and/or recording requirements, such as for an analog-to-digital converter that dithers in the least significant bit. If the value is unspecified or zero, any change is significant. Like PASCAL strings, the size of the string is given as an integer at the start of the string. SizeTag must be an unsigned Integer Bit position starts with 'zero'. This is the simplest case of a string data type where the encoding size of the string does not change. Size in bits of this string data type for both the memory allocation in the implementing software and also the size in bits for this parameter when it appears in a container. The termination character that represents the end of the string contents. For C and most strings, this is null (00), which is the default. In some string implementations, the size of the string contents (not the memory allocation size) is determined by a leading numeric value. This is sometimes referred to as Pascal strings. If a LeadingSize is specified, then the TerminationChar element does not have a functional meaning. Identical to VariableStringType but supports argument instance references. Determine the container size in bits by interrogating an instance of a parameter or argument. Determine the container size in bits by interrogating an instance of a parameter or argument and selecting a specified value based on tests of the value of that parameter or argument. In some string implementations, the size of the string contents (not the memory allocation size) is determined by a leading numeric value. This is sometimes referred to as Pascal strings. If a LeadingSize is specified, then the TerminationChar element does not have a functional meaning. The termination character that represents the end of the string contents. For C and most strings, this is null (00), which is the default. The upper bound of the size of this string data type so that the implementation can reserve/allocate enough memory to capture all reported instances of the string. Describe a variable string whose length may change between samples. Determine the container size in bits by interrogating an instance of a parameter. Determine the container size in bits by interrogating an instance of a parameter and selecting a specified value based on tests of the value of that parameter. In some string implementations, the size of the string contents (not the memory allocation size) is determined by a leading numeric value. This is sometimes referred to as Pascal strings. If a LeadingSize is specified, then the TerminationChar element does not have a functional meaning. The termination character that represents the end of the string contents. For C and most strings, this is null (00), which is the default. The upper bound of the size of this string data type so that the implementation can reserve/allocate enough memory to capture all reported instances of the string. Identical to StringDataEncodingType but supports argument instance references. Static length strings do not change in overall length between samples. They may terminate before the end of their buffer using a terminating character, or by various lookups, or calculations. But they have a maximum fixed size, and the data itself is always within that maximum size. Variable length strings are those where the space occupied in a container can vary. If the string has variable content but occupies the same amount of space when encoded should use the SizeInBits element. Specification of a variable length string needs to consider that the implementation needs to allocate space to store the string. Specify the maximum possible length of the string data type for memory purposes and also specify the bit size of the string to use in containers with the dynamic elements. The character set encoding of this string data type. Describe common encodings of string data: UTF-8 and UTF-16. See StringDataType. Static length strings do not change in overall length between samples. They may terminate before the end of their buffer using a terminating character, or by various lookups, or calculations. But they have a maximum fixed size, and the data itself is always within that maximum size. Variable length strings are those where the space occupied in a container can vary. If the string has variable content but occupies the same amount of space when encoded should use the SizeInBits element. Specification of a variable length string needs to consider that the implementation needs to allocate space to store the string. Specify the maximum possible length of the string data type for memory purposes and also specify the bit size of the string to use in containers with the dynamic elements. The character set encoding of this string data type. Defines string encodings. US-ASCII (7-bit), ISO-8859-1 (8-bit Extended ASCII), Windows-1252 (8-bit Extended ASCII), UTF-8 (Unicode), UTF-16 (Unicode with Byte Order Mark), UTF-16LE (Unicode Little Endian), UTF-16BE (Unicode Big Endian). See StringDataEncodingType. With UTF-16, encoded bits must be prepended with a Byte Order Mark. This mark indicates whether the data is encoded in big or little endian. With UTF-16LE, encoded bits will always be represented as little endian. Bits are not prepended with a Byte Order Mark. With UTF-16BE, encoded bits will always be represented as big endian. Bits are not prepended with a Byte Order Mark. With UTF-32, encoded bits must be prepended with a Byte Order Mark. This mark indicates whether the data is encoded in big or little endian. With UTF-32LE, encoded bits will always be represented as little endian. Bits are not prepended with a Byte Order Mark. With UTF-32BE, encoded bits will always be represented as big endian. Bits are not prepended with a Byte Order Mark. This element describes how a numeric value should be represented in engineering/calibrated form. The defaults reflect the most common form. Union values of common epoch definitions for document convenience. An unordered collection of algorithms Contains an unordered collection of Alias elements to describe alternate names or IDs for this named item. Applications should enforce uniqueness of individual nameSpace attribute values. Aliases are usually unique within the same nameSpace attribute value, depending on the physical meaning of that nameSpace. There are some cases where Alias values can be duplicated in a single nameSpace value. An alternate name, ID number, and sometimes flight software variable name in the code for this item. Used to contain an alias (alternate) name or ID for the object. For example, a parameter may have a mnemonic, an on-board id, and special IDs used by various ground software applications; all of these are alias's. Some ground system processing equipment has some severe naming restrictions on parameters (e.g., names must less then 12 characters, single case or integral id's only); their alias's provide a means of capturing each name in a "nameSpace". Note: the name is not reference-able (it cannot be used in a name reference substituting for the name of the item of interest). See NameDescriptionType. Aliases should be grouped together in a "namespace" so that they can be switched in and out of data extractions. The namespace generally identifies the purpose of the alternate name, whether for software variable names, additional operator names, or whatever the purpose. The alternate name or ID to use. The alias does not have the restrictions that apply to name attributes. This is useful for capturing legacy identifiers for systems with unusual naming conventions. It is also useful for capturing variable names in software, amongst other things. Use for any other data associated with a named item. May be used to include administrative data (e.g., version, CM or tags) or potentially any MIME type. Data may be included or given as an href. Identifier for this Ancillary Data characteristic, feature, or data. Optional text encoding method for the element text content of this element. The default is "text/plain". Optional Uniform Resource Identifier for this characteristic, feature, or data. Describe an unordered collection of ancillary data. AncillaryData elements capture platform/program/implementation specific data about the parent element object that is non-standard and would not fit into the schema. See AncillaryDataType. Optional list of AncillaryData elements associated with this item. Describe two or more conditions that are logically anded together. Conditions may be a mix of Condition and ORedCondition. See ORedConditionType and BooleanExpressionType. Condition elements describe a test similar to the Comparison element except that the parameters used have additional flexibility for the compare. This element describes tests similar to the ComparisonList element except that the parameters used are more flexible and the and/or for multiple checks can be specified. Describe an unordered collection of authors. See AuthorType. Contains information about an author, maintainer, or data source regarding this document. Type definition that describes the format of the contents of the Author element. A base type for boolean expression related elements that improves the mapping produced by data binding tools. A simple restriction on string for hexadecimal numbers. Must be in 0b or 0B form. Holds an arbitrarily complex boolean expression Condition elements describe a test similar to the Comparison element except that the parameters used have additional flexibility. This element describes tests similar to the ComparisonList element except that the parameters used are more flexible. This element describes tests similar to the ComparisonList element except that the parameters used are more flexible. Describe a byte order: big/little or byte list. Common byte orderings: most significant byte first (also known as big endian) and least significant byte first (also known as little endian). Describe a byte order using a byte list. The list is viewed as representing memory, the first item in the list is address 0. For mostSignificantByteFirst/big endian, the high order byte is the first byte in the list and has the highest significance followed by the less significant bytes ending with the least significant byte. For leastSignificantByteFirst/little endian, the first byte starts with the least significant byte which is first in the least and ends at the highest significant byte. For example given the value 0x0A0B0C0D the following example orderings can be formed. For mostSignificantByteFirst/big endian the significances would be listed as 3 (0x0A), 2 (0x0B), 1 (0x0C), 0 (0x0D) with ‘3’ being first in the list, and for leastSignificantByteFirst/little endian as 0 (0x0D), 1 (0x0C), 2 (0x0B), 3 (0x0A) with ‘0’ being first in the list. See DataEncodingType. Describe the comparison between the instance (value) of a parameter against either a specified value or another parameter instance. Left hand side parameter instance. Comparison operator. Right hand side parameter instance. Parameter is assumed to be of the same type as the comparison Parameter. Right hand side value. Specify as: integer data type using xs:integer, float data type using xs:double, string data type using xs:string, boolean data type using xs:boolean, binary data type using xs:hexBinary, enum data type using label name, relative time data type using xs:duration, absolute time data type using xs:dateTime. Values must not exceed the characteristics for the data type or this is a validation error. Takes precedence over an initial value given in the data type. Values are calibrated unless there is an option to override it. All comparisons must be true List of Comparison elements must all be true for the comparison to evaluate to true. Operators to use when testing a boolean condition for a validity check A simple ParameterInstanceRef to value comparison. The string supplied in the value attribute needs to be converted to a type matching the Parameter being compared to. Numerical values are assumed to be base 10 unless proceeded by 0x (hexadecimal), 0o (octal), or 0b (binary). The value is truncated to use the least significant bits that match the bit size of the Parameter being compared to. Operator to use for the comparison with the common equality operator as the default. Specify value as a string compliant with the XML schema (xs) type specified for each XTCE type: integer=xs:integer; float=xs:double; string=xs:string; boolean=xs:boolean; binary=xs:hexBinary; enum=xs:string from EnumerationList; relative time= xs:duration; absolute time=xs:dateTime. Supplied value must be within the ValidRange specified for the type. Context calibrations are applied when the ContextMatch is true. Context calibrators overide Default calibrators A MatchCriteriaType used for Context selection. Describe a custom, algorithmic alarm condition. The algorithm is assumed to return a boolean value: true or false. See AlarmType. Algorithm returns a boolean. Describe a percentage complete that is fixed from 0 to 100, or as value from a parameter. See ExecutionVerifierType. 0 to 100 percent Uses a parameter instance to obtain the value. The parameter value may be optionally adjusted by a Linear function or use a series of boolean expressions to lookup the value. Anything more complex and a DynamicValue with a CustomAlgorithm may be used. Defines an abstract schema type used as basis for NameDescriptionType and OptionalNameDescriptionType, includes an attribute for a short description and an element for a longer unbounded description. This type also provides alias set and ancillary data set See AliasSetType and AncillaryDataSetType. Optional long form description to be used for explanatory descriptions of this item and may include HTML markup using CDATA. Long Descriptions are of unbounded length. Used to contain an alias (alternate) name or ID for this item. See AliasSetType for additional explanation. Use for any non-standard data associated with this named item. See AncillaryDataSetType for additional explanation. Optional short description to be used for explanation of this item. It is recommended that the short description be kept under 80 characters in length. Describe an ordered table of integer values and associated conditions, forming a lookup table. The list may have duplicates. The table is evaluated from first to last, the first condition to be true returns the value associated with it. See DiscreteLookupType. Describe a lookup condition set using discrete values from parameters. Uses a parameter instance to obtain the value. The parameter value may be optionally adjusted by a Linear function or use a series of boolean expressions to lookup the value. Anything more complex and a DynamicValue with a CustomAlgorithm may be used Retrieve the value by referencing the value of a Parameter. A slope and intercept may be applied to scale or shift the value selected from the argument or parameter. Describe error detection/correction algorithm. A simple union type combining integer, octal, binary, and hexadecimal types Schema for a Header record. A header contains general information about the system or subsystem. The AuthorSet contains optional contact information for this document. The NoteSet contains optional technical information related to the content of this document. The HistorySet contains optional evolutionary information for data contained in this document. This attribute contains an optional version descriptor for this document. This attribute contains an optional date to be associated with this document. This attribute contains optional classification status for use by programs for which that is applicable. This attribute contains an optional additional instructions attribute to be interpreted by programs that use this attribute. This attribute contains a flag describing the state of this document in the evolution of the project using it. A simple restriction on string for hexadecimal numbers. Must be in 0x or 0X form. Describe an unordered collection of History elements. Usage is user defined. See HistoryType. Contains a history record related to the evolution of this document. Contains an Integer value; value may be provided directly or via the value in a parameter. Use a fixed integer value. Determine the value by interrogating an instance of a parameter. Determine the value by interrogating an instance of a parameter and selecting a specified value based on tests of the value of that parameter. Identical to IntegerValueType but supports argument instance references. Use a fixed integer value. Determine the value by interrogating an instance of an argument or parameter. Determine the value by interrogating an instance of an argument or parameter and selecting a specified value based on tests of the value of that argument or parameter. The Long Description is intended to be used for explanatory descriptions of the object and may include HTML markup. Long Descriptions are of unbounded length Mathematical operators used in the math operation. Behavior of each operator on the stack is described using notation (before -- after), where "before" represents the stack before execution of the operator and "after" represent the stack after execution. addition (x1 x2 -- x1+x2) subtraction (x1 x2 -- x1-x2) multiplication (x1 x2 -- x1*x2) division (x1 x2 -- x1/x2) An undefined condition exists if x2 is 0 modulo (x1 x2 -- x3) Divide x1 by x2, giving the modulo x3 An undefined condition exists if x2 is 0. Implementations should verify modulo versus remainder behavior. power function (x1 x2 -- x1**x2) An undefined condition exists if an imaginary number is the result. Imaginary numbers are not supported reverse power function (x1 x2 -- x2**x1) natural (base e) logarithm (x -- ln(x)) An undefined condition exists if x is less than or equal to 0 base-10 logarithm (x-- log(x)) An undefined condition exists if x is less than or equal to 0 exponentiation (x -- exp(x)) inversion (x -- 1/x) An undefined condition exists if x is less than 0 factorial (x -- x!) An undefined condition exists if x is less than 0 tangent (x -- tan(x)) radians cosine (x -- cos(x)) radians sine (x -- sin(x)) radians arctangent (x -- atan(x)) radians arctangent (x1 x2 -- atan2(x2, x1)) radians An undefined condition exists if x1 and x2 are 0 arccosine (x -- acos(x)) radians arcsine (x -- asin(x)) radians hyperbolic tangent (x -- tanh(x)) hyperbolic cosine (x -- cosh(x)) hyperbolic sine (x -- sinh(x)) hyperbolic arctangent (x -- atanh(x)) An undefined condition exists if x is outside the range [-1.0,+1.0] hyperbolic arccosine (x -- acosh(x)) An undefined condition exists if n is less than 1 hyperbolic arcsine (x -- asinh(x)) swap the top two stack items (x1 x2 -- x2 x1) Remove top item from the stack (x -- ) Duplicate top item on the stack (x -- x x) Duplicate top item on the stack (x1 x2 -- x1 x2 x1) signed bitwise left shift (x1 x2 -- x1 << x2) Limitation from SEI INT13-C. Use bitwise operators only on unsigned operands signed bitwise right shift (x1 x2 -- x1 >> x2) Limitation from SEI INT13-C. Use bitwise operators only on unsigned operands bitwise and (x1 x2 -- x1 & x2) Limitation from SEI INT13-C. Use bitwise operators only on unsigned operands bitwise or (x1 x2 -- x1 | x2) Limitation from SEI INT13-C. Use bitwise operators only on unsigned operands logical and (x1 x2 -- x1 && x2) The result of this can only be 0 or 1 logical or (x1 x2 -- x1 || x2) The result of this can only be 0 or 1 logical not (x1 x2 -- x1 ! x2) The result of this can only be 0 or 1 absolute value (x1 -- abs(x1)) Euclidean division quotient (x1 -- div(x1)) integer part (x1 -- int(x1)) greater than x,y (x1 x2 -- x1 > x2) The result of this can only be 0 or 1 greater than or equal x,y (x1 x2 -- x1 >= x2) The result of this can only be 0 or 1 less than x,y (x1 x2 -- x1 < x2) The result of this can only be 0 or 1 less than or equal x,y (x1 x2 -- x1 <= x2) The result of this can only be 0 or 1 equal x,y (x1 x2 -- x1 == x2) The result of this can only be 0 or 1 not equal x,y (x1 x2 -- x1 != x2) The result of this can only be 0 or 1 minimum of x,y (x1 x2 -- min(x1, x2)) maximum of x,y (x1 x2 -- max(x1, x2)) Bitwise exclusive or (XOR) (x1 x2 -- x1 xor x2) Limitation from SEI INT13-C. Use bitwise operators only on unsigned operands Bitwise not operation (x1 x2 -- x1 ~ x2) The result of this can only be 0 or 1 Limitation from SEI INT13-C. Use bitwise operators only on unsigned operands Contains either a simple Comparison, a ComparisonList, an arbitrarily complex BooleanExpression or an escape to an externally defined algorithm A simple comparison check involving a single test of a parameter value. A series of simple comparison checks with an implicit 'and' in that they all must be true for the overall condition to be true. An arbitrarily complex boolean expression that has additional flexibility on the terms beyond the Comparison and ComparisonList elements. An escape to an externally defined algorithm. Postfix (aka Reverse Polish Notation (RPN)) notation is used to describe mathmatical equations. It uses a stack where operands (either fixed values or ParameterInstances) are pushed onto the stack from first to last in the XML. As the operators are specified, each pops off operands as it evaluates them, and pushes the result back onto the stack. In this case postfix is used to avoid having to specify parenthesis. To convert from infix to postfix, use Dijkstra's "shunting yard" algorithm. Defines a name where all characters are allowed except '.', '[', ']', ':', ' ', and '/'. See NameDescriptionType. Defines a base schema type definition used by many other schema types throughout schema. Use it to describe a name with optional descriptions, aliases, and ancillary data. See NameType, LongDescriptionType, ShortDescriptionType, AliasSetType and AncillaryDataSetType. The name of this defined item. See NameType for restriction information. Describe a reference to a named item in an XTCE instance document. The named must be of schema type NameType. All name references use a Unix style file system name format where the SpaceSystem names form a path in the SpaceSystem tree. The following characters are reserved for the path: '/', ‘..’ and ‘.’ (multiple consecutive ‘/’s are treated as one). The path portion is similar to the directory path used in file system names and the path characters have similar meaning (e.g., SimpleSat/Bus/EPDS/BatteryOne/Voltage). There are three overall forms for name references: absolute path, relative path and just the name. The first two forms are called qualified name references; the last form is called an unqualified name reference. The unqualified form refers to an item in the SpaceSystem the reference is used in. The unqualified form refers to an item in the SpaceSystem the reference is used in. It is illegal for a name reference to point to no item (“a dangling name reference”). Contains an unordered collection of Notes. Usage is user defined. See NoteType. Contains a program defined technical note regarding this document. This type describes how a numeric value should be represented in engineering/calibrated form. The defaults reflect the most common form. Describes how the engineering/calibrated value of this number should be displayed with respect to the radix. Default is base 10. Describes how the engineering/calibrated value of this number should be displayed with respect to the minimum number of fractional digits. The default is 0. Describes how the engineering/calibrated value of this number should be displayed with respect to the maximum or upper bound of the number of digits. There is no default. No value specified should be interpreted as no upper bound such that all requires digits are used to fully characterize the value. Describes how the engineering/calibrated value of this number should be displayed with respect to the minimum number of integer digits. The default is 1. Describes how the engineering/calibrated value of this number should be displayed with respect to the maximum or upper bound of the integer digits. There is no default. No value specified should be interpreted as no upper bound such that all requires digits are used to fully characterize the value. Describes how the engineering/calibrated value of this number should be displayed with respect to negative values. This attribute specifies the character or characters that should be appended to the numeric value to indicate negative values. The default is none. Describes how the engineering/calibrated value of this number should be displayed with respect to positive values. This attribute specifies the character or characters that should be appended to the numeric value to indicate positive values. The default is none. Zero is considered to be specific to the implementation/platform and is not implied here. Describes how the engineering/calibrated value of this number should be displayed with respect to negative values. This attribute specifies the character or characters that should be prepended to the numeric value to indicate negative values. The default is a minus character "-". Describes how the engineering/calibrated value of this number should be displayed with respect to positive values. This attribute specifies the character or characters that should be prepended to the numeric value to indicate positive values. The default is none. Zero is considered to be specific to the implementation/platform and is not implied here. Describes how the engineering/calibrated value of this number should be displayed with respect to larger values. Groupings by thousand are specific to locale, so the schema only specifies whether they will be present and not which character separators are used. The default is false. Describes how the engineering/calibrated value of this number should be displayed with respect to notation. Engineering, scientific, or traditional decimal notation may be specified. The precise characters used is locale specific for the implementation/platform. The default is "normal" for the traditional notation. A simple restriction on string for hexadecimal numbers. Must be in 0o or 0O form. The type definition used by most elements that have an optional name with optional descriptions. Optional name of this defined item. See NameType for restriction information. Describe two or more conditions that are logically ored together. Conditions may be a mix of Condition and ANDedCondition. See ORedConditionType and BooleanExpressionType. Condition elements describe a test similar to the Comparison element except that the parameters used have additional flexibility for the compare. This element describes tests similar to the ComparisonList element except that the parameters used are more flexible and the and/or for multiple checks can be specified. Describe an unordered collection of parameters where duplicates defined by the Parameter name attribute are invalid. The ParameterSet exists in both the TelemetryMetaData and the CommandMetaData element so that each may be built independently but from a single namespace. See TelemetryMetaDataType and CommandMetaDataType. Defines a named and typed Parameter. Need to ensure that the named types actually exist Used to include a Parameter defined in another sub-system in this sub-system. Specifies the number base Defines whether the defined range between the minimum and maximum is the outside or inside the range being defined. The default, outside matches values less than the minimum and greater than the maximum. Inside matches values between the minimum and maximum. Most time values are relative to another time e.g. seconds are relative to minutes, minutes are relative to hours. This type is used to describe this relationship starting with the least significant time Parameter to and progressing to the most significant time parameter. Epochs may be specified as an xs date where time is implied to be 00:00:00, xs dateTime, or string enumeration of common epochs. The enumerations are TAI (used by CCSDS and others), J2000, UNIX (also known as POSIX), and GPS. Used to describe a relative time. Normally used for time offsets. A Relative time is expressed as PnYn MnDTnH nMnS, where nY represents the number of years, nM the number of months, nD the number of days, 'T' is the date/time separator, nH the number of hours, nM the number of minutes and nS the number of seconds. The number of seconds can include decimal digits to arbitrary precision. For example, to indicate a duration of 1 year, 2 months, 3 days, 10 hours, and 30 minutes, one would write: P1Y2M3DT10H30M. One could also indicate a duration of minus 120 days as: -P120D. An extension of Schema duration type. Hold a structure that can be repeated X times, where X is the Count Value (either fixed or dynamic) that contains the count of repeated structures. Identical to RepeatType but supports argument instance references. Value (either fixed or dynamic) that contains the count of repeated structures. A reference to a Service It is strongly recommended that the short description be kept under 80 characters in length A spline, or piecewise defined function, is a set on points from which a curve may be drawn to interpolate raw to calibrated values The order of a SplineCalibrator refers to the interpolation function. Order 0 is a flat line from the defined point (inclusive) to the next point (exclusive). Order 1 is linear interpolation between two points. Order 2 is quadratic fit and requires at least 3 points (unusual case). This order is generally not needed, but may be used to override the interpolation order for this point. The raw encoded value. The engineering/calibrated value associated with the raw value for this point. A term in a polynomial expression. The coefficient in a single term of a polynomial expression. The exponent in a single term of a polynomial expression. Should negative exponents be required, use a Math Calibrator style of definition for this type. base time units. days, months, years have obvoius ambiguity and should be avoided Describe the exponent, factor, form, and description for a unit. The unit itself is in element Unit in UnitSet. See UnitSetType. The attributes are optional because different programs use this element in different ways, depending on vendor support. Optional attribute used in conjunction with the "factor" attribute where some programs choose to specify the unit definition with these machine processable algebraic features. For example, a unit text of "meters" may have a "power" attribute of 2, resulting "meters squared" as the actual unit. This is not commonly used. The most common method for "meters squared" is to use the text content of the Unit element in a form like "m^2". Optional attribute used in conjunction with the "power" attribute where some programs choose to specify the unit definition with these machine processable algebraic features. For example, a unit text of "meters" may have a "factor" attribute of 2, resulting "2 times meters" as the actual unit. This is not commonly used. The most common method for "2 times meters" is to use the text content of the Unit element in a form like "2*m". A description of the unit, which may be for expanded human readability or for specification of the nature/property of the unit. For example, meters per second squared is of a nature/property of acceleration. The default value "calibrated" is most common practice to specify units at the engineering/calibrated value, it is possible to specify an additional Unit element for the raw/uncalibrated value. Describe a value and an associated string label, see EnumerationListType. Numeric raw/uncalibrated value to associate with a string enumeration label. If max value is given, the label maps to a range where value is less than or equal to maxValue. The range is inclusive. String enumeration label to apply to this value definition in the enumeration. An optional additional string description can be specified for this enumeration label to provide extended information if desired. Describe up to six levels: Normal, Watch, Warning, Distress, Critical, and Severe of conditions the alarm will trigger when true. The types are conditions available are a single comparison, a comparison list, a discrete lookup list, and custom algorithm. See MatchCriteriaType. An alarm state of least concern. Considered to be below the most commonly used Warning level. An alarm state of concern that represents the most commonly used minimum concern level for many software applications. An alarm state of concern in between the most commonly used Warning and Critical levels. An alarm state of concern that represents the most commonly used maximum concern level for many software applications. An alarm state of highest concern. Considered to be above the most commonly used Critical level. Describe up to six ranges where either less severe ranges are a subset of more severe ranges (outside), or more severe ranges are a subset of less severe ranges (inside). In both forms, the undefined least severe range is normal. Range values are in calibrated engineering units. See FloatRangeType. A range of least concern. Considered to be below the most commonly used Warning level. A range of concern that represents the most commonly used minimum concern level for many software applications. A range of concern in between the most commonly used Warning and Critical levels. A range of concern that represents the most commonly used maximum concern level for many software applications. A range of highest concern. Considered to be above the most commonly used Critical level. A value of outside specifies that the most severe range is outside all the other ranges: -severe -critical -distress -warning -watch normal +watch +warning +distress +critical +severe. A value of inside "inverts" these bands: -green -watch -warning -distress -critical severe +critical +distress +warning +watch. The most common form used is "outside" and is the default. Defines a base schema type used to build up the other data type specific alarm types. The definition includes a count to go into alarm (minViolations – the counts to go out of alarm is the same), a condition style alarm and a custom alarm. See AlarmConditionType, CustomAlgorithmType, BinaryAlarmConditionType, BooleanAlarmType, BinaryContextAlarmType, EnumerationAlarmType, NumericAlarmType, StringAlarmType, TimeAlarmType, TimeAlarmConditionType. A MatchCriteria may be specified for each of the 5 alarm levels. Each level is optional and the alarm should be the highest level to test true. An escape for ridiculously complex alarm conditions. Will trigger on changes to the containing Parameter. The number of successive instances that meet the alarm conditions for the alarm to trigger. The default is 1. Optionally specify the number of successive instances that do not meet the alarm conditions to leave the alarm state. If this attribute is not specified, it is treated as being equal to minViolations (symmetric). Describe any number of alarm ranges, each with its own level (normal, warning, watch, distress, critical, severe) and range form (inside or outside). Ranges may overlap, be disjoint and so forth. Ranges within the value sprectrum non-specified are non-normal. The most severe range level of value within the ranges is the level of the alarm. Range values are in calibrated engineering units. See FloatRangeType. Describe any number of alarm ranges, each with its own level (normal, warning, watch, distress, critical, severe) and range form (inside or outside). Ranges may overlap, be disjoint and so forth. Ranges within the value sprectrum non-specified are non-normal. The most severe range level of value within the ranges is the level of the alarm. Range values are in calibrated engineering units. See FloatRangeType. Defines to type of update rates: perSecond and perContainerUpdate. See RateInStreamType. Describe alarm conditions specific to the binary data type, extends the basic AlarmType. Alarm conditions for Boolean types Describe an ordered collection of context binary alarms, duplicates are valid. Process the contexts in list order. See BinaryContextAlarmType. Describe an alarm when the parameter value's rate-of-change is either too fast or too slow. The change may be with respect to time (the default) or with respect to samples (delta alarms). Use the changeType attribute to select the type: changePerSecond (time) or changePerSample (delta). The change may also be ether relative (as a percentage change) or absolute as set by the changeBasis attribute. (Delta alarms are typically absolute but percentage is conceivable). The alarm also requires the spanOfInterest in both samples and seconds to have passed before it is to trigger. For time based rate of change alarms, the time specified in spanOfInterestInSeconds is used to calculate the change. For sample based rate of change alarms, the change is calculated over the number of samples specified in spanOfInterestInSamples. A typical delta alarm would set: changeType=changePerSample, changeBasis=absoluteChange, spanOfInterestInSamples=1. A typical time based version would set: changeType=changePerSecond, changeBasis=percentageChange, and spaceOfInterestInSeconds=1. To set the ranges use maxInclusive, the following definition applies: | Normal.maxInclusive | <= | Watch.maxInclusive | <= | Warning.maxInclusive | <= | Distress.maxInclusive | <= | Critical.maxInclusive | <= | Severe.maxInclusive |. And it is further assumed the absolute value of each range and sampled value it taken to evaluate the alarm. See NumericAlarmType. Defines absoluteChange and percentageChange for use in rate of change alarms. Used by ChangeAlarmRangesType. Defines six levels: Normal, Watch, Warning, Distress, Critical and Severe. Typical implementations color the "normal" level as green, "warning" level as yellow, and "critical" level as red. These level definitions are used throughout the alarm definitions. Some systems provide a greater fidelity with the additional levels provided here. The "normal" level is not typically needed because "normal" should be construed as none of the concern levels evaluating to true. For cases where definiing "normal" is needed, refer to the specific alarm definition types. Defines the criticality level of a command. Criticality levels follow ISO 14950. Normal command. Corresponds to ISO 14950 Level D telecommand criticality. Command that is not a critical command but is essential to the success of the mission and, if sent at the wrong time, could cause momentary loss of the mission. Corresponds to ISO 14950 Level C telecommand criticality. Command that, if executed at the wrong time or in the wrong configuration, could cause irreversible loss or damage for the mission. Corresponds to ISO 14950 Level B telecommand criticality. Some space programs have called this "restricted" and may be implemented with a secondary confirmation before transmission. Command that is not expected to be used for nominal or foreseeable contingency operations, that is included for unforeseen contingency operations, and that could cause irreversible damage if executed at the wrong time or in the wrong configuration. Corresponds to ISO 14950 Level A telecommand criticality. Some space programs have called this "prohibited". In the event that a program uses this value, that program will need to define the meaning of this value to their system. In the event that a program uses this value, that program will need to define the meaning of this value to their system. Defines a changePerSecond and changePerSample for use in rate of change alarms. Used by ChangeAlarmRangesType. Describe a discrete value lookup and the value associated when the lookup evaluates to true. Value to use when the lookup conditions are true. Describe an alarm level and its enumeration label to trigger from. See EnumeratedAlarmType and EnumeratedParameterType. Defines six levels: Normal, Watch, Warning, Distress, Critical and Severe. Typical implementations color the "normal" level as green, "warning" level as yellow, and "critical" level as red. In the case of enumeration alarms, the "normal" is assumed by implementations to be any label not otherwise in an alarm state. The enumeration label is the engineering/calibrated value for enumerated types. Describe an alarm state for an enumeration label where the label is engineer/calibrated value. Note that labels may represent multiple raw/uncalbrated values. Describe a context that when true the alarm condition may be evaluated. See ContextMatchType and EnumerationAlarmType. Describe a context in terms of a parameter and value that when true enables the context alarm definition. Describe alarm conditions specific to the enumeration data type, extends the basic AlarmType with an EnumerationAlarmList. The alarms are described using the label (engineering/calibrated value) of the enumerated parameter. Enumeration labels may represent several raw/uncalibrated values, so as a result, a single alarm definition here may represent multiple raw values in the enumerated parameter. It is not necessary to define an alarm for raw/uncalibrated values that do not map to an enumeration. Implementations should implicitly define this as an alarm case, of which the manifestation of that is program/implementation specific. See EnumeratedParameterType. An additional check needs to be performed to ensure that the enumeration values in the alarms are valid enumeration values for the Parameter List of alarm state definitions for this enumerated type. Alarm state name for when no enumeration alarms evaluate to true. This defaults to "normal", which is almost always the case. Setting it to another alarm state permits a form of "inverted logic" where the alarm list can specify the normal states instead of the alarm states. Describe a floating point based range, several types of ranges are supported -- one sided and two sided, inclusive or exclusive. It would not make sense to set two mins or maxes. Used in a number of locations related to ranges: ValidFloatRangeSetType or AlarmRangeType for example. Verify that the combination provided is usable. Minimum decimal/real number value including itself. Minimum decimal/real number value excluding itself. Maximum decimal/real number value including itself. Maximum decimal/real number value excluding itself. Describe an integral based range: minInclusive and maxInclusive. Used in a number of locations related to ranges: ValidIntegerRangeSetType for example. Minimum integer value including itself. Maximum integer value including itself. A slope and intercept may be applied to scale or shift the value of the parameter in the dynamic value The alarm multi-range element type permits users to define multiple alarm ranges in a sequence that goes beyond the more typical "inside" and "outside" range definitions. It can be thought of as a "barber pole" definition. A value of outside specifies that the most severe range is outside all the other ranges: -severe -critical -distress -warning -watch normal +watch +warning +distress +critical +severe. A value of inside "inverts" these bands: -green -watch -warning -distress -critical severe +critical +distress +warning +watch. The most common form used is "outside" and is the default. The level of concern for this alarm definition. Describe alarm conditions specific to the numeric data types, extends the basic AlarmType with StaticAlarmRanges and ChangeAlarmRanges. See FloatParameterType and IntegerParameterType. StaticAlarmRanges are used to trigger alarms when the parameter value passes some threshold value. ChangeAlarmRanges are used to trigger alarms when the parameter value changes by a rate or quantity from a reference. Similar to but more lenient form of StaticAlarmRanges. Describe a parameter dependent context, that when evaluates to true, enables the use of this alarm definition. See ContextMatchType and NumericAlarmType. Contains the evaluation criteria for a parameter dependent test, that when evaluates to true, enables this alarm definition. Describe a string alarm condition based on matching a regular expression. The level and regular expression are described. The specific implementation of the regular expression syntax is not specified in the schema at this time. See StringAlarmListType. Describe an ordered collection of string alarms, where duplicates are valid. Evaluate the alarms in list order. The first to evaluate to true takes precedence. See StringAlarmLevelType. Describe alarms specific to the string data type, extends the basic AlarmType, while adding a StringAlarmList and defaultAlarmLevel attribute. The string alarm list is evaluated in list order. See ConcernsLevelsType and StringAlarmListType. Describe a context that when true the alarm may be evaluated. See ContextMatchType and StringAlarmType. An ordered collection of numeric alarms associated with a context. Process the contexts in list order. See StringContextAlarmType. Alarms associated with time data types StaticAlarmRanges are used to trigger alarms when the parameter value passes some threshold value ChangePerSecondAlarmRanges are used to trigger alarms when the parameter value's rate-of-change passes some threshold value. An alarm condition that triggers when the value changes too fast (or too slow) Context alarms are applied when the ContextMatch is true. Context alarms override Default alarms XTCE-specific replacement for xtce:NonNegativeLongType which more cleanly maps to native data types. XTCE-specific replacement for xtce:PositiveLongType which more cleanly maps to native data types. Optionally specify if this information pertains to something other than the calibrated/engineering value.