ILP-53 : Commented out Dynamics until implemented. ILPS CalculateInput removed …

…uuidSession, durSesstion and dynamics. ILPS CalculateOutput removed dynamics and rankeEstimate

ILP-53 : Commented out Dynamics until implemented. ILPS CalculateInput removed …
…uuidSession, durSesstion and dynamics. ILPS CalculateOutput removed dynamics and rankeEstimate
Skip Hines
Showing 2 changed files with 26 additions and 10 deletions
HPE/V1.2/HpeCore.xid.xml
ILP/V1.2/IlpPositioningApi.xid.xml
--- a/HPE/V1.2/HpeCore.xid.xml
View file @7334707
+++ b/HPE/V1.2/HpeCore.xid.xml
View file @7334707
@@ -32,7 +32,9 @@
        </enum>
-        <enum name="DynamicsProfile" type="Tensor.int8" default="undefined">
+<!--
+		Will resurrect when Dynamics are implemented
+        <enum name="DynamicsProfile" type="Tensor.uint8" default="undefined">
            <literal name="undefined" value="0"/>
            <literal name="stationary" value="1" />
            <literal name="spacecraft" value="2" />
@@ -45,6 +47,7 @@
            <literal name="pedestrian_jogging" value="9" />
            <literal name="pedestrian_walking" value="10" />
        </enum>
+-->
        <enum name="EstimateRanking" type="Tensor.int8" default="calcorder">
            <literal name="undefined" value="0"/>
@@ -135,9 +138,9 @@
            <comment>Bass type for time based observation data</comment>
            <elem name="epoch" type="datetime" multiplicity="1">
                <comment>
-                	Date the observation was attained. For GPS observatios (GPS_CODEPHASE_8, GPS_CODEPHASE_MIN6, GPS_CODEPHASE_MIN8, GNSS_PSEUDORANGE),
+                	Datetime the observation was attained.\n
-                	the epoch time has to have at least millisecond resolution. Fraction of a second epoch error can cause hundreds of meters of error
+					For GPS observatios (GPS_CODEPHASE_8, GPS_CODEPHASE_MIN6, GPS_CODEPHASE_MIN8, GNSS_PSEUDORANGE),
-                	in position.
+                	the epoch time has to have at least millisecond resolution. Fractions of a second epoch error can cause hundreds of meters of error in position.
                </comment>
            </elem>
        </struct>
--- a/ILP/V1.2/IlpPositioningApi.xid.xml
View file @7334707
+++ b/ILP/V1.2/IlpPositioningApi.xid.xml
View file @7334707
@@ -29,6 +29,9 @@
        <struct name="CalculateInput" type ="InputBase">
            <comment>ILP.Positioning.Calculate input data structure.</comment>
+<!--
+			these will be resurrected when Session storage is implemented.
            <elem name="uuidSession" multiplicity="0..1" type="UUID">
                <comment>
                    Optional session identifier.  See CreateSession for creating valid
@@ -46,6 +49,10 @@
                    is complete.
                </comment>
            </elem>
+-->
+<!--
+			This will be resurrected when Dynamics are implemented
            <elem name="dynamics" multiplicity="0..1" type="DynamicsProfile" default="0">
                <comment>
@@ -54,11 +61,12 @@
                    of motion. If session is specified, this value will be overridden.
                </comment>
            </elem>
+-->
            <elem name="rankEstimate" multiplicity="0..1" type="EstimateRanking" default="3">
                <comment>
-                    Specifies the sort order of the estimates produced by the hybrid calculation.  If not defined, the default value is to sort estimates
+                    Specifies the sort order of the estimates produced by the hybrid calculation.\n
-                    based on calculation order (0).
+					If not defined, the default value is to sort estimates based on calculation order (0).
                </comment>
            </elem>
@@ -133,23 +141,28 @@ If not specified, the set defaults to: Spheroid, Circle.
            <elem name="uuidSession" multiplicity="1" type="UUID">
                <comment>
-                    Session identifier.  This is the Identifier processed session used to process the
+                    Session identifier.\n
-                    calculate transaction.  If session, was not previously created by CreateSession, then
+				    This is the identifier processed session used to process the
-                    the session will not be available for future use.
+                    calculate transaction.
                </comment>
            </elem>
+<!--
+			May get resurrected when Dynamics are implemented.
            <elem name="dynamics" multiplicity="1" type="DynamicsProfile">
                <comment>
                    Specifies the dymnamics of the device providing the data.
                </comment>
            </elem>
+-->
+<!--
+			Client should remember their requested rankEstimate
            <elem name="rankEstimate" multiplicity="1" type="EstimateRanking">
                <comment>
                    Specifies the sort order of the estimates produced by the hybrid calculation.
                </comment>
            </elem>
+-->
            <elem name="status" multiplicity="1" type="CalculateStatus">
                <comment>