RFC 7622
E233820
RFC 7622 is an IETF standard that defines the addressing and formatting rules for XMPP (Extensible Messaging and Presence Protocol) identifiers, known as JIDs.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 7622 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T2114331 — 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 7622 Context triple: [XMPP, hasCoreSpecification, RFC 7622]
-
A.
RFC 4627
RFC 4627 is the original IETF specification that formally defined the JSON (JavaScript Object Notation) data interchange format.
-
B.
RFC 7720
RFC 7720 is an IETF standards document that specifies the technical and operational requirements for the DNS Root Server System.
-
C.
RFC 8259
RFC 8259 is the IETF specification that formally defines the JSON (JavaScript Object Notation) data interchange format, including its syntax and semantics.
-
D.
RFC 7541
RFC 7541 is the IETF specification that defines the HPACK header compression format used by HTTP/2 to efficiently encode HTTP header fields.
-
E.
RFC 7950
RFC 7950 is the IETF specification that standardizes the YANG 1.1 data modeling language used for modeling configuration and state data in network management protocols.
- 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 7622 Target entity description: RFC 7622 is an IETF standard that defines the addressing and formatting rules for XMPP (Extensible Messaging and Presence Protocol) identifiers, known as JIDs.
-
A.
RFC 4627
RFC 4627 is the original IETF specification that formally defined the JSON (JavaScript Object Notation) data interchange format.
-
B.
RFC 7720
RFC 7720 is an IETF standards document that specifies the technical and operational requirements for the DNS Root Server System.
-
C.
RFC 8259
RFC 8259 is the IETF specification that formally defines the JSON (JavaScript Object Notation) data interchange format, including its syntax and semantics.
-
D.
RFC 7541
RFC 7541 is the IETF specification that defines the HPACK header compression format used by HTTP/2 to efficiently encode HTTP header fields.
-
E.
RFC 7950
RFC 7950 is the IETF specification that standardizes the YANG 1.1 data modeling language used for modeling configuration and state data in network management protocols.
- F. None of above. chosen
Statements (39)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
technical standard ⓘ |
| appliesTo |
XMPP
ⓘ
surface form:
Extensible Messaging and Presence Protocol
XMPP ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| defines |
JID comparison rules
ⓘ
JID normalization rules ⓘ JID preparation rules ⓘ JID syntax ⓘ Jabber Identifier format ⓘ XMPP address format ⓘ rules for XMPP domainpart ⓘ rules for XMPP localpart ⓘ rules for XMPP resourcepart ⓘ |
| definesTerm |
JID
ⓘ
domainpart ⓘ localpart ⓘ resourcepart ⓘ |
| documentType | Standards Track RFC ⓘ |
| focusesOn | addressing in XMPP ⓘ |
| language | English ⓘ |
| obsoletes | RFC 6122 ⓘ |
| partOf |
IETF XMPP Working Group
ⓘ
surface form:
XMPP core specifications
|
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
RFC 6120
ⓘ
RFC 6121 ⓘ XMPP addressing ⓘ |
| specifies |
Unicode handling for XMPP addresses
ⓘ
addressing rules for XMPP JIDs ⓘ formatting rules for XMPP JIDs ⓘ stringprep and PRECIS usage for XMPP identifiers ⓘ |
| standardizes |
format of Jabber IDs
ⓘ
format of XMPP identifiers ⓘ |
| status | Internet Standard ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| title |
XMPP
ⓘ
surface form:
Extensible Messaging and Presence Protocol (XMPP): Address Format
|
| updatesProtocol |
XMPP
ⓘ
surface form:
Extensible Messaging and Presence Protocol
|
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 7622 Description of subject: RFC 7622 is an IETF standard that defines the addressing and formatting rules for XMPP (Extensible Messaging and Presence Protocol) identifiers, known as JIDs.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.