XTCE13 — SpaceSystem can mean multiple things

SpaceSystem in XTCE could mean a system/subsystem, a spacecraft, or perhaps a constellation of spacecraft. There should be a tag/attribute that specifies what the SpaceSystem represents. This would help with interpretation by implementing software.

Revise add some optional grouping to SpaceSystem element

It would be useful to allow for implementers and data owners to be able to include information in the emitted XML about the grouping or hierarchy of SpaceSystem elements. This is entirely specific to the project leveraging XTCE, so the committee does not propose any constraints on the values of these two new optional attributes.

Original definition of SpaceSystemType:

<complexType name="SpaceSystemType" mixed="false">
<annotation>
<documentation xml:lang="en">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.</documentation>
</annotation>
<complexContent>
<extension base="xtce:NameDescriptionType">
<sequence>
<element name="Header" type="xtce:HeaderType" minOccurs="0">
<annotation>
<documentation xml:lang="en">The Header element contains optional descriptive information about this SpaceSystem or the document as a whole when specified at the root SpaceSystem.</documentation>
</annotation>
</element>
<element name="TelemetryMetaData" type="xtce:TelemetryMetaDataType" minOccurs="0">
<annotation>
<documentation xml:lang="en">This element contains descriptions of the telemetry created on the space asset/device and sent to other data consumers.</documentation>
</annotation>
</element>
<element name="CommandMetaData" type="xtce:CommandMetaDataType" minOccurs="0">
<annotation>
<documentation xml:lang="en">This element contains descriptions of the commands and their associated constraints and verifications that can be sent to the space asset/device.</documentation>
</annotation>
</element>
<element name="ServiceSet" type="xtce:ServiceSetType" minOccurs="0"/>
<element ref="xtce:SpaceSystem" minOccurs="0" maxOccurs="unbounded">
<annotation>
<documentation xml:lang="en">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.</documentation>
</annotation>
</element>
</sequence>
<attribute name="operationalStatus" type="token" use="optional">
<annotation>
<documentation xml:lang="en">Optional descriptive attribute for document owner convenience.</documentation>
</annotation>
</attribute>
<attribute ref="xml:base"/>
</extension>
</complexContent>
</complexType>

Proposed new definition of SpaceSystemType:

Two attributes, "systemType" and "assetType" added.

<complexType name="SpaceSystemType" mixed="false">
<annotation>
<documentation xml:lang="en">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.</documentation>
</annotation>
<complexContent>
<extension base="xtce:NameDescriptionType">
<sequence>
<element name="Header" type="xtce:HeaderType" minOccurs="0">
<annotation>
<documentation xml:lang="en">The Header element contains optional descriptive information about this SpaceSystem or the document as a whole when specified at the root SpaceSystem.</documentation>
</annotation>
</element>
<element name="TelemetryMetaData" type="xtce:TelemetryMetaDataType" minOccurs="0">
<annotation>
<documentation xml:lang="en">This element contains descriptions of the telemetry created on the space asset/device and sent to other data consumers.</documentation>
</annotation>
</element>
<element name="CommandMetaData" type="xtce:CommandMetaDataType" minOccurs="0">
<annotation>
<documentation xml:lang="en">This element contains descriptions of the commands and their associated constraints and verifications that can be sent to the space asset/device.</documentation>
</annotation>
</element>
<element name="ServiceSet" type="xtce:ServiceSetType" minOccurs="0"/>
<element ref="xtce:SpaceSystem" minOccurs="0" maxOccurs="unbounded">
<annotation>
<documentation xml:lang="en">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.</documentation>
</annotation>
</element>
</sequence>
<attribute name="systemType" type="xtce:SystemTypeType" default="unknown">
<annotation>
<documentation xml:lang="en">Type of the space system. Represents what from a space enterprise this SpaceSystem element represents. See the individual enumeration descriptions in SystemTypeType.</documentation>
</annotation>
</attribute>
<attribute name="assetType" type="string" default="unknown">
<annotation>
<documentation xml:lang="en">Broad name for the type of asset, such as spacecraft, aircraft, device, or any other that makes sense for the system.</documentation>
</annotation>
</attribute>
<attribute name="operationalStatus" type="token" use="optional">
<annotation>
<documentation xml:lang="en">Optional descriptive attribute for document owner convenience.</documentation>
</annotation>
</attribute>
<attribute ref="xml:base"/>
</extension>
</complexContent>
</complexType>

With the systemType attribute, it becomes also necessary to add a new simpleType called SystemTypeType to capture the enumerations alluded to in the documentation. This should appear immediately after the SpaceSystemType definition here.

<simpleType name="SystemTypeType">
<annotation>
<documentation xml:lang="en">The type attribute represents what from a space enterprise this SpaceSystem element represents. See the enumerations for specific details. Unknown is the default for backwards compatibility, though it should be avoided in newer documents.</documentation>
</annotation>
<restriction base="token">
<enumeration value="asset">
<annotation>
<documentation xml:lang="en">An form of asset monitored and/or controlled by the enterprise that may participate in a larger group and may be subdivided into internal components.</documentation>
</annotation>
</enumeration>
<enumeration value="assetGroup">
<annotation>
<documentation xml:lang="en">A grouping of assets that make sense to aggregate together in the data model, such as a fleet or constellation.</documentation>
</annotation>
</enumeration>
<enumeration value="assetComponent">
<annotation>
<documentation xml:lang="en">Internal systems of assets permit managing the structure of XTCE documents by decomposing the internal structures of interest to tighten the scope of an individual SpaceSystem element. The XInclude facility is also available at the SpaceSystem element for managing the size of XTCE documents, in addition to the internal organization.</documentation>
</annotation>
</enumeration>
<enumeration value="unknown">
<annotation>
<documentation xml:lang="en">The default enumeration is meant for backwards compatibility with earlier versions and should be avoided.</documentation>
</annotation>
</enumeration>
</restriction>
</simpleType>