Skip to content

xid / specs

Go to a project
Toggle navigation
Toggle navigation pinning
392403c1 by Skip Hines
Options

Updated V1.2 to use Tensor/V1.0.0/ApiBase.xid.xml

1 parent 5158b0c6
Inline Side-by-side
Showing 11 changed files with 137 additions and 521 deletions
HPE/V1.2/README.md 0 → 100644
# HPE XIDs #
HPE XIDs do not encode their ordinals (i.e. tags and offets). XIDData.prop is required to maintain backward compatibility.
## Generate / Verify XIDData.prop ##
~~~sh
$ java -Xnoclassgc -jar $XIDSDK/bin/xidcg.jar \
-v \
-prop https://xid.location.studio/Tensor/V1.0.0/XIDData.prop \
-prop https://xid.location.studio/HPE/V1.2/XIDData.prop \
https://xid.location.studio/HPE/V1.2/HpeCellular.xid.xml \
https://xid.location.studio/HPE/V1.2/HpeCore.xid.xml \
https://xid.location.studio/HPE/V1.2/HpeGnss.xid.xml \
https://xid.location.studio/HPE/V1.2/HpeUsage.xid.xml \
https://xid.location.studio/HPE/V1.2/HpeWiFi.xid.xml
OR
$ java -Xnoclassgc -jar $XIDSDK/bin/xidcg.jar \
-v \
-prop ../../Tensor/V1.0.0/XIDData.prop \
-prop XIDData.prop \
HpeCellular.xid.xml \
HpeCore.xid.xml \
HpeGnss.xid.xml \
HpeUsage.xid.xml \
HpeWiFi.xid.xml
~~~
If xidcg reports:
~~~
Generating: xidout/meta/XID/XIDData.prop
~~~
Then something has changed and XIDData.prop needs to get updated.
ILP/V1.1.1/ApiBase.xid.xml deleted 100644 → 0
<?xml version="1.0" encoding="UTF-8" ?>
<specification xmlns="https://xid.location.studio/schema/V1.0.0/XtensibleInterfaceDefinition.xsd"
xmlns:xid="https://xid.location.studio/schema/V1.0.0/XtensibleInterfaceDefinition.xsd"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="https://xid.location.studio/schema/V1.0.0/XtensibleInterfaceDefinition.xsd https://xid.location.studio/schema/V1.0.0/XtensibleInterfaceDefinition.xsd"
identity="ApiBase.xid.xml">
<title>ILP Services API Base Definitions</title>
<comment>
This document defines the common types API service interface for the ILP and Simultaneous Localization
and Mapping (SLAM) services definitions. The service provides access to ILP and SLAM technologies for position
calculation for devices and services communicating via standard
IP based protocols. The API currently supports XMF and JSON wire formats.
</comment>
<import ref="https://xid.location.studio/Tensor/V1.0.0/Definitions.xid.xml" local="Definitions.xid.xml" />
<import ref="https://xid.location.studio/Tensor/V1.0.0/Common.xid.xml" local="Definitions.xid.xml" />
<import ref="https://xid.location.studio/HPE/V1.1.1/HpeCore.xid.xml" local="HpeCore.xid.xml" />
<import ref="https://xid.location.studio/HPE/CommonDefs/V1.1.1/HpeGnss.xid.xml" local="HpeGnss.xid.xml" />
<import ref="https://xid.location.studio/HPE/CommonDefs/V1.1.1/HpeCellular.xid.xml" local="HpeCellular.xid.xml" />
<import ref="https://xid.location.studio/HPE/CommonDefs/V1.1.1/HpeWiFi.xid.xml" local="HpeWiFi.xid.xml" />
<namespace name="ILP">
<using namespace="HPE"/>
<using namespace="Tensor"/>
<!--
*******************************
*InputBase Type Definition
*******************************
-->
<struct name="InputBase" >
<comment>Base input fields for operations supporting asynchronous transaction information.</comment>
<elem name="directive" multiplicity="0..*" type="NameValue">
<comment>
A set of directives to influence processing.
</comment>
</elem>
<elem name="devid" multiplicity="1" type="string">
<comment>
Required device identifier, that provides a consistent multi-transaction identifier
for a device or equivalent (e.g. service identifier) providing the data. Any errors or issues resulting from processing the data will include this identifier
in the system logs, providing traceability. Identifier should be unique.
</comment>
</elem>
<elem name="etid" multiplicity="0..1" type="string">
<comment>
Optional external transaction identifier for the caller to uniquely identify and track
the transaction and corresponding results. These identifiers will appear in the
ILP system logs for traceability analysis. The format of the transaction identifier is up to the caller
and can be anything: e.g. [uuid], [id1.subid0], [numerical], etc. This data is never interpreted by
the ILP system.
</comment>
</elem>
</struct>
<!--
*******************************
*OutputBase Type Definition
*******************************
-->
<struct name="OutputBase" >
<comment>Base output fields common to operations supporting asynchronous returning transaction information.</comment>
<elem name="devid" multiplicity="0..1" type="string">
<comment>
Device identifier provided at operation input, provides a consistent identifier
for a device or equivalent (e.g. service identifier) providing the data. Any errors or issues resulting from processing the data will include this identifier
in the system logs, providing traceability.
</comment>
</elem>
<elem name="etid" multiplicity="0..1" type="string">
<comment>
Optional external transaction identifier for the caller to uniquely identify and track
the transaction and corresponding results. These identifiers appear in the
ILP system logs for traceability analysis. The format of the transaction identifier is up to the caller
and can be anything: e.g. [uuid], [id1.subid0], [numerical], etc. This data is never interpreted by
the ILP system.
</comment>
</elem>
<elem name="resultcode" type="ResultCode" multiplicity="1" >
<comment>Result of the operation.</comment>
</elem>
<elem name="errinfo" type="Tensor.string" multiplicity="0..1">
<comment>Error information if result was not success.</comment>
</elem>
</struct>
</namespace>
</specification>
ILP/V1.2/ApiBase.xid.xml deleted 100644 → 0
<?xml version="1.0" encoding="UTF-8" ?>
<specification xmlns="https://xid.location.studio/schema/V1.0.0/XtensibleInterfaceDefinition.xsd"
xmlns:xid="https://xid.location.studio/schema/V1.0.0/XtensibleInterfaceDefinition.xsd"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="https://xid.location.studio/schema/V1.0.0/XtensibleInterfaceDefinition.xsd https://xid.location.studio/schema/V1.0.0/XtensibleInterfaceDefinition.xsd"
identity="ApiBase.xid.xml">
<title>ILP Services API Base Definitions</title>
<comment>
This document defines the common types API service interface for the ILP and Simultaneous Localization
and Mapping (SLAM) services definitions. The service provides access to ILP and SLAM technologies for position
calculation for devices and services communicating via standard
IP based protocols. The API currently supports XMF and JSON wire formats.
</comment>
<import ref="https://xid.location.studio/Tensor/V1.0.0/Definitions.xid.xml" local="Definitions.xid.xml" />
<import ref="https://xid.location.studio/Tensor/V1.0.0/Common.xid.xml" local="Definitions.xid.xml" />
<import ref="https://xid.location.studio/HPE/V1.2/HpeCore.xid.xml" local="HpeCore.xid.xml" />
<import ref="https://xid.location.studio/HPE/V1.2/HpeGnss.xid.xml" local="HpeGnss.xid.xml" />
<import ref="https://xid.location.studio/HPE/V1.2/HpeCellular.xid.xml" local="HpeCellular.xid.xml" />
<import ref="https://xid.location.studio/HPE/V1.2/HpeWiFi.xid.xml" local="HpeWiFi.xid.xml" />
<namespace name="ILP">
<using namespace="HPE"/>
<using namespace="Tensor"/>
<!--
*******************************
*InputBase Type Definition
*******************************
-->
<struct name="InputBase" >
<comment>Base input fields for operations supporting asynchronous transaction information.</comment>
<elem name="directive" multiplicity="0..*" type="NameValue">
<comment>
A set of directives to influence processing.
</comment>
</elem>
<elem name="devid" multiplicity="1" type="string">
<comment>
Required device identifier, that provides a consistent multi-transaction identifier
for a device or equivalent (e.g. service identifier) providing the data. Any errors or issues resulting from processing the data will include this identifier
in the system logs, providing traceability. Identifier should be unique.
</comment>
</elem>
<elem name="etid" multiplicity="0..1" type="string">
<comment>
Optional external transaction identifier for the caller to uniquely identify and track
the transaction and corresponding results. These identifiers will appear in the
ILP system logs for traceability analysis. The format of the transaction identifier is up to the caller
and can be anything: e.g. [uuid], [id1.subid0], [numerical], etc. This data is never interpreted by
the ILP system.
</comment>
</elem>
</struct>
<!--
*******************************
*OutputBase Type Definition
*******************************
-->
<struct name="OutputBase" >
<comment>Base output fields common to operations supporting asynchronous returning transaction information.</comment>
<elem name="devid" multiplicity="0..1" type="string">
<comment>
Device identifier provided at operation input, provides a consistent identifier
for a device or equivalent (e.g. service identifier) providing the data. Any errors or issues resulting from processing the data will include this identifier
in the system logs, providing traceability.
</comment>
</elem>
<elem name="etid" multiplicity="0..1" type="string">
<comment>
Optional external transaction identifier for the caller to uniquely identify and track
the transaction and corresponding results. These identifiers appear in the
ILP system logs for traceability analysis. The format of the transaction identifier is up to the caller
and can be anything: e.g. [uuid], [id1.subid0], [numerical], etc. This data is never interpreted by
the ILP system.
</comment>
</elem>
<elem name="resultcode" type="ResultCode" multiplicity="1" >
<comment>Result of the operation.</comment>
</elem>
<elem name="errinfo" type="Tensor.string" multiplicity="0..1">
<comment>Error information if result was not success.</comment>
</elem>
</struct>
</namespace>
</specification>
ILP/V1.2/IlpApiBase.xid.xml deleted 100644 → 0
<?xml version="1.0" encoding="UTF-8" ?>
<specification xmlns="https://xid.location.studio/schema/V1.0.0/XtensibleInterfaceDefinition.xsd"
xmlns:xid="https://xid.location.studio/schema/V1.0.0/XtensibleInterfaceDefinition.xsd"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="https://xid.location.studio/schema/V1.0.0/XtensibleInterfaceDefinition.xsd https://xid.location.studio/schema/V1.0.0/XtensibleInterfaceDefinition.xsd"
identity="IlpApiBase.xid">
<title>ILP Hybrid Positioning Services API Base Definitions</title>
<comment>
This document defines the common types API service interface for the IoT Location Platform (ILP).
The service provides hybrid position calculation for devices and services communicating
via standard IP based protocols. The API currently supports XMF and JSON wire formats.
</comment>
<import ref="https://xid.location.studio/HPE/V1.2/HpeGnss.xid.xml" local="HpeGnss.xid.xml" />
<import ref="https://xid.location.studio/HPE/V1.2/HpeCellular.xid.xml" local="HpeCellular.xid.xml" />
<import ref="https://xid.location.studio/HPE/V1.2/HpeWiFi.xid.xml" local="HpeWiFi.xid.xml" />
<namespace name="ILP">
<using namespace="HPE"/>
<using namespace="Tensor"/>
<!--
*******************************
*IlpInputBase Type Definition
*******************************
-->
<struct name="IlpInputBase" >
<comment>Base input fields for operations supporting asynchronous transaction information.</comment>
<elem name="idDevice" multiplicity="1" type="string">
<comment>
Required device identifier, that provides a consistent multi-transaction identifier
for a device or equivalent (e.g. service identifier) providing the data. Any errors or issues resulting from processing the data will include this identifier
in the system logs, providing traceability. Identifier should be unique.
</comment>
</elem>
<elem name="idTransaction" multiplicity="0..1" type="string">
<comment>
Optional transaction identifier for the caller to uniquely identify and track
the transaction and corresponding results. These identifiers will appear in the
ILP system logs for traceability analysis. The format of the transaction identifier is up to the caller
and can be anything: e.g. [uuid], [id1.subid0], [numerical], etc. This data is never interpreted by
the ILP system.
</comment>
</elem>
<!-- THis is future, don't uncomment until design issues resolved. M. Mathews/s. Hines 161130
<elem name="urlCallback" multiplicity="0..1" type="string">
<tag key="life-cycle" value="future" />
<comment>
Optional asynchronous callback used to callback client servers during long operations. Not all
interfaces may support this.
</comment>
</elem>
-->
</struct>
<!--
*******************************
*IlpOutputBase Type Definition
*******************************
-->
<struct name="IlpOutputBase" >
<comment>Base output fields common to operations supporting asynchronous returning transaction information.</comment>
<elem name="idDevice" multiplicity="1" type="string">
<comment>
Device identifier provided at operation input, provides a consistent identifier
for a device or equivalent (e.g. service identifier) providing the data. Any errors or issues resulting from processing the data will include this identifier
in the system logs, providing traceability.
</comment>
</elem>
<elem name="idTransaction" multiplicity="0..1" type="string">
<comment>
Optional transaction identifier for the caller to uniquely identify and track
the transaction and corresponding results. These identifiers appear in the
ILP system logs for traceability analysis. The format of the transaction identifier is up to the caller
and can be anything: e.g. [uuid], [id1.subid0], [numerical], etc. This data is never interpreted by
the ILP system.
</comment>
</elem>
<!-- THis is future, don't uncomment until design issues resolved. M. Mathews/s. Hine 161130
<elem name="urlCallback" multiplicity="0..1" type="string">
<tag key="life-cycle" value="future" />
<comment>
Optional asynchronous callback used to callback client servers during long operations. Not all
interfaces may support this.
</comment>
</elem>
-->
</struct>
</namespace>
</specification>
ILP/V1.2/IlpAssistanceApi.xid.xml
......@@ -12,8 +12,9 @@
and services communicating via standard IP based protocols. The API currently supports XMF and JSON wire formats.
</comment>
<import ref="https://xid.location.studio/ILP/V1.2/IlpApiBase.xid.xml" local="IlpApiBase.xid.xml" />
<import ref="https://xid.location.studio/Tensor/V1.0.0/ApiBase.xid.xml" local="ApiBase.xid.xml" />
<import ref="https://xid.location.studio/HPE/V1.2/HpeGnss.xid.xml" local="HpeGnss.xid.xml" />
<namespace name="ILP">
<using namespace="HPE"/>
<using namespace="Tensor"/>
......@@ -24,7 +25,7 @@
*******************************************************
-->
<!-- GnssDataInput structure -->
<struct name="GnssDataInput" type="IlpInputBase">
<struct name="GnssDataInput" type="InputBase">
<comment>ILP.Assistance.GnssData input request data.</comment>
<!-- Define internal data structure -->
......@@ -70,7 +71,7 @@
</comment>
</elem>
<elem name="location" multiplicity="0..1" type="Shape">
<elem name="location" multiplicity="0..1" type="Shape" polymorphic="true">
<comment>
Optional specification of the location to compute assistance data. If not specified
all available asistance data will be provided.
......@@ -91,16 +92,9 @@
</struct>
<!-- GnssDataOutput structure -->
<struct name="GnssDataOutput" type="IlpOutputBase">
<struct name="GnssDataOutput" type="OutputBase">
<comment>ILP.Assistance.GnssData output structure. </comment>
<elem name="resultcode" multiplicity="1" type="ResultCode">
<comment>
Result of GnssData operation.
If resultcode is not success, encCon and constellation data will not be present.
</comment>
</elem>
<elem name="encoding" multiplicity="0..1" type="EncodingFormat" default="0">
<comment>
Constellation Data encoding format. Data can be provided in a different encoding format
......
ILP/V1.2/IlpPositioningApi.xid.xml
......@@ -12,7 +12,8 @@
via standard IP based protocols. The API currently supports XMF and JSON wire formats.
</comment>
<import ref="https://xid.location.studio/ILP/V1.2/IlpApiBase.xid.xml" local="IlpApiBase.xid.xml" />
<import ref="https://xid.location.studio/Tensor/V1.0.0/ApiBase.xid.xml" local="ApiBase.xid.xml" />
<import ref="https://xid.location.studio/HPE/V1.2/HpeCore.xid.xml" local="HpeCore.xid.xml" />
<namespace name="ILP">
<using namespace="HPE"/>
......@@ -25,7 +26,7 @@
-->
<!-- CalculateInput structure -->
<struct name="CalculateInput" type ="IlpInputBase">
<struct name="CalculateInput" type ="InputBase">
<comment>ILP.Positioning.Calculate input data structure.</comment>
<elem name="uuidSession" multiplicity="0..1" type="UUID">
......@@ -88,13 +89,6 @@ If not specified, the set defaults to: Spheroid, Circle.
</comment>
</elem>
<elem name="directive" multiplicity="0..*" type="NameValue" ord="87">
<comment>
A set of directives to influence processing. Unknown directives are ignored.
</comment>
</elem>
<elem name="state" multiplicity="0..1" type="StateInfo" ord="90">
<comment>
Specifies the position to initialize the state of the positioning engine.\n
......@@ -134,7 +128,7 @@ If not specified, the set defaults to: Spheroid, Circle.
</enum>
<!-- CalculateOutput structure -->
<struct name="CalculateOutput" type="IlpOutputBase" >
<struct name="CalculateOutput" type="OutputBase" >
<comment>ILP.Positioning.Calculate output data structure. This contains the reuslts of a calculate oeration.</comment>
<elem name="uuidSession" multiplicity="1" type="UUID">
......@@ -173,131 +167,6 @@ If not specified, the set defaults to: Spheroid, Circle.
<!--
*******************************************************
CreateSession Data Types
*******************************************************
-->
<!-- CreateSessionInput structure -->
<struct name="CreateSessionInput" type="IlpInputBase">
<comment>ILP.Positioning.CreateSession input data structure.</comment>
<elem name="dynamics" multiplicity="1" type="DynamicsProfile">
<comment>
Specifies the dymnamics of the device providing the data. If not known specify undefined.
This parameter optimizes configuration of the estimator to constraint calculations based on the type
of motion. If session is specified, this value will be overridden.
</comment>
</elem>
<elem name="duration" multiplicity="1" type="int32">
<comment>
Number of seconds duration should persist. Maximum value is 86400 (1 day).
</comment>
</elem>
<elem name="typeObs" multiplicity="0..*" type="ObservationType">
<comment>
Optional List of supported observation types. Improves transaction initialization speed if only observation types needed are specified.
If not specified, all supported observations will be available for the session.
</comment>
</elem>
<elem name="ctTypicalObs" multiplicity="0..1" type="int32">
<comment>
Optional count of typical observations. Improves memory allocation when sizing internal buffers to typical number
of observations.
</comment>
</elem>
</struct>
<!-- CreateSessionOutput structure -->
<struct name="CreateSessionOutput" type="IlpOutputBase" >
<comment>ILP.Positioning.CreateSession output data structure.</comment>
<elem name="resultcode" multiplicity="1" type="ResultCode">
<comment>
Result of session creation operation.
</comment>
</elem>
<elem name="uuidSession" multiplicity="0..1" type="UUID">
<comment>
Session identifier of the created session.
</comment>
</elem>
</struct>
<!--
*******************************************************
ReleaseSession Data Types
*******************************************************
-->
<!-- ReleaseSessionInput structure -->
<struct name="ReleaseSessionInput" >
<comment>ILP.Positioning.ReleaseSession input data structure.</comment>
<elem name="uuidSession" multiplicity="1" type="UUID">
<comment>
Session identifier of the session to release.
</comment>
</elem>
</struct>
<!--
*******************************************************
Initialize Data Types
*******************************************************
-->
<!-- InitializeInput structure -->
<struct name="InitializeInput" type="IlpInputBase" >
<comment>ILP.Positioning.Initialize input data structure.</comment>
<elem name="uuidSession" multiplicity="0..1" type="UUID">
<comment>
Optional session identifier. See CreateSession for creating valid
session identifiers. Transactions can be processed in the context of a session to provide
historical information and link calcuation in time.
</comment>
</elem>
<elem name="durSession" multiplicity="0..1" type="int32">
<comment>
Optional session duration. Default is 0 (not persisted). If specified,
the session created for this transaction will be stored for a maximum of 86400 seconds.
The uuidSession returned in the output, can be used in subsequent calls to Calculate to utilize
the persisted session data. Call ReleaseSession to release any persisted content once the session
is complete.
</comment>
</elem>
<elem name="state" multiplicity="1" type="StateInfo">
<comment>
Specifies the position to initialize the state of the positioning engine.
</comment>
</elem>
</struct>
<!-- InitializeOutput structure -->
<struct name="InitializeOutput" type="IlpOutputBase">
<comment>ILP.Positioning.Initialize output data structure.</comment>
<elem name="resultcode" multiplicity="1" type="ResultCode">
<comment>
Result of session creation operation.
</comment>
</elem>
<elem name="uuidSession" multiplicity="0..1" type="UUID">
<comment>
Session identifier of the created session.
</comment>
</elem>
</struct>
<!--
*******************************************************
ILP Positioning Service Interface.
*******************************************************
-->
......@@ -308,36 +177,7 @@ If not specified, the set defaults to: Spheroid, Circle.
<comment>Calculates the position of the device given the specified observation data.</comment>
<input name="Input" type="CalculateInput" sid="0x1010"/>
<output name="Result" type="CalculateOutput" sid="0x1011" />
</operation>
<operation name="CreateSession">
<comment>
Creates a persistent session object and returns its UUID. Can be used to process a series of related transactions
using the previous filter state. Good for temporal or multiple observation type updates that were not
available at the same time.
</comment>
<input name="Input" type="CreateSessionInput" sid="0x1012"/>
<output name="Result" type="CreateSessionOutput" sid="0x1013"/>
</operation>
<operation name="ReleaseSession">
<comment>
Releases any persistent session data associated with the UUID.
</comment>
<input name="Input" type="ReleaseSessionInput" sid="0x1014"/>
<!-- output name="Result" type="void" sid="0x0000" result="return"/ -->
</operation>
<operation name="Initialize">
<comment>
Initializes the positioning engine to state specified in the provided shape information.
This is an optional interaction given most cases, this initial position can be determmined from
the provided data.
</comment>
<input name="Input" type="InitializeInput" sid="0x1016"/>
<output name="Result" type="InitializeOutput" sid="0x1017" />
</operation>
</interface>
</namespace>
......
ILP/V1.2/IlpSubmissionApi.xid.xml
......@@ -11,7 +11,7 @@
data without invoking the full get position operation.
</comment>
<import ref="https://xid.location.studio/ILP/V1.2/IlpApiBase.xid.xml" local="IlpApiBase.xid.xml" />
<import ref="https://xid.location.studio/Tensor/V1.0.0/ApiBase.xid.xml" local="ApiBase.xid.xml" />
<namespace name="ILP">
<using namespace="HPE"/>
......@@ -22,7 +22,7 @@
Note: all the tags are defined. These have to
match CalculateInput tags of the same name.
-->
<struct name="PositionInfo" type="IlpInputBase" >
<struct name="PositionInfo" type="InputBase" >
<comment>Used as ILP.Submission.PositionInfo input.</comment>
<elem name="state" multiplicity="0..1" type="StateInfo" ord="90">
......@@ -33,12 +33,6 @@
</comment>
</elem>
<elem name="directive" multiplicity="0..*" type="NameValue" ord="87">
<comment>
A set of directives to influence processing.
</comment>
</elem>
<elem name="encObs" multiplicity="0..1" type="EncodingFormat" default="0" ord="88">
<comment>
Observation set encoding format. Observations may be passed to the service in
......
ILP/V1.2/README.md 0 → 100644
# ILP XIDs #
ILP XIDs do not encode their ordinals (i.e. tags and offets). XIDData.prop is required to maintain backward compatibility.
## Generate / Verify XIDData.prop ##
~~~sh
$ java -Xnoclassgc -jar $XIDSDK/bin/xidcg.jar \
-v \
-prop https://xid.location.studio/Tensor/V1.0.0/XIDData.prop \
-prop https://xid.location.studio/HPE/V1.2/XIDData.prop \
-prop https://xid.location.studio/ILP/V1.2/XIDData.prop \
https://xid.location.studio/ILP/V1.2/IlpAssistanceApi.xid.xml \
https://xid.location.studio/ILP/V1.2/IlpPositioningApi.xid.xml \
https://xid.location.studio/ILP/V1.2/IlpSubmissionApi.xid.xml
OR
$ java -Xnoclassgc -jar $XIDSDK/bin/xidcg.jar \
-v \
-prop ../../Tensor/V1.0.0/XIDData.prop \
-prop ../../HPE/V1.2/XIDData.prop \
-prop XIDData.prop \
IlpAssistanceApi.xid.xml \
IlpPositioningApi.xid.xml \
IlpSubmissionApi.xid.xml
~~~
If xidcg reports:
~~~
Generating: xidout/meta/XID/XIDData.prop
~~~
Then something has changed and XIDData.prop needs to get updated.
ILP/V1.2/XIDData.prop
......@@ -401,7 +401,6 @@ Ord.HPE.TaskReport.start=113
Ord.HPE.TaskReport.status=115
Ord.HPE.TaskReport.taskid=112
Ord.ILP.CalculateInput.confidence=84
Ord.ILP.CalculateInput.directive=87
Ord.ILP.CalculateInput.durSession=81
Ord.ILP.CalculateInput.dynamics=82
Ord.ILP.CalculateInput.encObs=88
......@@ -416,12 +415,6 @@ Ord.ILP.CalculateOutput.dynamics=81
Ord.ILP.CalculateOutput.rankEstimate=82
Ord.ILP.CalculateOutput.status=83
Ord.ILP.CalculateOutput.uuidSession=80
Ord.ILP.CreateSessionInput.ctTypicalObs=83
Ord.ILP.CreateSessionInput.duration=81
Ord.ILP.CreateSessionInput.dynamics=80
Ord.ILP.CreateSessionInput.typeObs=82
Ord.ILP.CreateSessionOutput.resultcode=80
Ord.ILP.CreateSessionOutput.uuidSession=81
Ord.ILP.GnssDataInput.Request=84
Ord.ILP.GnssDataInput.RequestSpec.AssistData=68
Ord.ILP.GnssDataInput.RequestSpec.constellation=64
......@@ -432,23 +425,11 @@ Ord.ILP.GnssDataInput.elmask=83
Ord.ILP.GnssDataInput.encoding=81
Ord.ILP.GnssDataInput.epoch=80
Ord.ILP.GnssDataInput.location=82
Ord.ILP.GnssDataOutput.assistdata=82
Ord.ILP.GnssDataOutput.encoding=81
Ord.ILP.GnssDataOutput.resultcode=80
Ord.ILP.IlpInputBase.idDevice=64
Ord.ILP.IlpInputBase.idTransaction=65
Ord.ILP.IlpOutputBase.idDevice=64
Ord.ILP.IlpOutputBase.idTransaction=65
Ord.ILP.InitializeInput.durSession=81
Ord.ILP.InitializeInput.state=82
Ord.ILP.InitializeInput.uuidSession=80
Ord.ILP.InitializeOutput.resultcode=80
Ord.ILP.InitializeOutput.uuidSession=81
Ord.ILP.PositionInfo.directive=87
Ord.ILP.GnssDataOutput.assistdata=81
Ord.ILP.GnssDataOutput.encoding=80
Ord.ILP.PositionInfo.encObs=88
Ord.ILP.PositionInfo.observations=89
Ord.ILP.PositionInfo.state=90
Ord.ILP.ReleaseSessionInput.uuidSession=64
Ord.Logging.ActionMsg.category=98
Ord.Logging.ActionMsg.id=96
Ord.Logging.ActionMsg.iid=99
......@@ -486,19 +467,35 @@ Ord.Logging.TransactionMsg.devid=83
Ord.Logging.TransactionMsg.etid=81
Ord.Logging.TransactionMsg.tid=80
Ord.Logging.UsageMsg.uri=96
Ord.Tensor.Command.argument=66
Ord.Tensor.Command.etid=65
Ord.Tensor.Command.name=64
Ord.Tensor.CommandApi.Execute.Input.commands=64
Ord.Tensor.CommandApi.Execute.Input.wantresponses=65
Ord.Tensor.CommandApi.Execute.Output.lastcommand=64
Ord.Tensor.CommandApi.Execute.Output.lastresult=65
Ord.Tensor.CommandApi.Execute.Output.responses=66
Ord.Tensor.CommandResponse.etid=65
Ord.Tensor.CommandResponse.name=64
Ord.Tensor.CommandResponse.output=67
Ord.Tensor.CommandResponse.result=66
Ord.Tensor.InputBase.devid=64
Ord.Tensor.InputBase.directive=66
Ord.Tensor.InputBase.etid=65
Ord.Tensor.NameValue.name=64
Ord.Tensor.NameValue.value=65
Ord.Tensor.OutputBase.devid=64
Ord.Tensor.OutputBase.errinfo=67
Ord.Tensor.OutputBase.etid=65
Ord.Tensor.OutputBase.resultcode=66
Ord.Tensor.VoidType.reserved=64
SID.ILP.Assistance.Gnss.Input=4120
SID.ILP.Assistance.Gnss.Output=4121
SID.ILP.Positioning.Calculate.Input=4112
SID.ILP.Positioning.Calculate.Output=4113
SID.ILP.Positioning.CreateSession.Input=4114
SID.ILP.Positioning.CreateSession.Output=4115
SID.ILP.Positioning.Initialize.Input=4118
SID.ILP.Positioning.Initialize.Output=4119
SID.ILP.Positioning.ReleaseSession.Input=4116
SID.ILP.Submission.PositionInfo.Input=4126
SID.Tensor.CommandApi.Execute.Input=256
SID.Tensor.CommandApi.Execute.Output=257
Size.HPE.Arc3D=45
Size.HPE.Arc=33
Size.HPE.ArcBand3D=49
......@@ -556,24 +553,12 @@ Size.ILP.Assistance.Gnss.Input=-1
Size.ILP.Assistance.Gnss.Output=-1
Size.ILP.CalculateInput=-1
Size.ILP.CalculateOutput=-1
Size.ILP.CreateSessionInput=-1
Size.ILP.CreateSessionOutput=-1
Size.ILP.GnssDataInput.RequestSpec=-1
Size.ILP.GnssDataInput=-1
Size.ILP.GnssDataOutput=-1
Size.ILP.IlpInputBase=-1
Size.ILP.IlpOutputBase=-1
Size.ILP.InitializeInput=-1
Size.ILP.InitializeOutput=-1
Size.ILP.PositionInfo=-1
Size.ILP.Positioning.Calculate.Input=-1
Size.ILP.Positioning.Calculate.Output=-1
Size.ILP.Positioning.CreateSession.Input=-1
Size.ILP.Positioning.CreateSession.Output=-1
Size.ILP.Positioning.Initialize.Input=-1
Size.ILP.Positioning.Initialize.Output=-1
Size.ILP.Positioning.ReleaseSession.Input=-1
Size.ILP.ReleaseSessionInput=-1
Size.ILP.Submission.PositionInfo.Input=-1
Size.Logging.ActionMsg=-1
Size.Logging.AppMetrics=-1
......@@ -586,5 +571,11 @@ Size.Logging.TaskReport=-1
Size.Logging.TraceMsg=-1
Size.Logging.TransactionMsg=-1
Size.Logging.UsageMsg=-1
Size.Tensor.Command=-1
Size.Tensor.CommandApi.Execute.Input=-1
Size.Tensor.CommandApi.Execute.Output=-1
Size.Tensor.CommandResponse=-1
Size.Tensor.InputBase=-1
Size.Tensor.NameValue=-1
Size.Tensor.OutputBase=-1
Size.Tensor.VoidType=-1
......
Tensor/V1.0.0/README.md
......@@ -10,8 +10,19 @@ $ java -Xnoclassgc -jar $XIDSDK/bin/xidcg.jar \
https://xid.location.studio/Tensor/V1.0.0/ApiBase.xid.xml \
https://xid.location.studio/Tensor/V1.0.0/Command.xid.xml \
https://xid.location.studio/Tensor/V1.0.0/Common.xid.xml \
https://xid.location.studio/Tensor/V1.0.0/Definiions.xid.xml \
https://xid.location.studio/Tensor/V1.0.0/Definitions.xid.xml \
https://xid.location.studio/Tensor/V1.0.0/Logging.xid.xml
OR
$ java -Xnoclassgc -jar $XIDSDK/bin/xidcg.jar \
-v \
-prop XIDData.prop \
ApiBase.xid.xml \
Command.xid.xml \
Common.xid.xml \
Definitions.xid.xml \
Logging.xid.xml
~~~
If xidcg reports:
......
Tensor/V1.0.0/XIDData.prop
......@@ -47,8 +47,15 @@ Ord.Tensor.CommandResponse.etid=65
Ord.Tensor.CommandResponse.name=64
Ord.Tensor.CommandResponse.output=67
Ord.Tensor.CommandResponse.result=66
Ord.Tensor.InputBase.devid=64
Ord.Tensor.InputBase.directive=66
Ord.Tensor.InputBase.etid=65
Ord.Tensor.NameValue.name=64
Ord.Tensor.NameValue.value=65
Ord.Tensor.OutputBase.devid=64
Ord.Tensor.OutputBase.errinfo=67
Ord.Tensor.OutputBase.etid=65
Ord.Tensor.OutputBase.resultcode=66
Ord.Tensor.VoidType.reserved=64
SID.Tensor.CommandApi.Execute.Input=256
SID.Tensor.CommandApi.Execute.Output=257
......@@ -67,5 +74,7 @@ Size.Tensor.Command=-1
Size.Tensor.CommandApi.Execute.Input=-1
Size.Tensor.CommandApi.Execute.Output=-1
Size.Tensor.CommandResponse=-1
Size.Tensor.InputBase=-1
Size.Tensor.NameValue=-1
Size.Tensor.OutputBase=-1
Size.Tensor.VoidType=-1
......
Styling with Markdown is supported
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!