Comparison of data-serialization formats: Difference between revisions

Revision as of 14:30, 15 January 2023

Revision as of 07:15, 18 January 2023

Line 335:

| [https://developers.google.com/protocol-buffers/docs/encoding Developer Guide: Encoding]

| {{yes}}

| {{partialyes}}{{ref|pbtextformat|d}}

| {{no}}

| {{yes|Built-in}}

Line 478:

| {{note|pltxt}}The "classic" format is plain text, and an XML format is also supported.

| {{note|thrifttxt}}Theoretically possible due to abstraction, but no implementation is included.

| {{note|pbtextformat}}The primary format is binary, but a text formatand JSON formats isare available.<ref>{{cite web|url=https://developers.google.com/protocol-buffers/docs/reference/cpp/google.protobuf.text_format|title=text_format.h - Protocol Buffers|website=Google Developers}}</ref><ref>{{cite web|url=https://developers.google.com/protocol-buffers/docs/proto3#json|title=JSON Mapping - Protocol Buffers|website=Google Developers}}</ref>

| {{note|stdrefs}}Means that generic tools/libraries know how to encode, decode, and dereference a reference to another piece of data in the same document. A tool may require the [[Interface description language|IDL]] file, but no more. Excludes custom, non-standardized referencing techniques.

| {{note|asn1refs}}ASN.1 has X.681 (Information Object System), X.682 (Constraints), and X.683 (Parameterization) that allow for the precise specification of open types where the types of values can be identified by integers, by [[Object identifier|OIDs]], etc. OIDs are a standard format for globally unique identifiers, as well as a standard notation ("absolute reference") for referencing a component of a value. For example, PKIX uses such notation in RFC 5912. With such notation (constraints on parameterized types using information object sets), generic ASN.1 tools/libraries can automatically encode/decode/resolve references within a document.