XEP-0060: Publish-Subscribe
E845094
XEP-0060: Publish-Subscribe is an XMPP protocol extension that defines a flexible publish-subscribe messaging pattern for distributing and receiving event notifications in real time.
All labels observed (1)
| Label | Occurrences |
|---|---|
| XEP-0060: Publish-Subscribe canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T10158118 — 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.
Target entity: XEP-0060: Publish-Subscribe Context triple: [XMPP Extension Protocols, hasComponent, XEP-0060: Publish-Subscribe]
-
A.
XMPP Extension Protocols
XMPP Extension Protocols are a collection of standardized specifications (XEPs) that extend the core XMPP protocol with additional features such as messaging enhancements, presence extensions, and application-specific functionality.
-
B.
Publish–Subscribe pattern
The Publish–Subscribe pattern is a messaging design pattern in which senders (publishers) broadcast messages without knowledge of specific receivers, and subscribers receive only the messages they have expressed interest in.
-
C.
XMPP
XMPP (Extensible Messaging and Presence Protocol) is an open, XML-based communication protocol primarily used for instant messaging, presence information, and real-time data exchange over the internet.
-
D.
XEP
XEP is the standard abbreviation for XMPP Extension Protocols, which define modular enhancements and additional features for the XMPP messaging protocol.
-
E.
XMPP Standards Foundation
The XMPP Standards Foundation is a non-profit organization that develops and maintains open standards for the Extensible Messaging and Presence Protocol (XMPP), enabling interoperable real-time communication across the internet.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: XEP-0060: Publish-Subscribe Target entity description: XEP-0060: Publish-Subscribe is an XMPP protocol extension that defines a flexible publish-subscribe messaging pattern for distributing and receiving event notifications in real time.
-
A.
XMPP Extension Protocols
XMPP Extension Protocols are a collection of standardized specifications (XEPs) that extend the core XMPP protocol with additional features such as messaging enhancements, presence extensions, and application-specific functionality.
-
B.
Publish–Subscribe pattern
The Publish–Subscribe pattern is a messaging design pattern in which senders (publishers) broadcast messages without knowledge of specific receivers, and subscribers receive only the messages they have expressed interest in.
-
C.
XMPP
XMPP (Extensible Messaging and Presence Protocol) is an open, XML-based communication protocol primarily used for instant messaging, presence information, and real-time data exchange over the internet.
-
D.
XEP
XEP is the standard abbreviation for XMPP Extension Protocols, which define modular enhancements and additional features for the XMPP messaging protocol.
-
E.
XMPP Standards Foundation
The XMPP Standards Foundation is a non-profit organization that develops and maintains open standards for the Extensible Messaging and Presence Protocol (XMPP), enabling interoperable real-time communication across the internet.
- F. None of above. chosen
Statements (77)
| Predicate | Object |
|---|---|
| instanceOf |
XMPP Extension Protocol Specification
ⓘ
XMPP Publish-Subscribe Protocol ⓘ |
| alsoKnownAs | XEP-0060 PubSub NERFINISHED ⓘ |
| basedOn | Extensible Messaging and Presence Protocol NERFINISHED ⓘ |
| category |
event notification protocol
ⓘ
real-time communication protocol ⓘ |
| definesAccessModel |
authorize
ⓘ
open ⓘ presence ⓘ roster ⓘ whitelist ⓘ |
| definesConcept |
access model
ⓘ
affiliation ⓘ item ⓘ node configuration ⓘ notification ⓘ notification payload ⓘ persistent items ⓘ publish model ⓘ publisher ⓘ pubsub node ⓘ pubsub service ⓘ subscriber ⓘ subscription ⓘ |
| definesOperation |
configure node
ⓘ
create node ⓘ delete node ⓘ manage affiliations ⓘ manage subscriptions ⓘ publish item ⓘ request items ⓘ retract item ⓘ subscribe ⓘ unsubscribe ⓘ |
| definesPattern | publish-subscribe messaging pattern ⓘ |
| definesPublishModel |
open
ⓘ
publishers ⓘ subscribers ⓘ |
| definesRole |
outcast
ⓘ
owner ⓘ publisher ⓘ subscriber ⓘ |
| fullName | XEP-0060: Publish-Subscribe NERFINISHED ⓘ |
| governingBody | XMPP Standards Foundation NERFINISHED ⓘ |
| notificationChannel | message stanzas ⓘ |
| primaryInteractionPattern | request-response via IQ GENERATED ⓘ |
| protocolFamily | XMPP NERFINISHED ⓘ |
| relatedSpecification |
XEP-0030: Service Discovery
NERFINISHED
ⓘ
XEP-0163: Personal Eventing Protocol NERFINISHED ⓘ XEP-0248: PubSub Collection Nodes NERFINISHED ⓘ |
| shortName | XEP-0060 NERFINISHED ⓘ |
| supports |
asynchronous message distribution
ⓘ
loosely coupled communication ⓘ many-to-many messaging ⓘ real-time event notifications ⓘ |
| supportsFeature |
access control
ⓘ
event payload delivery ⓘ event-only nodes ⓘ instant nodes ⓘ item expiration ⓘ node collections ⓘ notification filtering ⓘ payload-less notifications ⓘ persistent nodes ⓘ publisher authorization ⓘ service discovery integration ⓘ subscription expiration ⓘ subscription options ⓘ |
| transport | XMPP stanzas ⓘ |
| useCase |
IoT data distribution
ⓘ
multi-user event systems ⓘ news feeds ⓘ presence and status updates ⓘ real-time event distribution ⓘ |
| usesNamespace | http://jabber.org/protocol/pubsub ⓘ |
| usesStanzaType |
IQ
ⓘ
message ⓘ |
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.
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.
Subject: XEP-0060: Publish-Subscribe Description of subject: XEP-0060: Publish-Subscribe is an XMPP protocol extension that defines a flexible publish-subscribe messaging pattern for distributing and receiving event notifications in real time.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.