RFC 3629
E138249
RFC 3629 is the Internet standard that defines the UTF-8 character encoding for representing Unicode/ISO/IEC 10646 characters in a byte-oriented format.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 3629 canonical | 5 |
How this entity was disambiguated
This entity first appeared as the object of triple T1209444 — 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: RFC 3629 Context triple: [ISO/IEC 10646, relatedStandard, RFC 3629]
-
A.
RFC 3710
RFC 3710 is an IETF document that defines the purpose, structure, and procedures of the Internet Engineering Steering Group (IESG) within the Internet standards process.
-
B.
RFC 3546
RFC 3546 is an Internet Engineering Task Force (IETF) specification that originally defined the use of extensions within the Transport Layer Security (TLS) protocol.
-
C.
RFC 3720
RFC 3720 is the Internet Engineering Task Force (IETF) standard that specifies the Internet Small Computer Systems Interface (iSCSI) protocol for transporting SCSI commands over IP networks.
-
D.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
-
E.
RFC 3411
RFC 3411 is an IETF standard that specifies the architecture for the Simple Network Management Protocol (SNMP) framework used for managing devices on IP networks.
- 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: RFC 3629 Target entity description: RFC 3629 is the Internet standard that defines the UTF-8 character encoding for representing Unicode/ISO/IEC 10646 characters in a byte-oriented format.
-
A.
RFC 3710
RFC 3710 is an IETF document that defines the purpose, structure, and procedures of the Internet Engineering Steering Group (IESG) within the Internet standards process.
-
B.
RFC 3546
RFC 3546 is an Internet Engineering Task Force (IETF) specification that originally defined the use of extensions within the Transport Layer Security (TLS) protocol.
-
C.
RFC 3720
RFC 3720 is the Internet Engineering Task Force (IETF) standard that specifies the Internet Small Computer Systems Interface (iSCSI) protocol for transporting SCSI commands over IP networks.
-
D.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
-
E.
RFC 3411
RFC 3411 is an IETF standard that specifies the architecture for the Simple Network Management Protocol (SNMP) framework used for managing devices on IP networks.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| addresses |
invalid byte sequences in UTF-8
ⓘ
overlong UTF-8 sequences ⓘ security considerations for UTF-8 ⓘ |
| appliesTo |
Internet protocols
ⓘ
textual data interchange ⓘ |
| area | Applications Area ⓘ |
| category | Character encoding standard ⓘ |
| defines |
UTF-8
ⓘ
UTF-8 character encoding ⓘ encoding of Unicode characters in 8-bit octets ⓘ transformation format of ISO/IEC 10646 ⓘ |
| definesCodeUnitSequenceLength | 1 to 4 octets ⓘ |
| definesEncodingUnit |
8-bit byte
ⓘ
octet ⓘ |
| definesMaximumCodePoint | U+10FFFF ⓘ |
| definesProperty |
backward compatibility with ASCII
ⓘ
self-synchronizing property of UTF-8 ⓘ |
| documentType | Standards Track RFC ⓘ |
| encodingType |
byte-oriented encoding
ⓘ
variable-length encoding ⓘ |
| ensures | ASCII characters have same byte values in UTF-8 ⓘ |
| hasAbbreviation | RFC 3629 ⓘ |
| language | English ⓘ |
| obsoletes | RFC 2279 ⓘ |
| organization | Internet Society ⓘ |
| prohibits | encoding of UTF-16 surrogates in UTF-8 ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedStandard |
ISO/IEC 10646
ⓘ
Unicode Standard ⓘ |
| relatesTo |
ISO/IEC 10646
ⓘ
Unicode ⓘ |
| restricts | UTF-8 code sequences to 4 bytes ⓘ |
| RFCNumber | 3629 ⓘ |
| specifies |
encoding of Unicode scalar values
ⓘ
ill-formed UTF-8 byte sequences ⓘ rules for surrogate code points in UTF-8 ⓘ well-formed UTF-8 byte sequences ⓘ |
| standardizes | UTF-8 ⓘ |
| status |
Internet Standard
ⓘ
Standards Track RFC ⓘ |
| stream | IETF Stream ⓘ |
| title | UTF-8, a transformation format of ISO 10646 ⓘ |
| topic |
character encoding
ⓘ
internationalization ⓘ text representation in computers ⓘ |
| updates | UTF-8 specification ⓘ |
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: RFC 3629 Description of subject: RFC 3629 is the Internet standard that defines the UTF-8 character encoding for representing Unicode/ISO/IEC 10646 characters in a byte-oriented format.
Referenced by (5)
Full triples — surface form annotated when it differs from this entity's canonical label.