RFC 7519
E830585
RFC 7519 is the Internet standard that specifies the JSON Web Token (JWT) format for securely representing claims between parties in web authentication and authorization.
All labels observed (2)
How this entity was disambiguated
This entity first appeared as the object of triple T9931381 — 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 7519 Context triple: [JSON Web Token, definedIn, RFC 7519]
-
A.
RFC 6749
RFC 6749 is the IETF specification that defines the OAuth 2.0 authorization framework used for secure delegated access to web resources.
-
B.
RFC 6750
RFC 6750 is an IETF specification that defines the use of bearer tokens for securing HTTP requests in the OAuth 2.0 authorization framework.
-
C.
RFC 4627
RFC 4627 is the original IETF specification that formally defined the JSON (JavaScript Object Notation) data interchange format.
-
D.
JSON Web Tokens (JWT)
JSON Web Tokens (JWT) are a compact, URL-safe standard for securely transmitting digitally signed claims between parties, commonly used for stateless authentication and authorization in web applications.
-
E.
RFC 5849
RFC 5849 is the Internet standard that originally defined the OAuth 1.0 protocol for secure delegated authorization before being superseded by OAuth 2.0 in RFC 6749.
- 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 7519 Target entity description: RFC 7519 is the Internet standard that specifies the JSON Web Token (JWT) format for securely representing claims between parties in web authentication and authorization.
-
A.
RFC 6749
RFC 6749 is the IETF specification that defines the OAuth 2.0 authorization framework used for secure delegated access to web resources.
-
B.
RFC 6750
RFC 6750 is an IETF specification that defines the use of bearer tokens for securing HTTP requests in the OAuth 2.0 authorization framework.
-
C.
RFC 4627
RFC 4627 is the original IETF specification that formally defined the JSON (JavaScript Object Notation) data interchange format.
-
D.
JSON Web Tokens (JWT)
JSON Web Tokens (JWT) are a compact, URL-safe standard for securely transmitting digitally signed claims between parties, commonly used for stateless authentication and authorization in web applications.
-
E.
RFC 5849
RFC 5849 is the Internet standard that originally defined the OAuth 1.0 protocol for secure delegated authorization before being superseded by OAuth 2.0 in RFC 6749.
- F. None of above. chosen
Statements (50)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ technical specification ⓘ |
| appliesTo |
HTTP-based APIs
ⓘ
OAuth 2.0 ⓘ OpenID Connect ⓘ |
| area | Security ⓘ |
| category | Standards Track ⓘ |
| defines |
JSON Web Token
ⓘ
linked to:
JSON Web Tokens (JWT)
|
| definesAbbreviation |
JWT
ⓘ
linked to:
JSON Web Tokens (JWT)
|
| documentType | Standards-track RFC ⓘ |
| format | text ⓘ |
| identifier |
RFC7519
ⓘ
linked to:
RFC 7519
|
| language | English ⓘ |
| number | 7519 ⓘ |
| obsoletedBy | None ⓘ |
| obsoletes | None ⓘ |
| partOf | JOSE specification suite ⓘ |
| primaryPurpose |
securely represent claims between parties
ⓘ
web authentication ⓘ web authorization ⓘ |
| publicationDate | May 2015 ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedTo |
RFC 7515
ⓘ
RFC 7516 ⓘ RFC 7517 ⓘ RFC 7518 ⓘ |
| securityConsiderationsSection | Yes ⓘ |
| shortTitle |
JWT
ⓘ
linked to:
JSON Web Tokens (JWT)
|
| specifies |
JWT claims
ⓘ
JWT encoding ⓘ JWT header ⓘ JWT payload ⓘ JWT processing rules ⓘ JWT signature ⓘ JWT validation ⓘ private claim names ⓘ public claim names ⓘ registered claim names ⓘ |
| specifiesFormatOf | JSON-based security tokens ⓘ |
| standardizes | token-based authentication mechanism ⓘ |
| status | Proposed Standard ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| title |
JSON Web Token (JWT)
ⓘ
linked to:
JSON Web Tokens (JWT)
|
| usesDataFormat | JSON ⓘ |
| usesEncoding | Base64url ⓘ |
| workingGroup |
JOSE
ⓘ
JSON Object Signing and Encryption ⓘ
linked to:
JSON Object Signing and Encryption framework
|
| year | 2015 ⓘ |
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 7519 Description of subject: RFC 7519 is the Internet standard that specifies the JSON Web Token (JWT) format for securely representing claims between parties in web authentication and authorization.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.