-
Key: XTCE12-397
-
Status: closed
-
Source: Northrop Grumman ( Mr. Joseph Vlietstra)
-
Summary:
MetaCommandStep argument values are assigned using <ArgumentList> / <Argument> elements. Using these elements creates two issues in the XTCE model:
- Two different element definitions for <ArgumentList> / <Argument>
- <MetaCommandStep> / <ArgumentList> / <Argument>
- <MetaCommand> / <ArgumentList> / <Argument>
- Two XML implementations of the ArgumentAssignment concept:
- <MetaCommandStep> / <ArgumentList> / <Argument>
- <BaseMetaCommand> / <ArgumentAssignmentList> / <ArgumentAssignment>
Recommend replacing the argument assignment elements in <MetaCommandStep> with the elements used for <BaseMetaCommand>.
This would provide a more unified and descriptive definition. - Two different element definitions for <ArgumentList> / <Argument>
-
Reported: XTCE 1.1 — Tue, 6 Dec 2016 18:00 GMT
-
Disposition: Resolved — XTCE 1.2
-
Disposition Summary:
Use ArgumentAssignmentList
In the complexType MetaCommandStepType, add the annotation:
<annotation>
<documentation>Describe a MetaCommand step, consisting MetaCommand reference and argument list. See MetaCommandStepListType and NameReferenceType.</documentation>
</annotation>and replace the element:
<element name="ArgumentList" type="xtce:ArgumentValueAssignmentListType" minOccurs="0"/>
with:
<element name="ArgumentAssignmentList" type="xtce:ArgumentAssignmentListType" minOccurs="0"/> -
Updated: Tue, 10 Jul 2018 14:22 GMT
XTCE12 — MetaCommandStep argument assignment
- Key: XTCE12-397
- OMG Task Force: XML Telemetric & Command Exchange Format 1.2 (XTCE) RTF