Many resources are needed to download a project. Please understand that we have to compensate our server costs. Thank you in advance. Project price only 1 $
You can buy this project and download/modify it how often you want.
This project contains software to support the Object Management Group (OMG) Space Domain Task Force (SDTF) maintained XML Telemetry and Command Exchange (XTCE) specification.
Used by both the TelemetryMetaData and the CommandMetaData components each may be built independently.
source
<complexType name="ParameterSetType"> <annotation> <documentation xml:lang="en">Used by both the TelemetryMetaData and the CommandMetaData components each may be built independently.</documentation> </annotation> <choice maxOccurs="unbounded"> <element name="Parameter"> <annotation> <appinfo>Need to ensure that the named types actually exist</appinfo> </annotation> <complexType> <complexContent> <extension base="xtce:NameDescriptionType"> <sequence> <element name="ParameterProperties" type="xtce:ParameterPropertiesType" minOccurs="0"/> </sequence> <attribute name="parameterTypeRef" type="xtce:NameReferenceType" use="required"/> <attribute name="initialValue" type="string" use="optional"> <annotation> <documentation xml:lang="en">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. Initial values for Array or Aggregate types may not be set.</documentation> <appinfo>The value type must match the Parameter type</appinfo> </annotation> </attribute> </extension> </complexContent> </complexType> </element> <element name="ParameterRef" type="xtce:ParameterRefType"> <annotation> <documentation xml:lang="en">Used to include a Parameter defined in another sub-system in this sub-system.</documentation> </annotation> </element> </choice> </complexType>
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. Initial values for Array or Aggregate types may not be set.
appinfo
The value type must match the Parameter type
annotation
appinfo
Need to ensure that the named types actually exist
source
<element name="Parameter"> <annotation> <appinfo>Need to ensure that the named types actually exist</appinfo> </annotation> <complexType> <complexContent> <extension base="xtce:NameDescriptionType"> <sequence> <element name="ParameterProperties" type="xtce:ParameterPropertiesType" minOccurs="0"/> </sequence> <attribute name="parameterTypeRef" type="xtce:NameReferenceType" use="required"/> <attribute name="initialValue" type="string" use="optional"> <annotation> <documentation xml:lang="en">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. Initial values for Array or Aggregate types may not be set.</documentation> <appinfo>The value type must match the Parameter type</appinfo> </annotation> </attribute> </extension> </complexContent> </complexType> </element>
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. Initial values for Array or Aggregate types may not be set.
appinfo
The value type must match the Parameter type
source
<attribute name="initialValue" type="string" use="optional"> <annotation> <documentation xml:lang="en">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. Initial values for Array or Aggregate types may not be set.</documentation> <appinfo>The value type must match the Parameter type</appinfo> </annotation> </attribute>
element ParameterSetType/Parameter/ParameterProperties
A telemetered Parameter is one that will have values in telemetry. A derived Parameter is one that is calculated, usually be 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 on the ground (e.g. a ground command counter).
Used to include a Parameter defined in another sub-system in this sub-system.
source
<element name="ParameterRef" type="xtce:ParameterRefType"> <annotation> <documentation xml:lang="en">Used to include a Parameter defined in another sub-system in this sub-system.</documentation> </annotation> </element>