Updated Results structure to align better with Dataset definition.
Showing
1 changed file
with
8 additions
and
12 deletions
... | @@ -157,13 +157,9 @@ | ... | @@ -157,13 +157,9 @@ |
157 | * ResultSet Structure Definition. | 157 | * ResultSet Structure Definition. |
158 | ************************************* | 158 | ************************************* |
159 | --> | 159 | --> |
160 | <struct name="ResultSet" type="GeoSpatial.Object" rttkey="GeoSpatial.ObjectType.IlpTestResultSet"> | 160 | <struct name="ServiceResults" type="GeoSpatial.Object" rttkey="GeoSpatial.ObjectType.IlpTestResultSet"> |
161 | <comment>Specification for an ILP analysis test data result set.</comment> | 161 | <comment>Specification for an ILP analysis test data result set.</comment> |
162 | 162 | ||
163 | <elem name="uuidData" multiplicity ="0..*" type="UUID" > | ||
164 | <comment>Zero or more UUIDs identifying the survey test data used in this result set.</comment> | ||
165 | </elem> | ||
166 | |||
167 | <elem name="records" type="ResultRecord" multiplicity="0..*"> | 163 | <elem name="records" type="ResultRecord" multiplicity="0..*"> |
168 | <comment>The estimated position result records.</comment> | 164 | <comment>The estimated position result records.</comment> |
169 | </elem> | 165 | </elem> |
... | @@ -190,13 +186,9 @@ | ... | @@ -190,13 +186,9 @@ |
190 | * Results Structure Definition. | 186 | * Results Structure Definition. |
191 | ************************************* | 187 | ************************************* |
192 | --> | 188 | --> |
193 | <struct name="Results" type="GeoSpatial.Object" rttkey="GeoSpatial.ObjectType.IlpTestResults"> | 189 | <struct name="DataSetResults" type="GeoSpatial.Object" rttkey="GeoSpatial.ObjectType.IlpTestResults"> |
194 | <comment>Specification for an ILP analysis test data result set.</comment> | 190 | <comment>Specification for an ILP analysis test data result set.</comment> |
195 | 191 | ||
196 | <elem name="uuidData" multiplicity ="0..*" type="UUID" > | ||
197 | <comment>Zero or more UUIDs identifying the survey test data used in this result set.</comment> | ||
198 | </elem> | ||
199 | |||
200 | <elem name="startExecutionDate" type="datetime" multiplicity="1"> | 192 | <elem name="startExecutionDate" type="datetime" multiplicity="1"> |
201 | <comment>Date and time the test was executed.</comment> | 193 | <comment>Date and time the test was executed.</comment> |
202 | </elem> | 194 | </elem> |
... | @@ -206,9 +198,13 @@ | ... | @@ -206,9 +198,13 @@ |
206 | <comment>Duration of the execution time in milliseconds.</comment> | 198 | <comment>Duration of the execution time in milliseconds.</comment> |
207 | </elem> | 199 | </elem> |
208 | 200 | ||
209 | <elem name="resultsets" multiplicity="0..*" type="ResultSet"> | 201 | <elem name="serviceResults" multiplicity="0..*" type="ServiceResults"> |
210 | <comment>Results processed by a specified service.</comment> | 202 | <comment>Results processed by a specified service.</comment> |
211 | </elem> | 203 | </elem> |
204 | |||
205 | <elem name="uuidData" multiplicity ="0..*" type="UUID" > | ||
206 | <comment>Zero or more UUIDs identifying the survey test data used in this result set.</comment> | ||
207 | </elem> | ||
212 | </struct> | 208 | </struct> |
213 | 209 | ||
214 | <!-- | 210 | <!-- |
... | @@ -260,7 +256,7 @@ | ... | @@ -260,7 +256,7 @@ |
260 | 256 | ||
261 | <comment>Test Execution output. Note if not wanting results, the execute method will return early with a processing result code.</comment> | 257 | <comment>Test Execution output. Note if not wanting results, the execute method will return early with a processing result code.</comment> |
262 | 258 | ||
263 | <elem name="results" multiplicity="0..1" type="Results"> | 259 | <elem name="results" multiplicity="0..*" type="Results"> |
264 | <comment>The result test data set if the 'returnResults' option was selected on input.</comment> | 260 | <comment>The result test data set if the 'returnResults' option was selected on input.</comment> |
265 | </elem> | 261 | </elem> |
266 | 262 | ... | ... |
-
Please register or sign in to post a comment