Skip to content
Toggle navigation
Toggle navigation
This project
Loading...
Sign in
xid
/
specs
Go to a project
Toggle navigation
Toggle navigation pinning
Projects
Groups
Snippets
Help
Project
Activity
Repository
Graphs
Issues
0
Merge Requests
0
Wiki
Snippets
Network
Create a new issue
Commits
Issue Boards
Files
Commits
Network
Compare
Branches
Tags
4642bea9
authored
2018-04-09 22:17:03 -0700
by
Skip Hines
Browse Files
Options
Browse Files
Tag
Download
Email Patches
Plain Diff
ILP-551 : changed Java package and moved Encoding formats from Definitions to Common
1 parent
dbec40ca
Expand all
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
57 additions
and
0 deletions
Tensor/V1.1/Common.xid.xml
Tensor/V1.1/Definitions.xid.xml
Tensor/V1.1/Common.xid.xml
View file @
4642bea
...
...
@@ -71,6 +71,63 @@
<literal
name =
"target"
value =
"1"
/>
<literal
name =
"initiator"
value =
"2"
/>
</enum>
<!-- Encoding format type spec.-->
<type
name=
"EncodingFormat"
size=
"2"
>
<comment>
The encoding format determines how element data is run-time encoded within a particular element independent of the
transport encoding.
These values are specified in the "encoding" attribute for elements. Not all encoding formats
are supported by every wireline protocol implementation. Additionally, custom encodings may be
defined to support application defined encodings. Any non-standard encodings must be registered (to avoid collision)
and approved by the appropriate approving authority (e.g. Comtech). Values from 0 to 255 are reserved
for standard-encodings. Custom encodings start at 256(0x0100) and extend to 65535 (0xFFFF).\n
\n
This is not the same as defining in XID a raw datatype or json datatype which are NOT changeable are run-time.
\n
Example: \n
\t The message XMF but a field is defined to be encoded as JSON.\n
\t Likewise, the message is JSON, but a field is run-time encoded to be XMF.\n
\n
Data encoding format type. If 0, value is not encoded. See ResrvedEncodingFormats
for a list of standard format specifiers.
</comment>
<lang
name=
"c"
type=
"uint16_t"
include=
"stdint.h"
/>
<lang
name=
"cpp"
type=
"uint16_t"
include=
"cstdint"
/>
<lang
name=
"java"
type=
"XidShort"
include=
"com.comtechtel.tensor.xid.XidShort"
/>
<lang
name=
"node"
type=
"XidUShort"
/>
</type>
<!-- ReservedEncodingFormats standard encoding formats.-->
<enum
name=
"ReservedEncodingFormats"
type=
"Tensor.uint16"
default=
"natural"
>
<comment>
Reserved encoding formats define standard additional encodings known to all implementations.
</comment>
<literal
name=
"natural"
value=
"0"
>
<comment>
Data is not further encoded, it is in its natural wireline format.\n
This is the default value if not defined explicitly.
</comment>
</literal>
<literal
name=
"raw"
value=
"1"
>
<comment>
Data is in an unspecified binary format. The interpretation of the data is
falls to the producer and consumer of the information.
For textual wireline encodings like JSON, the data will be valid within the representation.
</comment>
</literal>
<literal
name=
"xmf"
value=
"2"
>
<comment>
Data is XMF binary format. The binary data is structured using atoms and atom lists.
For textual wireline encodings like JSON, this is XMF base64 encoded.
</comment>
</literal>
<literal
name=
"json"
value=
"3"
>
<comment>
Data is formatted as JSON compliant ascii text. For binary encodings like XMF, the content will be JSON instead.
</comment>
</literal>
</enum>
</namespace>
</specification>
...
...
Tensor/V1.1/Definitions.xid.xml
View file @
4642bea
This diff is collapsed.
Click to expand it.
Write
Preview
Styling with
Markdown
is supported
Attach a file
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to post a comment