A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z



[General] An abbreviation of "Access Control List".
It defines which users are authorized to access and which control instructions are permitted to be used depending on the privileges granted to objects.
(Example: Read: Read permissions, Write: Edit permissions, Read/Write: Read/Edit permissions)


[Pesronium] One of the cell control objects. It represents user authentication means in that cell, and can register multiple cells per cell. The basic type (selected by default) is composed of information such as account name and password. It is also possible to correspond to other authentication means such as OpenID Connect by installing a plugin. It may be used to register multiple authentication means in an individual's cell or may be used to authenticate an organization member in an organization's cell.


[OData] Shows the relationship between two or more EntityTypes (RDB tables). It is defined by a pair of AssociationEnds and $links in between.
Associations are categorized into "one-to-one", "one-to-many", and "many-to-many". For details, refer to User OData Model.


[OData]The EntityType that is the endpoint that constitutes the Association. The Association consists of a pair of AssociationEnds and $ links between them.


[General] Authentication. For the account authentication of Personium, the method that performs authentication based on the created account name and password to acquire tokens has been adopted.


bar file

[Personium] An abbreviation of "box archive file". This archive file is a compilation of box structure details.
The hierarchical structure in the folder represents the hierarchical structure of WebDAV collections, and the files stored in WebDAV are retained by storing files at these hierarchical levels.
For details, refer to bar File.


[Personium] The area that stores data used for the application. It is also a WebDAV collection. It has a unique name and schema URL. One box is initially retained in a cell (the main box) even before boxes are created, but it cannot be deleted.

Box installation

[Personium] To create a box using the bar file. For details, refer to the Box Installation API.

Box level ACL

[Personium] The ACL for resources under the box. For details, refer to Access Control Model.



[Personium] Data store for each data subject. PDS (Personal Data Store) is used for personal use. In Personium, it is possible to use the concept of data principals not only for people but also for data and organizations of organizations and objects.
(Eg My Cell, Your Cell, Cell of a Company, Cell of a Department, Cell of My Car)

Cell control object

[Personium] The definition structure that defines each function of a cell, including Role, Account, Box, ExtCell, and ExtRole. Refer to Cell Control Object.

Cell level ACL

[Personium] ACL to Cell excluding Box level access authority. Define the operation of the Cell control object and the access control to the subordinate Box.

Cell Profile

[Personium] The item that shows the cell name, image, and other cell information within the Personium portal.


[WebDAV] Corresponds to the folder / directory in the ordinary file system. Personium can handle special collections called "OData Service Collection" and "Engine Service Collection" in addition to regular collections.


[OData] The property that has an attribute accompanied by lower attributes. The item name is ComplexTypeProperty.
(For example, if "Address" is a ComplexType, possible attributes could be Street 1, Street 2, Country, Zip code, Prefecture, City/town/village, etc.)


[OData] The name of lower attributes of a ComplexType. For example, if ComplexType is "Address", possible attributes could be Street 1, Street 2, Country, Zip code, Prefecture, City/town/village, etc.


[General] An abbreviation of "Cross-Origin Resource Sharing". JavaScript shall permit XMLHttpRequest for other domains in the Web page. Refer to CORS Support.
(For details, refer to External Site)

Cross Domain Access Control

[General] Access control for servers that have different domains. In Personium, the Cross Domain Access Policy File based on XMLHttpRequest Level2 is used for control.


Engine Service Collection

[Personium] A special collection for the user to register new logic on the server side. For details, refer to Engine Service Collection.


[OData] The recording structure of data, which corresponds to one row of an RDB table. For example, it represents a row of information such as Name, Address, and Sex.


[OData] The definition structure for representing data structure as an Entity Data Model (EDM). EntityTypes represent broader concepts (such as customers and order details)


[HTTP] Refers to the Entity Tag. It is possible to send requests depending on the client status using unique identifiers used for Web cache verification.
This makes use of the cache more effective and secures bandwidth when it is not necessary to return all responses in a situation where contents are not updated.


