RFC 2279
E595261
RFC 2279 is an older Internet standard that originally defined UTF-8 as a transformation format for Unicode, later superseded by RFC 3629.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2279 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T6442136 — 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 2279 Context triple: [RFC 3629, obsoletes, RFC 2279]
-
A.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
-
B.
RFC 2449
RFC 2449 is an Internet standards document that extends the POP3 email protocol with additional capabilities and commands to improve flexibility and interoperability.
-
C.
RFC 2572
RFC 2572 is an earlier IETF specification that defined the Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) before being superseded by RFC 3412.
-
D.
RFC 2487
RFC 2487 is an Internet standards document that originally defined the STARTTLS extension for securing SMTP connections with TLS, later superseded by RFC 3207.
-
E.
RFC 1939
RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
- 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 2279 Target entity description: RFC 2279 is an older Internet standard that originally defined UTF-8 as a transformation format for Unicode, later superseded by RFC 3629.
-
A.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
-
B.
RFC 2449
RFC 2449 is an Internet standards document that extends the POP3 email protocol with additional capabilities and commands to improve flexibility and interoperability.
-
C.
RFC 2572
RFC 2572 is an earlier IETF specification that defined the Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) before being superseded by RFC 3412.
-
D.
RFC 2487
RFC 2487 is an Internet standards document that originally defined the STARTTLS extension for securing SMTP connections with TLS, later superseded by RFC 3207.
-
E.
RFC 1939
RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
- F. None of above. chosen
Statements (28)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| defines |
UTF-8
ⓘ
UTF-8 as a transformation format of ISO/IEC 10646 ⓘ UTF-8 as a variable-length character encoding ⓘ |
| definesProperty |
UTF-8 is compatible with ASCII for 7-bit characters
ⓘ
UTF-8 uses sequences of 1 to 6 bytes per code point ⓘ |
| hasNumber | 2279 ⓘ |
| language | English ⓘ |
| obsoletedBy | RFC 3629 ⓘ |
| publicationMonth | January ⓘ |
| publicationYear | 1998 ⓘ |
| publishedBy | Internet Engineering Task Force ⓘ |
| publishedInSeries |
RFC series
ⓘ
linked to:
RFCs
|
| relation | superseded by later UTF-8 definition in RFC 3629 ⓘ |
| standardizes |
encoding of ISO/IEC 10646 in UTF-8
ⓘ
encoding of Unicode in UTF-8 ⓘ |
| status | Obsoleted ⓘ |
| stream |
IETF Standards Track
ⓘ
linked to:
IETF Internet standards process
|
| subject |
ISO/IEC 10646
ⓘ
UTF-8 ⓘ Unicode ⓘ character encoding ⓘ |
| successorStandard | RFC 3629 ⓘ |
| title | UTF-8, a transformation format of ISO 10646 ⓘ |
| updates | RFC 2044 ⓘ |
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 2279 Description of subject: RFC 2279 is an older Internet standard that originally defined UTF-8 as a transformation format for Unicode, later superseded by RFC 3629.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.