Skip to content

xid / specs

Go to a project
Toggle navigation
Toggle navigation pinning
b235e214 by Mike Mathews
Options

Changed the names of the XMF fields to related to XMF instead of encoding.

1 parent 62fa0518
Inline Side-by-side
Showing 1 changed file with 8 additions and 8 deletions
ILP/V1.2/IlpPositioningApi.xid.xml
......@@ -105,13 +105,6 @@
</comment>
</elem>
<elem name="obsSetEncodedFmt" multiplicity="0..1" type="EncodingFormat" default="0" ord="88">
<comment>
Encoded observation set encoding format. Observations may be passed to the service in
an encoding format different than the wire format, encoded in accordance to the
format defined by the this field. By default native format (XMF) is specified.
</comment>
</elem>
<elem name="observations" multiplicity="0..1" type="ObservationSet" ord="89">
<comment>
......@@ -122,8 +115,15 @@
</comment>
</elem>
<elem name="obsSetXmfFmt" multiplicity="0..1" type="EncodingFormat" default="0" ord="88">
<comment>
XMF observation set encoding format. XMF Observations may be passed to the service in
an encoding format different than the XNF, encoded in accordance to the
format key defined by the this field. By default (0) is the native format XMF.
</comment>
</elem>
<elem name="obsSetEncoded" multiplicity="0..1" type="xmf" ord="90">
<elem name="obsSetXmf" multiplicity="0..1" type="xmf" ord="90">
<comment>
Encoded observation set encoded in the format specified by "obsSetEncodedFmt". The base, 'native' format is XMF.
At least one of observations, obsSetEncoded, or state is required, otherwise there is insufficient data to process.
......
Styling with Markdown is supported
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!