- character
-
From The Platform for Privacy Preferences 1.0 (P3P1.0) Specification (2002-04-16)
Strings consist of a sequence of zero or more characters, where a character is defined as in the XML Recommendation [XML]. A single character in P3P thus corresponds to a single Unicode abstract character with a single corresponding Unicode scalar value (see [UNICODE]).
- data category
-
From The Platform for Privacy Preferences 1.0 (P3P1.0) Specification (2002-04-16)
A significant attribute of a data element or data set that may be used by a trust engine to determine what type of element is under discussion, such as physical contact information. P3P1.0 specifies a set of data categories.
- data element
-
From The Platform for Privacy Preferences 1.0 (P3P1.0) Specification (2002-04-16)
An individual data entity, such as last name or telephone number. For interoperability, P3P1.0 specifies a base set of data elements.
- data schema
-
From The Platform for Privacy Preferences 1.0 (P3P1.0) Specification (2002-04-16)
A collection of data elements and sets defined using the P3P1.0 DATASCHEMA element. P3P1.0 defines a standard data schema called the P3P base data schema.
- data set
-
From The Platform for Privacy Preferences 1.0 (P3P1.0) Specification (2002-04-16)
A known grouping of data elements, such as "user.home-info.postal". The P3P1.0 base data schema specifies a number of data sets.
- data structure
-
From The Platform for Privacy Preferences 1.0 (P3P1.0) Specification (2002-04-16)
A hierarchical description of a set of data elements. A data set can be described according to its data structure. P3P1.0 defines a set of basic datastructures that are used to describe the data sets in the P3P base data schema.
- equable practice
-
From The Platform for Privacy Preferences 1.0 (P3P1.0) Specification (2002-04-16)
A practice that is very similar to another in that the purpose and recipients are the same or more constrained than the original, and the other disclosures are not substantially different. For example, two sites with otherwise similar practices that follow different -- but similar -- sets of industry guidelines.
- identified data
-
From The Platform for Privacy Preferences 1.0 (P3P1.0) Specification (2002-04-16)
Data that reasonably can be used by the data collector to identify an individual.
- policy
-
From The Platform for Privacy Preferences 1.0 (P3P1.0) Specification (2002-04-16)
A collection of one or more privacy statements together with information asserting the identity, URI, assurances, and dispute resolution procedures of the service covered by the policy.
- practice
-
From The Platform for Privacy Preferences 1.0 (P3P1.0) Specification (2002-04-16)
The set of disclosures regarding data usage, including purpose, recipients, and other disclosures.
- preference
-
From The Platform for Privacy Preferences 1.0 (P3P1.0) Specification (2002-04-16)
A rule, or set of rules, that determines what action(s) a user agent will take. A preference might be expressed as a formally defined computable statement (e.g., the [APPEL] preference exchange language).
- purpose
-
From The Platform for Privacy Preferences 1.0 (P3P1.0) Specification (2002-04-16)
The reason(s) for data collection and use.
- repository
-
From The Platform for Privacy Preferences 1.0 (P3P1.0) Specification (2002-04-16)
A mechanism for storing user information under the control of the user agent.
- resource
-
From The Platform for Privacy Preferences 1.0 (P3P1.0) Specification (2002-04-16)
A network data object or service that can be identified by a URI. Resources may be available in multiple representations (e.g. multiple languages, data formats, size, and resolutions) or vary in other ways.
- safe zone
-
From The Platform for Privacy Preferences 1.0 (P3P1.0) Specification (2002-04-16)
Part of a Web site where the service provider performs only minimal data collection, and any data that is collected is used only in ways that would not reasonably identify an individual.
- service
-
From The Platform for Privacy Preferences 1.0 (P3P1.0) Specification (2002-04-16)
A program that issues policies and (possibly) data requests. By this definition, a service may be a server (site), a local application, a piece of locally active code, such as an ActiveX control or Java applet, or even another user agent. Typically, however, a service is usually a Web site. In this specification the terms "service" and "Web site" are often used interchangeably.The person or legal entity which offers information, products or services from a Web site, collects information, and is responsible for the representations made in a practice statement.
- service provider (Data controller, legal entity)
-
From The Platform for Privacy Preferences 1.0 (P3P1.0) Specification (2002-04-16)
The person or legal entity which offers information, products or services from a Web site, collects information, and is responsible for the representations made in a practice statement.
- statement
-
From The Platform for Privacy Preferences 1.0 (P3P1.0) Specification (2002-04-16)
A P3P statement is a set of privacy practice disclosures relevant to a collection of data elements.
- URI
-
From The Platform for Privacy Preferences 1.0 (P3P1.0) Specification (2002-04-16)
A Uniform Resource Identifier used to locate Web resources. For definitive information on URI syntax and semantics, see [URI]. URIs that appear within XML or HTML have to be treated as specified in [CHARMODEL], section Character Encoding in URI References. This does not apply to URIs appearing in HTTP header fields; the URIs there should always be fully escaped.
- user
-
From The Platform for Privacy Preferences 1.0 (P3P1.0) Specification (2002-04-16)
An individual (or group of individuals acting as a single entity) on whose behalf a service is accessed and for which personal data exists. P3P policies describe the collection and use of personal data about this individual or group.A program whose purpose is to mediate interactions with services on behalf of the user under the user's preferences. A user may have more than one user agent, and agents need not reside on the user's desktop, but any agent must be controlled by and act on behalf of only the user. The trust relationship between a user and his or her agent may be governed by constraints outside of P3P. For instance, an agent may be trusted as a part of the user's operating system or Web client, or as a part of the terms and conditions of an ISP or privacy proxy.