Permissions API specification
E242838
The Permissions API specification is a web standard that defines a unified way for web applications to query and manage user permission states for powerful browser features like notifications, geolocation, and camera access.
All labels observed (6)
| Label | Occurrences |
|---|---|
| PermissionStatus | 2 |
| Permissions API specification canonical | 2 |
| PermissionDescriptor | 1 |
| PermissionStatus interface | 1 |
| Permissions interface | 1 |
| Permissions.query() | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T2175045 — 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: Permissions API specification Context triple: [Notifications API, relatedTo, Permissions API specification]
-
A.
Resource Description and Access
Resource Description and Access is a modern library cataloging standard that provides guidelines for describing and accessing information resources in both digital and physical formats.
-
B.
Perm
Perm is a major industrial and cultural city in the Ural region of Russia, situated on the Kama River and historically significant as a gateway between European and Asian Russia.
-
C.
OpenAPI
OpenAPI is a widely adopted, language-agnostic specification for describing and documenting RESTful APIs in a standardized, machine-readable format.
-
D.
REST API
A REST API is a web service interface that allows clients to interact with resources over HTTP using standard methods like GET, POST, PUT, and DELETE in a stateless, structured way.
-
E.
API gateway
An API gateway is a server that acts as a single entry point for client requests to multiple backend services, handling tasks like routing, security, rate limiting, and protocol translation.
- 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: Permissions API specification Target entity description: The Permissions API specification is a web standard that defines a unified way for web applications to query and manage user permission states for powerful browser features like notifications, geolocation, and camera access.
-
A.
Resource Description and Access
Resource Description and Access is a modern library cataloging standard that provides guidelines for describing and accessing information resources in both digital and physical formats.
-
B.
Perm
Perm is a major industrial and cultural city in the Ural region of Russia, situated on the Kama River and historically significant as a gateway between European and Asian Russia.
-
C.
OpenAPI
OpenAPI is a widely adopted, language-agnostic specification for describing and documenting RESTful APIs in a standardized, machine-readable format.
-
D.
REST API
A REST API is a web service interface that allows clients to interact with resources over HTTP using standard methods like GET, POST, PUT, and DELETE in a stateless, structured way.
-
E.
API gateway
An API gateway is a server that acts as a single entry point for client requests to multiple backend services, handling tasks like routing, security, rate limiting, and protocol translation.
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
Browser API specification
ⓘ
W3C specification ⓘ Web standard ⓘ |
| aimsTo |
improve user privacy controls
ⓘ
provide a consistent permissions model across features ⓘ reduce permission prompt fatigue ⓘ |
| allows |
feature-specific permission descriptors
ⓘ
querying current permission state without prompting the user ⓘ |
| appliesTo |
web applications
ⓘ
web browsers ⓘ |
| concerns |
powerful web platform features
ⓘ
privacy-sensitive browser features ⓘ user permissions ⓘ |
| defines | Permissions API ⓘ |
| definesConcept |
Permissions API specification
self-linksurface differs
ⓘ
surface form:
PermissionDescriptor
Permissions API specification self-linksurface differs ⓘ
surface form:
PermissionStatus
permission state ⓘ |
| definesInterface |
Permissions API specification
self-linksurface differs
ⓘ
surface form:
PermissionStatus interface
Permissions API specification self-linksurface differs ⓘ
surface form:
Permissions interface
|
| definesMethod |
Permissions API specification
self-linksurface differs
ⓘ
surface form:
Permissions.query()
Permissions.request() ⓘ Permissions.revoke() ⓘ navigator.permissions.query() ⓘ navigator.permissions.request() ⓘ navigator.permissions.revoke() ⓘ |
| definesPermissionState |
denied
ⓘ
granted ⓘ prompt ⓘ |
| hasFullName | Permissions API ⓘ |
| partOf |
Open Web Platform
ⓘ
surface form:
Web Platform specifications
|
| relatedTo |
Geolocation API
ⓘ
surface form:
Geolocation API specification
Media Capture and Streams specification ⓘ Notifications API Standard ⓘ
surface form:
Notifications API specification
|
| standardizes |
a unified way to manage permission states
ⓘ
a unified way to query permission states ⓘ permissions management for web applications ⓘ |
| supportsFeature |
background-sync permission
ⓘ
camera permission ⓘ clipboard-read permission ⓘ clipboard-write permission ⓘ geolocation permission ⓘ microphone permission ⓘ midi permission ⓘ notifications permission ⓘ persistent-storage permission ⓘ push permission ⓘ |
| usedBy |
browsers to expose permission state to scripts
ⓘ
web developers to check permissions programmatically ⓘ |
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: Permissions API specification Description of subject: The Permissions API specification is a web standard that defines a unified way for web applications to query and manage user permission states for powerful browser features like notifications, geolocation, and camera access.
Referenced by (8)
Full triples — surface form annotated when it differs from this entity's canonical label.
subject surface form:
Notifications API
this entity surface form:
PermissionStatus
Permissions API specification
→
definesConcept
→
Permissions API specification
self-linksurface differs
ⓘ
this entity surface form:
PermissionStatus
Permissions API specification
→
definesConcept
→
Permissions API specification
self-linksurface differs
ⓘ
this entity surface form:
PermissionDescriptor
Permissions API specification
→
definesInterface
→
Permissions API specification
self-linksurface differs
ⓘ
this entity surface form:
Permissions interface
Permissions API specification
→
definesInterface
→
Permissions API specification
self-linksurface differs
ⓘ
this entity surface form:
PermissionStatus interface
Permissions API specification
→
definesMethod
→
Permissions API specification
self-linksurface differs
ⓘ
this entity surface form:
Permissions.query()