OAuth Working Group
E697199
The OAuth Working Group is an IETF body responsible for developing and maintaining the OAuth protocol standards for secure authorization on the web.
All labels observed (2)
| Label | Occurrences |
|---|---|
| IETF OAuth Working Group | 1 |
| OAuth Working Group canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T7933983 — 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: OAuth Working Group Context triple: [RFC 6749, workingGroup, OAuth Working Group]
-
A.
HTTP Working Group
The HTTP Working Group is an IETF standards body responsible for developing and maintaining the Hypertext Transfer Protocol and related web communication specifications.
-
B.
OAuth 2.0
OAuth 2.0 is an industry-standard authorization framework that enables applications to obtain limited access to user resources on HTTP services without exposing user credentials.
-
C.
OpenID Connect
OpenID Connect is an identity layer built on top of OAuth 2.0 that enables secure user authentication and single sign-on across applications.
-
D.
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.
-
E.
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.
- 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: OAuth Working Group Target entity description: The OAuth Working Group is an IETF body responsible for developing and maintaining the OAuth protocol standards for secure authorization on the web.
-
A.
HTTP Working Group
The HTTP Working Group is an IETF standards body responsible for developing and maintaining the Hypertext Transfer Protocol and related web communication specifications.
-
B.
OAuth 2.0
OAuth 2.0 is an industry-standard authorization framework that enables applications to obtain limited access to user resources on HTTP services without exposing user credentials.
-
C.
OpenID Connect
OpenID Connect is an identity layer built on top of OAuth 2.0 that enables secure user authentication and single sign-on across applications.
-
D.
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.
-
E.
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.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
IETF working group
ⓘ
standards development organization unit ⓘ |
| abbreviation | OAuth WG NERFINISHED ⓘ |
| area | Security Area ⓘ |
| field |
authorization protocols
ⓘ
identity and access management ⓘ web security ⓘ |
| goal |
develop and maintain OAuth protocol standards
ⓘ
enable secure delegated authorization on the web ⓘ |
| hasCommunicationChannel | mailing list ⓘ |
| meetsAt | IETF meetings NERFINISHED ⓘ |
| parentOrganization | Internet Engineering Task Force NERFINISHED ⓘ |
| produces |
Internet-Drafts
NERFINISHED
ⓘ
RFCs ⓘ |
| scope |
authorization framework
ⓘ
client and authorization server interaction ⓘ security best practices for OAuth ⓘ token usage ⓘ |
| standardizes |
Bearer Token Usage
NERFINISHED
ⓘ
JSON Web Token Profile for OAuth 2.0 Access Tokens NERFINISHED ⓘ OAuth 2.0 NERFINISHED ⓘ OAuth 2.0 Authorization Server Issuer Identification NERFINISHED ⓘ OAuth 2.0 Authorization Server Metadata NERFINISHED ⓘ OAuth 2.0 Demonstrating Proof-of-Possession at the Application Layer (DPoP) NERFINISHED ⓘ OAuth 2.0 Device Authorization Grant NERFINISHED ⓘ OAuth 2.0 Dynamic Client Registration NERFINISHED ⓘ OAuth 2.0 Incremental Authorization NERFINISHED ⓘ OAuth 2.0 JWT Secured Authorization Request (JAR) NERFINISHED ⓘ OAuth 2.0 JWT-Secured Authorization Response Mode (JARM) NERFINISHED ⓘ OAuth 2.0 Mutual-TLS Client Authentication and Certificate-Bound Access Tokens NERFINISHED ⓘ OAuth 2.0 Pushed Authorization Requests NERFINISHED ⓘ OAuth 2.0 Resource Indicators NERFINISHED ⓘ OAuth 2.0 Rich Authorization Requests NERFINISHED ⓘ OAuth 2.0 Security Best Current Practice NERFINISHED ⓘ OAuth 2.0 Security Topics NERFINISHED ⓘ OAuth 2.0 Step-up Authentication Challenge Protocol NERFINISHED ⓘ OAuth 2.0 Token Exchange NERFINISHED ⓘ OAuth 2.0 Token Introspection NERFINISHED ⓘ OAuth 2.0 Token Revocation NERFINISHED ⓘ OAuth 2.0 for Browser-Based Apps NERFINISHED ⓘ OAuth 2.0 for Native Apps NERFINISHED ⓘ OAuth 2.1 NERFINISHED ⓘ Proof Key for Code Exchange NERFINISHED ⓘ |
| topic |
access tokens
ⓘ
authorization server security ⓘ client authentication ⓘ secure authorization ⓘ |
| usesProcess | IETF consensus process ⓘ |
| website | https://datatracker.ietf.org/wg/oauth ⓘ |
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: OAuth Working Group Description of subject: The OAuth Working Group is an IETF body responsible for developing and maintaining the OAuth protocol standards for secure authorization on the web.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.
this entity surface form:
IETF OAuth Working Group