[Personium] An instance that occurs inside or outside Personium. For details, refer to Event Overview.


[Personium] External and internal event occurrence logs. These can be acquired using the Log Acquisition API.

$expand query

[OData] One of the supported OData queries. This query is for acquiring specified relation information simultaneously by addition to a data acquisition request. (Details)

External Cell

[Personium] An external cell. It is one of the cell control objects. It is a cell outside a cell. Cells of all units can be handled as external cells. For details, refer to Cell Control Object.

External Role

[Personium] An external role. It is one of the cell control objects (ExtRole). It represents a user entity to which a specific role has been granted in an external cell that has a specific relationship. For example, it is possible to register "External Role" such as "administrator (Role) of affiliated organization (Cell) " or "consulting doctor (Role) of goods purchase customer (Cell) ", etc., and by linking this with the role, operations such as data disclosure etc. to indirectly related others It is possible to use like to forgive.


$filter query

[OData] One of the supported OData queries. This query is for refining data by specifying search conditions. (Details)

$format query

[OData] One of the supported OData queries. This query is for specifying the media type in the HTTP response. (Details)


[General] An abbreviation of "Fully Qualified Domain Name".
This represents the complete domain name that defines a specific computer or host on the Internet (for example,

Full-Text Search Query

[OData] The query for performing a search that compares every word in the entire data included in the EntityType by adding q="Search word" to a request. (Details)


Implicit Flow

[OAuth2.0] One of the permitting flows defined in OAuth2.0. Clients directly receive access tokens as substitutes for permission codes (resource owner permission results).
For details, refer to External Site.

$inlinecount query

[OData] One of the supported OData queries. This query is for displaying the count of entities in the collection. (Details)


Main Box

[Personium] The box named "__" (two underscores) created by default during cell creation. Its behavior is similar to that of normal boxes but this box is undeletable.
It is used not only for application data storage but also for the storage of information (json format) specific to that cell.


[Personium] The function that sends and receives messages between cells in Personium. It can transmit and receive arbitrary messages of users and issue relationships ($links) between cells. For details, refer to Message Model.


[OData] Multiplicity. The related EntityType count when AssociationEnd is created.
The notation of AssociationEnd multiplicity is one of "1", "0..1" (0 or 1), and "*" (many) with respect to the relationship between two EntityTypes.



[OData] The property that represents the navigation from one end to the other end of an association in the Entity Data Model or OData data structure.



[OData] An abbreviation of "Open Data Protocol". It is one of the collections (a data set stored in a box). This is the standard data access protocol conforming to HTML and enables CRUD access to data resources.
For details on OData, click here.

OData Service Collection

[Personium] It is a special WebDAV extension collection for handling arbitrary relational data with OData protocol, and it can be created in arbitrary hierarchy in Box. Under this collection itself is the root of the service of OData and $ metadata itself storing the schema information is also the root of the OData space for setting the schema. Relational data can be handled based on arbitrary schema defined here.

$orderby query

[OData] One of the supported OData queries. The values are displayed sorted in the order specified by the user. The default is ascending order. (Details)



[OData] The column head value of each EntityType. For example, if the EntityType is "Customer", possible properties could be "ID", "Name", and "Address".


[Personium] Privileges granted to the roles defined in the cell to access data in the box associated with specific roles.
Privileges are defined in ACL configuration in Personium. For details, refer to Access Control Model.



[General] An abbreviation of "role-based access control". It involves defining roles for various accounts and configuring access control based on roles.


[Personium] A definition body that receives Relation issue requests and messages from specific cells.

Refresh token

[OAuth2] The token used for reissuing access tokens. The refresh token is valid for 24 hours.

Refresh token authentication

[Personium] The process that reissues access tokens..


[Personium] A cell control object indicating the relationship between itself (own cell) and another person (external cell). By linking the cell control object Relation and Role, it is possible to collectively assign roles to accessers from other cells in a specific relationship. Be aware that it is a model that independently defines unilateral relationships of relationships to others seen by themselves. In principle, Relation registration of own cell and link to external cell can be done without consent of the other party. For example, when expressing a mutual relationship of "parent and child", a Relation object "My child" is registered in the parent cell and associated with a child cell whose parent cell is registered as an external cell In addition to this, it is desirable to register Relation objects having the opposite meaning of "my parents" in the child cells to the parent cell that the child cell registers as an external cell, and link them.

Relation class URL

[Personium] The URL of a related resource defined as an application. The relation class URL structure is as follows:
${Schema URL}/__relation/__/${RelationName}

Relation instance URL

[Personium] The URL of a specific relation with respect to which a request is sent to one or more external cells.
The relation instance URL structure is as follows:
${Cell URL}/__relation/${BoxName}/${RelationName}


[Personium] The attribute value of an ACL element that defines the request level for box schema privileges.


[WebDAV] Represents the collection type. ODataCollection/ServiceCollection/DavCollection/file etc.


[Personium] One of the cell control objects. This represents the "role" defined for all cells. (Examples: administrator, teacher, student)
As it is possible to specify which accounts (users) can access the cell, the settings that define the account ownership of the cell can be created with different access privileges.

Role class URL

[Personium] The URL of the role for storage inside the trans-cell token. The role class URL structure is as follows:
${schema URL}/__role/__/${RoleName}

Role instance URL

[Personium] The URL that provides the current status of the role registered with a specific cell. It is the same as the role resource URL. The Schema is as follows:
${Cell URL}/__role/${BoxName}/${RoleName}


[OAuth2.0] An abbreviation of "Resource Owner Password Credentials". It is one of the permitting processes defined in OAuth2.0. For details, refer to External Site. A standard authentication method for obtaining Personium tokens using ID / PW.


Schema URL

[Personium] The URL that represents the schema stored in Personium. The definition is Cell URL or URI.

$select query

[OData] One of the supported OData queries. This query is for specifying and acquiring only a specific property during data acquisition. Multiple properties can also be specified. (Details)


[Personium] The definition structure that transmits messages for relation setting approval and normal messages for a target cell. For details, refer to Message Model.

Service Collection

[Personium] One of the collections (a data set stored in a box). This is a collection of services to execute user-defined server-side logic.

Service registration

[WebDAV] To register user-defined server-side logic in a collection.

$skip query

[OData] One of the supported OData queries. This query is for extracting data excluding the specified count from the display among acquired data. (Details)



[General] A random string used mainly for user authentication. Tokens are used for access to stored data and resources in Personium. A token is described in the cURL requested by a client.
There are the following types in Personium, and the tokens are changed an hour after issuing.
(1)Cell local token: Used for the access to resources in the authenticated cell
(2)Trans-cell token: Used for the access to resources in a cell authenticated by another cell

Token authentication

[General] One of authentication processes. The method for authentication using the access token described in the cURL requested by a client. For details, refer to Certification Model.

$top query

[OData] One of the supported OData queries. This specifies the maximum number of acquired data records and returns data for that count. Extracted data is counted from the beginning in the set. (Details)



[Personium] The data area composed of multiple cells on the Personium platform server. It has a fully qualified domain name (UnitFQDN) that is referred to as the absolute domain name.

Unit control object

[Personium] A group of objects for creating and managing cells as the unit user (administrator).

Unit User

[Personium] Unit administrator user. This user has CRUD (Create/Read/Update/Delete) privileges within the unit.



[WebDAV] An abbreviation of "Web-based Distributed Authoring and Versioning". This is the protocol for various users to co-write documents and files on the Web server; it is an extension of HTTP.
On the Personium portal, WebDAV collections are files and folders, and CRUD functions are used.
Refer to WebDAV Resources.

A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z