Root Element. Also contains attributes to indicate the overall security classification of this TML stream or file. If needed individual data clusters can be labeled with a security class. for relating external subject to external subject or transducer data to external subject. An external subject (object) is external to the system. fixed version 1.0 contains a value or a set of values for describing models and functions number of points, or ranges in values element. Allowed values: positive integer. Default is 0. Allowed Values: fcn, charFrame. singleValue. Default is fcn. the value element can contain one or multiple values. Allowed Values: continuous, discrete, lastValue, returnToZero, data type of the value. Allowed values: text, number. Default number values can contain a single value or a string of values separated by a comma. Each value can contain text, number, or a range of numbers. Each range value shall contain two numbers separated by three decimal points (...), the first number identifies the closed end of the range and the second number identifies the open end of the range. Values in the range may be integer or real numbers. Reals may use E for exponent. In addition to numbers in the range the text -inf and inf can be used to represent -infinity and plus infinity respectively. For arrayType of function interpolation between values should be handled as indicated in the fcnInterpolate element. default 1. if multiple values of mult, then each value corresponds to the corresponding Characteristic Frame position or interval. Can have a set of mult or offset equalization values and a sensor modifying those values through a bindUID. The bindUID sensor value will multiply with the values in the mult element. default 0. if multiple values of offset, then each value corresponds to the corresponding Characteristic Frame position or interval. Can have a set of mult or offset equalization values and a sensor modifying those values through a bindUID. The bindUID sensor value will add with the values in the offset element. contains security of process description ISO8601 dateTime stamp a process can have zero or more inputs. This describes a single input process cycle, initiated by an input trigger uid of input fixed or forced input value not. single value or array defined by logical data structure a process can have one or more outputs. This describes a single output processing cycle, initiated by an output trigger uid of output Identification of the system ISO8601 dateTime stamp ISO8601 dateTime stamp clock counter. sysClk UID same as the system UID. There is only one clock per system. Subsystems may have clocks Period in seconds number base in which clock characters increment. Allowed values are: 2, 8, 10, 16. Default is 10 counter starting point after rollover. default 0 max counter count which roll over occurs relationships of objects within the system. characterized at the time of the system characterization. For describing positional relations of subjects external to a system. An empty posRelation tag in a data indicates that this uidRef relation is no longer exist uid of the obj being positioned. multiples allowed if in same position and orientation Identifies the absolute time reference for each sysClk. Default is any time reference in a cluster represents absolute time relating to the corresponding clock value. An empty timeRelation tag in a data stream indicates that this uidRef relation is no longer a part of the system UID of the sysClk. Default: Uid of system clock which transducer is contained in. time Datum. Allowed Values: UTC, other, Default UTC. Allowed values: dateTime, year, mo, day, hour, min, sec. Default: dateTime (ISO 8601) dataUid reference of the sensor measurements providing the absolute time reference. Connects bindUIDs to processes. connects outputs to inputs. transducer data to processes and processes to processes. An empty connect tag in a data stream indicates that this UID relation is no longer a part of the system. Example of data to data relation. attaching a process to monitor the state of the gain parameter on the steady state response through a bindUID point. longer description of the signal or the property relation connection or node UID of the connection signal data relationship data source UID of the data (live or archived). Archived data streams will have a UID indicative of the data source, time, and clk count of the start. data sink UID of the data reference. Archived data streams will have a UID indicative of the data source, time, and clk count of the start. Property to property relation or phenomenon to phenomenon relation. transmitter to receiver, Ambient to receiver, Example: thermal to voltage transducer connected to a voltage to data transducer. example optical filter on the front of an optical camera lens longer description of the property relation connection or node UID of the property relationship uidRef of the property or phenomenon If the P-to-P interface has a distance between them, then this describes the medium in which the energy propagates. Allowed values: vacuum, air, water. default air If the P-to-P interface has a distance between them, then this describes the mechanism in which the energy propagates. Allowed values: radiation, conduction, convection, osmosis. default radiation bind types on most elements enables the description of transducers in the initialization data stream of data elements. ISO8601 dateTime stamp Top level transducer classification allowed values: transmitter, receiver, transceiver. default is receiver. allowed values: insitu, remote. Default is insitu. Allowed values: attitudeIndependent (default), locationIndependent, positionalIndependent, positionalDependent uid of dataArray name of dataArray Name of mathematical term used in the transformation equations. Index of component is same as order sequence in the lds. Allowed values: columns, rows, planes default is columns The chosen object (dataSet or dataArray) repeats this many time. default 1 a dataArrays contain a homogeneous collection of either subordinate dataArrays or dataSets. data Sets contain a heterogeneous collection of one or more dataUnits uid of dataSet. name of dataSet Name of mathematical term used in the transformation equations. Index of component is the order in the sequence in the LDS structure. number of subordinate sets and/or arrays. default 1 A dataSet contains a collection of one or more heterogeneous data units or data arrays. dataArray are discouraged from being used within a dataSet when defining the logical data structure. a dataArray contains a homogeneous collection of one or more dataSets or dataArrays uid of registry object Do the tml descriptions comply with the TML Compliance Rules ISO8601 dateTime stamp ISO8601 dateTime stamp Do the TML descriptions accurately reflect actual performance specifications ISO8601 dateTime stamp ISO8601 dateTime stamp which spatial reference system (i.e. spatial datum) are spatial coordinates referenced (relative) to. Allowed values: transducer, earthCentered, earthLocal, subject. If ref system is transducer or subject then the uid of the transducer or subject must be identified in the refObjUidRef element. If the spaceRefSystem element is a transducer or a Sunbect, then this element will identify the particular Transducer or Subject. This is the UID reference of the object which position coordinates are referenced (relative) to. TCF set of positional (translations and rotations) coordinates for each shape, space separated real numbers. Order of coordinates shall be from lowest frequency to highest frequency, same as lds. Default locations and orientations are zero Allowed Values: pos, vel, accel, Default is pos. Allowed Values: x, y, z, Alpha, beta, rho, latitude, longitude, altitude, omega, phi, kappa, accuracy is in terms of the data value before adjustment by mult and offset. if a characteristic frame (i.e. number of values) of values of accuracy, then each value corresponds to the corresponding Characteristic Frame position or interval Allowed values: relative, absolute, systematic, random. default is absolute Allowed Values: gaussian, chi, chi2, possion, gamma. default is gaussian allowed values: 1sigma, 2sigma, 3sigma, 4sigma, 5sigma, 6sigma, percent, range. RMS, RSS, Default is 1sigma A single accyValue relates to whole range of parent coordinates (e.g. data or prop). If accyValue is variable over the parent coordinates then there shall be a one-to-one correspondence between the accyValues and the parent coordinates. use mult and offset to describe variances over CF the CFSubSampling can be used for chipping part of a large dataArry out and for reducing the number of points within an array for which to associate modeling parameters. there is one sub sampling element set of points for each component structure (col, row, plane). index numbers of col, row or plane position within the CFs are listed for which corresponding modeling points will be associated. sample points are separated by commas, ranges are indicated by ... between numbers which indicates a continuous interval for a single sample. interpolation between samples uses logical structure. Allowed values: column, row, plane. default is column. One cfSubSampling element for each cfStructComp required. Allowed values: positive integers from 1 to the number of columns, rows, or planes in the data structure. This number indicates the number of samples in the cfSubSampleIndexPts. use same rules as points under value An empty clusterdesc tag in a data stream indicates that this cluster is no longer contained in the data stream. description of the data cluster dataUidRef of the tap point in the system to which this cluster corresponds. UID of the transducer, process input process output, or connection node from which or to which this cluster relates. This is the UID used in the data header (i.e. reference attribute in data start tag). Is some cases a data in a single cluster may come from multiple dataUid tap points. short ID used in the data header (i.e. ref attribute in data start tag) Allowed Values: fromSystem, toSystem. default fromSystem Allowed values: binary, packedXML. verboseXML. default binary Integer number of bytes in Cluster If cluster type is binary this field describes the encoding of the header attributes. binary files will contain only the contents of the attributes and not the attribute tag. The binary header will not contain the left carrot and the letters "data" at the beginning of the header either, nor the right carrot at the end of the header. ref, reference, dateTime, contents and ismClass attributes will be encoded and handled as "string" type Allowed values: ref, clk, reference, dateTime, contents, seq, total, ismClass. Default ref Allowed values: text, number. Default is number. if fixed field size. Default is fixed size. number of bits. default 8 number of significant bits. default 8 if numSigBits is less than numBits this element indicates how sigbit are justified. Allowed values: left, right. Default: right if field is variable size. delimiter used to separate variable size dataUnits in cluster when encode is text (utf or ucs). default delimiter is none. empty tag means none. delimiter used to separate variable size dataUnits in cluster when encode is text (utf or ucs). default delimiter is none. Empty tag means none Allowed values: big, little. default little Allowed values: ucs16, utf8, signInt, unsignInt, real, bcd. default unsignInt. when numbers are encoded as text the number base must be understood. Allowed values: 2, 8, 10, 16, 32, 64, 128. default 10 how should the text or number be handled in the client application. Allowed values: anuURI, boolean, byte, double, float, short, string, int, integer, long, nonNegativeInteger, nonPositiveInteger, positiveInteger, unsignedByte, unsignedInt, unsignedShort, unsignedLong. describes what time tag is used for the cluster. Useful when parent systems normalize clocks from child components. This element also describes how accurately the sysClk value is applied to the cluster start instant. This is different from the accuracy of the system clock. if clk is used in the start tag and multiple clocks are used in a system. Default is the first parent system clock This unit describes the encoding of the dataUnit identified in the dataUnitUidRef child element. Some clusters which represent only an event from a source or a trigger are empty and may not contain any dataUnits. UID of the dataUnit from the logical structure. Allowed values: text, number, binBlob. Default is text. if fixed field size default 8 default if numSigBits is less than numBits this element indicates how sigbit are justified. Allowed values: left, right. Default: right if field is variable size. Default is variable size. delimiter used to separate variable size dataUnits in cluster when encode is text (utf or ucs). default delimiter is none. Empty tag means none. default delimiter is none. Empty tag means none. Allowed values: big, little. default little Allowed values: ucs16, utf8, signInt, unsignInt, real, complex, bcd. default utf8. When clusterType is not binary only utf8 is allowed in cluster. All types are allowed when clusterType is binary. Complex values are exchanged as two phenomenon (mag and phase or real and imaginary components) or as a single complex number. when numbers are encoded as text the number base must be understood. Allowed values: 2, 8, 10, 16, 32, 64, 128. default 10 how should the text or number be handled in the client application. Allowed values: anuURI, boolean, byte, double, float, short, string, int, integer, long, nonNegativeInteger, nonPositiveInteger, positiveInteger, unsignedByte, unsignedInt, unsignedShort, unsignedLong. number of characteristic frames in a cluster or the number of clusters which comprise a large characteristic frame. default = 1. example: 2 means 2 CF per cluster, -2 means 2 clusters per CF. Allowed values: signed integer. zero not allowed. This is the order in which data is sent in the cluster or CF (whichever is larger) relative to the logical data structure. The order of structure components are listed from lowest freq to highest frequency order. If transport sequence is blank then the sequence is the same as the logical order (sequence) for that structure component. Sequence of (in this element - seqOfThisDataStruct) in the data structure identified in the next element (inThisDataStruct). seqOfBitsInUnit, seqOfUnitsInSets, seqOfSetsInCf, seqOfCfInClust. Identify the dataStructComponent in this element by dataUidRef. dataUid of the cluster is "cluster" Sequence of the data structure components identified in the previous element (seqOfThisDataStruct) in the data structure identified in this element (inThisDataStruct). seqOfBitsInUnit, seqOfUnitsInSets, seqOfSetsInCf, seqOfCfInClust. Identify the dataStructComponent in this element by dataUidRef. dataUid of the cluster is "cluster" Allowed values; The sequence shall contain a string of value separated by a comma. Each value can be a positive integer or a range. ranges shall be indicated by two integer numbers separated by three sequential decimal points (....) to indicate a run from the first number to the second this element carries the date to or from transducer systems. The data element will carry a single instance or a continuous stream of a condition or set of synchronous conditions time tag to the precise instant of creation. There is no XML markup of data within the data tag. A system description will describe the decoding and understanding of the data within the data tag. alias or short id reference of transducer or process producing this data sys clock state at trigger point to data cluster. For low sampling frequency transducers this high frequency clock state may not be required. A full dateTime attribute may suffice for time synchronization of data. this is the full UID reference to the cluster description Full qualified date and time of transducer or process producing this data. For low sampling frequency transducers this high frequency clock state may not be required. A full dateTime attribute may suffice for time synchronization of data. If a binary stream header does not contain a contents field then the data cluster is by default explicit data. This field is encoded as a binary (2-bits) "00" in a binary file if the field is contained. if no "total" attribute exist then this attribute can be used to number the data elements like a count, this enables the receipt end to determine if any data clusters were lost. total in sequence e.g. 1 of 4, 2 of 4. 1 and 2 being the seq number and 4 being the total security classification of each data cluster. Overall data classification of transducer data in clusterDescription. Overall classification of file or stream in tml start tag. an elemental unit of data. one description for each unit uid of dataUnit name of dataUnit Name of mathematical term used in the transformation equations. Index of component is the order in the sequence in the LDS structure. Allowed values: number, complexNumber, text, or binaryBlob. default is number If dataType is binaryBlob then number of bytes in the binary blob. Not used for transducer structures, only for process structures. the logical structure of data (i.e. of the characteristic frame). This is not necessarily the structure or order that data is communicated in. The transmission order is defined in the cluster description. The transmission order is defined relative to the logical order. uid of lds name of lds Allowed values: 0, 1, 2, 3. Default is 0. dimensionality of the logical data structure (lds). number of structure components used for giving hints for data representation. 0 dim is a single value, 1 dim is a series of columns, rows or planes, 2 dim is any order of two structure components (col-row, col-plane, or row-plane), and a 3 dim is any order of three structure components col-row-plane Number of dataSets or dataArrays in the Characteristic Frame. Allowed Value: positive integer. Default:1 logical data structure of the characteristic frame. Lowest frequency array first. Connects transducer to bindUids. Associate transducer data to a (remote) object. This may occur after data acquisition. An object is either a transducer, subject or their properties. Many subjects may be related to data in a dataArray. The objects can be related to data units, sets and arrays to subjects. description of the signal or the property relation connection or node UID of the connection signal data or property relationship Object can be a single transducer (dangle relation), a single dataUID, or many subjects can be related to a single data unit. probabilities can be assigned to each relation. name of the object identify object as a transducer or a subject. Allowed Values: subject, transducer. Default: subject UID of the object (subject or transducer, or probable subject). local id of the subject if multiple ids are used to associate with each cell of the logical structure. if localId assigned to objUidRef for building CF of obj to data (i.e.CF) relationships. Sequence of values is the same as the sequence in the data (logical data structure or subsampled data structure, if present) Value range -1 to 1. -1 is 100% no confidence. confidence values match same sequence as logical data structure or subsampled data structure, if present (if multiple objects in data structure) UID of the data reference. Archived data streams will have a UID indicative of the data source, time, and clk count of the start. This relation describes object to object relations. Attaching a transducer to an object (object is a subject or a transducer) (i.e. dangle, where the only thing the transducer interfaces to is that subject. (cant different individual data many measures with many individual subjects, see objToData). The transducer to transducers relation does not include phenomenon to phenomenon connections, see dataToData description of the relation uid of the relationship many objects can be related to a many objects. probabilities can be assigned to each relation name of the object identify object as a transducer or a subject. Allowed Values: subject, transducer. Default: subject if objType is subject then identify if direct or indirect subject. Allowed values: direct, indirect. Default is direct. UID of the subject (or probable subject). local id of the subject if multiple ids are used to associate with each cell of the logical structure. Sequence of values is the same as the sequence in the data (logical data structure) confidence of relationship (-1 to 1). -1 is 100% no confidence. confidence values match same sequence as logical data structure (if multiple values in data structure) A transducer can be a stand alone object or part of a system. Describes derivation of output dataUnits relative to input dataUnits or constants. An empty process tag in a data stream indicates that this process is no longer a part of the system input to output mapping. one or more mappings for each dataUnit. Can have property-property, property-data, or data-property mappings. property-property-property and property-property-data mappings are also allowed as long as independent property values can be found somewhere. Separate mappings can be used for different hystersis directions or for non-continuous or broken functions. Allowed values code, plot. Default: plot allowed values: increasing, decreasing, both. default both Is response calibrated, or is response a relative reading? true of false. Default: true For uncalibrated responses is the output proportional to the input? true of false. Mult factors can also reflect prop or inversely prop for calibrated responses. Default: true. a process input can be determined from its output. Allowed Values: true, false. default true a time shift in the input only results in a time shift in the output. Allowed Values: true, false. default true allowed values: true or false. do not need explicit Phen plot values if linear is true. Phen and data mult and offset can be used if there are no limits. default true Allowed values: continuous, discrete, lastValue, returnToZero. how to interpolate between corresponding data values between adjacent CF's. default is continuous Allowed values: continuous, discrete, lastValue, returnToZero. how to interpolate between data values within a CF. default continuous values for the physical property (phenomenon) axis of the input output transfer function Is the physical property (phenomenon) the input or output for this dataUnit. Allowed values: input, output. Default: input from Physical Property (Phenomenon) Dictionary Qualifier for the property. From Qualifier Dictionary. e.g. aveValue, rmsValue, rssValue, instValue, accumulatedValue, rateOfChange, range, min, max... From Units Of Measure Dictionary (SI Units) if the physical property (phenomenon) had a direction associated with it such as torque or force. direction relative to the transducer reference system. Allowed Values: horizontal, vertical, +xTranslation, -xTranslation, +yTranslation, -yTranslation, +zTranslation, -zTranslation, +alpha, -alpha, +beta, -beta, +rhoTranslation, -rhoTranslation, +latTranslation, -latTranslation, +longTranslation -longTranslation, +altTranslation, -altTranslation, +omegaRotation, -omegaRotation, +phiRotation, -phiRotation, +kappaRotation, -kappaRotation, none Default: none Name of mathematical term used in the transformation equations. If a calibrated source is available this elements identifies the calibration level or points (bindUID) to the calibrated sensor measuring the source. This is used for post correcting relative readings Default: none values for the data axis of the input output transfer function Is the data an input or an output for this dataUnit. Allowed values: input, output. Default: output uid of the data form the logical data structure (dataUnit) to which this response model corresponds Name of mathematical term used in the transformation equations. data resulting from calibrated source. or bindUID points to sensor measurement measuring calib source. Default: none computer code of the transfer process from input to output Allowed Values: source, exe default: source Allowed Values: C, C++, Java, Fortran, C Sharp, Basic, Visual Basic. Default: C Listing of code. Base64 encoded executable or source code with unallowed XML characters escaped out time domain or frequency domain impulse characteristics for linear time invariant transforms. May have a separate response for each dataUnit and for each type (freq and time). Or dataUnits within a data Set may share the same response. same as uidRef in attributes Allowed values: freq, time. default is time. indicates if frequency of time domain descriptions. amplitude dependent axis. time domain independent axis. frequency domain independent axis. one for each dataUnit and for each type of freqResp (carrier, modulation, and powerSpectrialDensity) and each type of plot amp vs freq and phase vs freq (can combine plots onto one as well) same as uidRef in attributes Allowed values: carried, modulation, PSD (pwrSpectralDensity). default carrier Set of point coordinates describing amplitude dependent axis Set of point coordinates describing phase dependent axis Set of point coordinates describing frequency independent axis Allowed values: spherical, rectangular, cylindrical, wgs84elliptical. default is spherical. corresponding UID of dataUnit, dataSet, or data Array. If data array then all subordinate data structures share same model (row, col, or plane), if dataSet then all data units share same model (cf), if dataUnit then only that units model is described (cf). Multiple AS are combined as spatial intersections. e.g. one for columns and one for rows. Typically every cell within a multiple cell CF will share the same shape but have unique positions. This is the shape of the AS for the power profile indicated. May also have multiple shapes to define multiple lobes of energy fields. Multiple shapes within an AS are combined as a spatial unions. The position elements defines the position of each shape. The equi-power surface power level compared to the point of transmission or reception. default is -3db beam pattern, pwrProfile="-3". one set of coordinates for each spatial axes. Each shape is defined relative to an arbitrary data spatial reference system. Allowed values: x, y, z, alpha, beta, rho. values contains a string of real numbers. The mult and offset are single values, unless the shape varies over the Characteristic Frame then the mult and offset may contain a Characteristic Frame array of values. simple IFOV alpha=0, beta=0. (ray where rho is infinite) location and attitude of ambiguity shape This is the subject (object, thing) that relates to the phenomenon (property) that is affected or detected by the transducer. The relation between a subject and transducer data or subject and subject is described in the relationship element. An empty subject tag in a data stream indicates that this object is no longer a part of the system An empty system tag (with id) in a data stream indicates that the system is no longer available in the stream, or if system was not previously part of the parent system it will be added to the parent system. Allowed Values: private, privateOnDataRecipt, privateOnInputTrig, pvtOnChgOutput. publicOnTrigReciept. public trigger: controllable by external commands. private trigger: uncontrollable by external commands. Virtual trig sensor puts sysClk time in data tag. If public a bindUid is made available. default trigger is privatePeriodic. if trigger is public then this identifies the uidRef of trigger source (command). Whenever a data cluster is sent to this UID or to the uid of a process that is bound to this uid then this transducer or process cycle will trigger. The bindUid enables late binding of the trigger source if private trigger is periodic then, trigger period in seconds time duration of the CF in seconds. Can also be determined by the CF offset time values by subtracting the smallest offset time from the largest offset time. Duration does not vary over the CF. Only one value. latency time in seconds (real number). Time between the input and the output. Transducer time tags should be corrected to reflect correct input time for receivers and output time for transmitters. Latency for processes reflects the process delay. Latency time does not vary over the CF. Only one value. data integration time for each sample in the CF. Each dataunit may have a different time. This element contains the number of samples in a CF or the number indicated by the noOfSubSampledIndexPoints element in the CFsubSamplingSequence or just one time. If just one time then the same time applies to all sample in the CF. corresponding UID of dataUnit or dataSet. Duplicate of uid in identification element Default: Uid of dataSet cfOffSetTime contains time offsets for each dataUnit or dataSet in the CF relative to the clock attribute (clk or dateTime) in the data start tag. contains the number of time values indicated by the numSubSampledIndexPoints in the cfSubSampling child element. or num corresponding UID of dataUnit or dataSet. Duplicate of uid in identification element Default: Uid of dataSet A transducer can be a stand alone object or part of a system. An empty transducer tag in a data stream indicates that this transducer is no longer a part of the system short descriptive name of element unique ID for this element the contents of this element are exactly the same as the contents of the uidRef element. no need repeating it. (similar to xlink) indication of the complexity of handling this data. Allowed Values: 1A - 1F, 2A -2F, 3A - 3F, 4A - 4F, 5A - 5F. default 1A