CBOR
E754598
CBOR (Concise Binary Object Representation) is a compact, schema-less binary data serialization format designed for efficient, small-footprint data interchange, especially in constrained environments like IoT.
All labels observed (2)
| Label | Occurrences |
|---|---|
| CBOR canonical | 1 |
| Concise Binary Object Representation | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T8756348 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CBOR Context triple: [MessagePack, similarTo, CBOR]
-
A.
ASN.1
ASN.1 (Abstract Syntax Notation One) is a standardized, platform-independent notation used to define and encode complex data structures in telecommunications and cryptographic protocols, including X.509 certificates.
-
B.
MessagePack
MessagePack is a compact, efficient binary serialization format designed to encode structured data for fast transmission and storage across different programming languages.
-
C.
BSON
BSON is a binary-encoded serialization format commonly used by MongoDB to store and transfer structured data efficiently while supporting additional data types beyond those in JSON.
-
D.
HPACK
HPACK is the dedicated header compression format used by HTTP/2 to efficiently encode and transmit HTTP header fields while maintaining security and performance.
-
E.
JSON
JSON (JavaScript Object Notation) is a lightweight, text-based data interchange format widely used for transmitting structured data in web APIs and configuration files.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: CBOR Target entity description: CBOR (Concise Binary Object Representation) is a compact, schema-less binary data serialization format designed for efficient, small-footprint data interchange, especially in constrained environments like IoT.
-
A.
ASN.1
ASN.1 (Abstract Syntax Notation One) is a standardized, platform-independent notation used to define and encode complex data structures in telecommunications and cryptographic protocols, including X.509 certificates.
-
B.
MessagePack
MessagePack is a compact, efficient binary serialization format designed to encode structured data for fast transmission and storage across different programming languages.
-
C.
BSON
BSON is a binary-encoded serialization format commonly used by MongoDB to store and transfer structured data efficiently while supporting additional data types beyond those in JSON.
-
D.
HPACK
HPACK is the dedicated header compression format used by HTTP/2 to efficiently encode and transmit HTTP header fields while maintaining security and performance.
-
E.
JSON
JSON (JavaScript Object Notation) is a lightweight, text-based data interchange format widely used for transmitting structured data in web APIs and configuration files.
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
binary data serialization format
ⓘ
data interchange format ⓘ |
| abbreviation | CBOR ⓘ |
| category |
IETF standard
ⓘ
linked to:
IETF Internet standards process
|
| comparedTo | JSON ⓘ |
| definedIn | RFC 7049 ⓘ |
| designedFor |
Internet of Things
ⓘ
compact data representation ⓘ constrained environments ⓘ efficient data interchange ⓘ schema-less data serialization ⓘ small-footprint implementations ⓘ |
| encodingType | binary ⓘ |
| fullName |
Concise Binary Object Representation
ⓘ
linked to:
CBOR
|
| goal |
efficient parsing
ⓘ
low code size implementations ⓘ low message overhead ⓘ |
| isBinaryAlternativeTo | JSON ⓘ |
| property |
compact binary encoding
ⓘ
deterministic encoding possible ⓘ extensible via tags ⓘ human-readable diagnostic notation ⓘ schema-less ⓘ self-describing ⓘ |
| standardizedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| supports |
Unicode strings
ⓘ
arrays ⓘ binary data ⓘ boolean values ⓘ byte strings ⓘ canonical encoding rules ⓘ floating-point numbers ⓘ indefinite-length items ⓘ integers ⓘ maps ⓘ null value ⓘ simple values ⓘ tags ⓘ text data ⓘ |
| updatedBy | RFC 8949 ⓘ |
| useCase |
IoT device communication
ⓘ
constrained network protocols ⓘ embedded systems ⓘ machine-to-machine communication ⓘ web protocols ⓘ |
| usedIn |
CoAP
ⓘ
OSCORE ⓘ SUIT manifests ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: CBOR Description of subject: CBOR (Concise Binary Object Representation) is a compact, schema-less binary data serialization format designed for efficient, small-footprint data interchange, especially in constrained environments like IoT.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.