HTTP Working Group
E49793
The HTTP Working Group is an IETF standards body responsible for developing and maintaining the Hypertext Transfer Protocol and related web communication specifications.
All labels observed (5)
| Label | Occurrences |
|---|---|
| HTTP Working Group canonical | 7 |
| IETF HTTP Working Group | 4 |
| IETF HTTPbis Working Group | 2 |
| HTTP WG | 1 |
| Hypertext Transfer Protocol (httpbis) | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T394773 — 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: HTTP Working Group Context triple: [RFC 9114, workingGroup, HTTP Working Group]
-
A.
Web Hypertext Application Technology Working Group
The Web Hypertext Application Technology Working Group (WHATWG) is a community of browser vendors, web developers, and other stakeholders that collaboratively develops and maintains key web standards, including the HTML Living Standard.
-
B.
W3C Coordination Group
The W3C Coordination Group is a World Wide Web Consortium body responsible for overseeing and harmonizing the work of various W3C groups to ensure technical consistency and effective collaboration across web standards.
-
C.
W3C Working Group
A W3C Working Group is a formal body within the World Wide Web Consortium that develops and maintains web standards and related technical reports through a consensus-driven process.
-
D.
W3C Interest Group
A W3C Interest Group is a community within the World Wide Web Consortium that brings together stakeholders to discuss and explore specific web-related topics without necessarily producing formal standards.
-
E.
W3C Technical Architecture Group
The W3C Technical Architecture Group is a specialized body within the World Wide Web Consortium that steers the evolution of web architecture and ensures the consistency and integrity of web standards.
- 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: HTTP Working Group Target entity description: The HTTP Working Group is an IETF standards body responsible for developing and maintaining the Hypertext Transfer Protocol and related web communication specifications.
-
A.
Web Hypertext Application Technology Working Group
The Web Hypertext Application Technology Working Group (WHATWG) is a community of browser vendors, web developers, and other stakeholders that collaboratively develops and maintains key web standards, including the HTML Living Standard.
-
B.
W3C Coordination Group
The W3C Coordination Group is a World Wide Web Consortium body responsible for overseeing and harmonizing the work of various W3C groups to ensure technical consistency and effective collaboration across web standards.
-
C.
W3C Working Group
A W3C Working Group is a formal body within the World Wide Web Consortium that develops and maintains web standards and related technical reports through a consensus-driven process.
-
D.
W3C Interest Group
A W3C Interest Group is a community within the World Wide Web Consortium that brings together stakeholders to discuss and explore specific web-related topics without necessarily producing formal standards.
-
E.
W3C Technical Architecture Group
The W3C Technical Architecture Group is a specialized body within the World Wide Web Consortium that steers the evolution of web architecture and ensures the consistency and integrity of web standards.
- F. None of above. chosen
Statements (51)
| Predicate | Object |
|---|---|
| instanceOf |
IETF working group
ⓘ
standards body ⓘ technical working group ⓘ |
| abbreviation |
HTTP WG
ⓘ
linked to:
HTTP Working Group
|
| field |
Internet protocols
ⓘ
computer networking ⓘ web technologies ⓘ |
| goal |
develop and maintain HTTP and related specifications
ⓘ
ensure interoperability of HTTP implementations ⓘ evolve HTTP to meet modern web requirements ⓘ |
| operatesUnder |
IETF Applications and Real-Time Area
ⓘ
linked to:
IETF Areas
|
| partOf | Internet Engineering Task Force ⓘ |
| publishes | RFCs ⓘ |
| responsibleFor |
HTTP Alternative Services specification
ⓘ
HTTP Strict Transport Security specification ⓘ HTTP authentication specifications ⓘ HTTP caching specifications ⓘ
linked to:
RFC 7234
HTTP content negotiation specifications ⓘ HTTP header field specifications ⓘ HTTP method definitions ⓘ HTTP over TLS specifications ⓘ HTTP range requests specifications ⓘ
linked to:
HTTP/1.1 Range Requests
HTTP semantics specifications ⓘ HTTP status code definitions ⓘ HTTP/1.1 authentication specification ⓘ
linked to:
RFC 7235
HTTP/1.1 caching specification ⓘ HTTP/1.1 conditional requests specification ⓘ
linked to:
RFC 7232
HTTP/1.1 message syntax and routing specification ⓘ
linked to:
RFC 7230
HTTP/1.1 range requests specification ⓘ
linked to:
HTTP/1.1 Range Requests
HTTP/1.1 specification ⓘ
linked to:
HTTP/1.1
HTTP/2 HPACK header compression specification ⓘ
linked to:
HPACK
HTTP/2 specification ⓘ
linked to:
RFC 7540
HTTP/3 QPACK header compression specification ⓘ HTTP/3 specification ⓘ
linked to:
HTTP/3
Hypertext Transfer Protocol ⓘ
linked to:
HTTP
URI-related HTTP specifications ⓘ content coding specifications for HTTP ⓘ message routing specifications for HTTP ⓘ transfer coding specifications for HTTP ⓘ |
| standardizes |
HTTP over QUIC
ⓘ
linked to:
HTTP/3
HTTP over TCP ⓘ HTTP over TLS ⓘ
linked to:
HTTPS
application-layer protocol for the World Wide Web ⓘ semantics of HTTP header fields ⓘ semantics of HTTP methods ⓘ semantics of HTTP status codes ⓘ wire formats for HTTP messages ⓘ |
| usesProcess |
IETF consensus process
ⓘ
IETF working group meetings ⓘ mailing list discussions ⓘ open participation ⓘ |
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: HTTP Working Group Description of subject: The HTTP Working Group is an IETF standards body responsible for developing and maintaining the Hypertext Transfer Protocol and related web communication specifications.
Referenced by (15)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: HTTP Working Group
linked to: HTTP Working Group
linked to: HTTP Working Group
linked to: HTTP Working Group
linked to: HTTP Working Group
linked to: HTTP Working Group
linked to: HTTP Working Group
linked to: HTTP Working Group