Glossary of terms defined in the Solid Specifications

Generated from the specfications using https://github.com/jeff-zucker/specs2gloss

data pod
A data pod is a place for storing documents, with mechanisms for controlling who can access what.
https://solidproject.org/TR/protocol#data-pod
Solid app
A Solid app is an application that reads or writes data from one or more storages.
https://solidproject.org/TR/protocol#solid-app
URI
A Uniform Resource Identifier (URI) provides the means for identifying resources [RFC3986].
https://solidproject.org/TR/protocol#uniform-resource-identifier
resource
A resource is the target of an HTTP request identified by a URI [RFC7231].
https://solidproject.org/TR/protocol#resource
container resource
A container resource is a hierarchical collection of resources that contains other resources, including containers.
https://solidproject.org/TR/protocol#container-resource
root container
A root container is a container resource that is at the highest level of the collection hierarchy.
https://solidproject.org/TR/protocol#root-container
resource metadata
Resource metadata encompasses data about resources described by means of RDF statements [RDF11-CONCEPTS].
https://solidproject.org/TR/protocol#resource-metadata
agent
An agent is a person, social entity, or software identified by a URI; e.g., a WebID denotes an agent [WEBID].
https://solidproject.org/TR/protocol#agent
owner
An owner is a person or a social entity that is considered to have the rights and responsibilities of a data storage. An owner is identified by a URI, and implicitly has control over all data in a storage. An owner is first set at storage provisioning time and can be changed.
https://solidproject.org/TR/protocol#owner
origin
An origin indicates where an HTTP request originates from [RFC6454].
https://solidproject.org/TR/protocol#origin
read operation
A read operation entails that information about a resource’s existence or its description can be known. [Source]
https://solidproject.org/TR/protocol#read-operation
write operation
A write operation entails that information about resources can be created or removed. [Source]
https://solidproject.org/TR/protocol#write-operation
append operation
An append operation entails that information can be added but not removed. [Source]
https://solidproject.org/TR/protocol#append-operation
URI
A Uniform Resource Identifier (URI) provides the means for identifying resources [RFC3986].
https://solidproject.org/TR/wac#uri
resource
A resource is the target of an HTTP request identified by a URI [RFC7231].
https://solidproject.org/TR/wac#resource
container resource
A container resource is a hierarchical collection of resources that contains other resources, including containers.
https://solidproject.org/TR/wac#container-resource
root container
A root container is a container resource that is at the highest level of the collection hierarchy.
https://solidproject.org/TR/wac#root-container
ACL resource
An ACL resource is represented by an RDF document [RDF11-CONCEPTS] that includes Authorizations determining access to resources.
https://solidproject.org/TR/wac#acl-resource
Authorization
An Authorization is an abstract thing which is identified by a URI and whose properties are defined in an ACL resource, e.g., access modes granted to agents the ability to perform operations on resources.
https://solidproject.org/TR/wac#authorization
access mode
An access mode is a class of operations that can be performed on one or more resources.
https://solidproject.org/TR/wac#access-mode
agent
An agent is a person, social entity or software identified by a URI, e.g., a WebID denotes an agent [WEBID].
https://solidproject.org/TR/wac#agent
agent group
An agent group is a group of persons or entities identified by a URI.
https://solidproject.org/TR/wac#agent-group
agent class
An agent class is a class of persons or entities identified by a URI.
https://solidproject.org/TR/wac#agent-class
origin
An origin indicates where an HTTP request originates from [RFC6454].
https://solidproject.org/TR/wac#origin
Notification Subscription API
An HTTP URI at which a client can initiate a subscription to notification events for a particular set of resources [RFC7231].
https://solidproject.org/TR/notifications-protocol#notification-subscription-api
Notification Subscription Metadata Resource
An RDF document [RDF11-CONCEPTS] that includes metadata about the capabilities of a Notification Subscription API.
https://solidproject.org/TR/notifications-protocol#notification-subscription-metadata-resource
@context
The @context property is MUST be an array containing the value https://www.w3.org/ns/solid/notification/v1. Other values MAY also be present.
https://solidproject.org/TR/notifications-protocol#server-subscription-request-context
expiration
An ISO 8601 datetime value indicating a proposed expiration point for a subscription. A server may choose another value.
https://solidproject.org/TR/notifications-protocol#feature-expiration
state
An opaque value representing the last known state of a resource. If the resource state is known to have changed when the client establishes a subscription, an initial notification must be sent to the client. This value should correspond to a resource's ETag header value.
https://solidproject.org/TR/notifications-protocol#feature-state
rate
An ISO 8601 duration value indicating the minimum amount of time to elapse between notifications sent to the client
https://solidproject.org/TR/notifications-protocol#feature-rate
accept
A MIME-Type value that indicates the desired serialization of the notification. For instance, text/turtle may be acceptable.
https://solidproject.org/TR/notifications-protocol#feature-accept
source
The source property is used in the body of the subscription response. The value of this property MUST be a URI, using the wss scheme. A JavaScript client would use the entire value as input to the WebSocket constructor.
https://solidproject.org/TR/websocket-subscription-2021#websocketsubscription2021-source