This document uses the following terms:
absolute path: A string that identifies the location of a file and that begins with a drive identifier and root directory or network share and ends with the complete file name. Examples are C:\Documents\Work\example.txt and \\netshare\Documents\Work\example.txt.
absolute URL: The full Internet address of a page or other World Wide Web resource. The absolute URL includes a protocol, such as "http," a network location, and an optional path and file name — for example, http://www.treyresearch.net/.
access control list (ACL): A list of access control entries (ACEs) that collectively describe the security rules for authorizing access to some resource; for example, an object or set of objects.
alert: An Internet message that is sent to subscribers automatically to notify them when user-defined criteria are met. Alerts are generated automatically when items such as documents, webpages, list items, sites, or other resources on a server are changed.
anchor text: The text that is included with a hyperlink to describe the target content of a hyperlink.
anonymous access link: An implementation of tokenized sharing link that can allow users to gain guest access to content, such as a document or folder, without sign-in when using the specific tokenized sharing link.
app: (1) See web application.
(2) See SharePoint Add-in.
app instance: An instantiation of an app on a specific site.
app package: An implementation-specific file that specifies an app.
app principal: Designates an authenticated entity that is not a user.
app product identifier: A unique designation that is shared by all versions of an app.
application: A participant that is responsible for beginning, propagating, and completing an atomic transaction. An application communicates with a transaction manager in order to begin and complete transactions. An application communicates with a transaction manager in order to marshal transactions to and from other applications. An application also communicates in application-specific ways with a resource manager in order to submit requests for work on resources.
attachment: An external file that is included with an Internet message or associated with an item in a SharePoint list.
authentication: The act of proving an identity to a server while providing key material that binds the identity to subsequent communications.
back-end database server: A server that hosts data, configuration settings, and stored procedures that are associated with one or more applications.
base field type: An XML-based schema that defines the type of data, such as formatted text or an integer, that can be entered and stored in a field in a list. Every field in a list is derived from a specific base field type.
base type: An XML-based schema that defines the data and rendering fields that can be used in a list. Every list is derived from a specific base type.
base view identifier: An integer that uniquely identifies a view definition for a list.
blind carbon copy (Bcc) recipient: An addressee on a Message object that is not visible to recipients of the Message object.
blog: A website that contains a series of posts about a subject and is arranged in reverse chronological order. Also referred to as web log.
Boolean: An operation or expression that can be evaluated only as either true or false.
Business Connectivity Services (BCS): A set of services that enables interaction and integration with back-end data in a line-of-business (LOB) system, including external data and related services. BCS includes the Business Data Connectivity (BDC) service.
Business Data Connectivity (BDC): A shared service that stores information about business application data that exists outside a server farm. It can be used to display business data in lists, Web Parts, search results, user profiles, and custom applications. Previously referred to as Business Data Catalog.
calculated field: A user-defined field that can perform calculations by using the contents of other fields.
calendar type: A 2-byte integer value that specifies the type of calendar to use in a specific context.
canonical URL: An absolute URL that identifies a space, tool, or component the same way on any device.
carbon copy (Cc) recipient: An address on a Message object that is visible to recipients of the Message object but is not necessarily expected to take any action.
cascading style sheet (CSS): An extension to HTML that enables authors and users of HTML documents to attach style sheets to those documents, as described in [CSS-LEVEL1] and [CSS-LEVEL2]. A style sheet includes typographical information about the appearance of a page, including the font for text on the page.
change log: A log of changes, such as add and delete, that are made to objects that are stored on a back-end database server. Applications can use this information to identify changes that occurred on those objects.
change token: A serialized token that can be used to determine whether changes occurred in the system. It can also be used to deserialize packages in the correct sequence during import or restore operations.
check out: The process of retrieving a writable copy of a file or project from a source repository. This locks the file for editing to prevent other users from overwriting or editing it inadvertently.
checked out: A publishing level that indicates that a document has been created and locked for exclusive editing by a user in a version control system.
child: An object that is immediately below the current object in a hierarchy.
claims provider: A software component or service that can be used to issue a claim during sign-in operations and to display, resolve, and provide search capabilities for claims in a card selector.
Collaborative Application Markup Language (CAML): An XML-based language that is used to describe various elements, such as queries and views, in sites that are based on SharePoint Products and Technologies.
collation: A set of rules that determines how data is compared, ordered, and presented.
color scheme: A table of color values that enables colors to be referenced by an index value in the table instead of a color value. See also color palette.
comment: An annotation that is associated with a cell, text, or other object to provide context-specific information or reviewer feedback.
computed field: A field that can perform data manipulation and display functions by using the contents of other fields.
configuration database: A database that is stored on a back-end database server and contains both persisted objects and site collection metadata for lookup purposes.
content database: A database that is stored on a back-end database server and contains stored procedures, site collections, and the contents of those site collections.
content type: A named and uniquely identifiable collection of settings and fields that store metadata for individual items in a SharePoint list. One or more content types can be associated with a list, which restricts the contents to items of those types.
content type group: A named category of content types that is used to organize content types of a similar purpose.
content type identifier: A unique identifier that is assigned to a content type.
content type order: The sequence in which content types are displayed.
Coordinated Universal Time (UTC): A high-precision atomic time standard that approximately tracks Universal Time (UT). It is the basis for legal, civil time all over the Earth. Time zones around the world are expressed as positive and negative offsets from UTC. In this role, it is also referred to as Zulu time (Z) and Greenwich Mean Time (GMT). In these specifications, all references to UTC refer to the time at UTC-0 (or GMT).
crawl: The process of traversing a URL space to acquire items to record in a search catalog.
crawler: A process that browses and indexes content from a content source.
creator: The user who creates protected content.
CSOM array: An ordered collection of values that can be used in an XML request or JSON response text. The values are identified by their position and their position is determined by a zero-based integer index.
CSOM binary: An array of 8-bit, unsigned integers that can be used in an XML request or as a string in JSON response text.
CSOM Boolean: A Boolean value that can be used in an XML request or JSON response text. A CSOM Boolean value is either "true" or "false".
CSOM DateTime: An Int64 value that represents the number of 100-nanosecond time intervals that have elapsed since 12:00:00, January 1, 0001. It can be used in an XML request or as a string in JSON response text. The value can represent time intervals through 23:59:59.9999999, December 31, 9999. It can also specify whether a local, UTC, or no time zone applies.
CSOM dictionary: An object that contains an unordered collection of key/value pairs that can be used in an XML request or JSON response text. Each key in a CSOM dictionary has a unique name.
CSOM Double: A 64-bit, double-precision, floating-point value, which is the DOUBLE type described in [MS-DTYP], that can be used in an XML request or as a number in JSON response text. The range of CSOM Double values is from "-1.79769313486232e308" to "1.79769313486232e308".
CSOM error: An object that contains information about an error that occurred on a protocol server when processing a request.
CSOM expando field: A field that stores data for an instance of a CSOM Object and is not defined explicitly in the corresponding CSOM Object type.
CSOM GUID: A GUID, as described in [MS-DTYP], that can be used in an XML request or as a string in JSON response text.
CSOM Int16: A 16-bit, signed integer value, which is the INT16 type described in [MS-DTYP], that can be used in an XML request or as a number in JSON response text. The range of CSOM Int16 values is from "-32768" to "32767".
CSOM Int32: A 32-bit, signed integer value, which is the INT32 type described in [MS-DTYP], that can be used in an XML request or as a number in JSON response text. The range of CSOM Int32 values is from "-2147483648" to "2147483647".
CSOM Int64: A 64-bit, signed integer value, which is the INT64 type described in [MS-DTYP], that can be used in an XML request or as a number in JSON response text. The range of CSOM Int64 values is from "-9223372036854775808" to "9223372036854775807".
CSOM Object: An object that contains a set of members, which are named values and methods. It has a Unicode string value, which is referred to as a CSOM type name, that identifies its type.
CSOM Stream: A series of bytes that is used to transfer data and that supports reading, writing, and seeking.
CSOM String: A representation of text as a series of Unicode characters. It can be used in an XML request or JSON response text.
CSOM UInt32: A 32-bit, unsigned integer value, which is the UINT32 type described in [MS-DTYP], that can be used in an XML request or as a number in JSON response text. The range of CSOM UInt32 values is from "0" to "4294967295".
CSOM UInt64: A 64-bit, unsigned integer value, which is the UINT64 type described in [MS-DTYP], that can be used in an XML request or as a number in JSON response text. The range of CSOM UInt64 values is from "0" to "18446744073709551615".
culture name: A part of a language identification tagging system, as described in [RFC1766]. Culture names adhere to the format "<languagecode2>-<country/regioncode2>." If a two-letter language code is not available, a three-letter code that is derived from [ISO-639] is used.
current user: The user who is authenticated during processing operations on a front-end web server or a back-end database server.
current version: The latest version of a document that is available to a user, based on the permissions of the user and the publishing level of the document.
custom action: An extension to the user interface, such as a button on a toolbar or a link on a site settings page.
custom list: A user-defined list or enumeration that can be used to sort data in a worksheet.
data connection library: A SharePoint library that contains a collection of universal data connection (.udcx) and Office data connection (.odc) files.
data source: A database, web service, disk, file, or other collection of information from which data is queried or submitted. Supported data sources vary based on application and data provider.
data validation: The process of testing the accuracy of data; a set of rules that specify the type and range of data that users can enter.
data validation criteria: See data validation.
datasheet: A worksheet window that contains the source data for a Microsoft Graph chart object.
datetime: A data type that represents the date and time when a document can be normalized and indexed as a numeric value by a search application. The range and degree of granularity varies according to search application and implementation.
declarative workflow: A workflow that is created with XAML (Extensible Application Markup Language) files and does not require precompiled code to run.
default list view: The view of a SharePoint list that the owner of the list selected to appear when users browse to the list without specifying a view.
default mobile list view: The view of a SharePoint list that the owner of the list selected to appear when users browse to the list by using a mobile device and without specifying a view.
default scalar property set: A set of properties that are retrieved by default for an object. The properties map to fields in a storage schema.
default view: The layout and organization of a document or list that appears automatically when users open that document or display that list.
dependent lookup field: A lookup field that displays additional data for an item that is returned by a primary lookup field. See also primary lookup field.
designer: A visual design surface for adding and arranging controls on a user form and writing code for those controls.
dictionary: A collection of key/value pairs. Each pair consists of a unique key and an associated value. Values in the dictionary are retrieved by providing a key for which the dictionary returns the associated value.
discussion board: A list in which users can read, post, and reply to messages from other users who are members of the same discussion board.
discussion item: A remark or response that is posted to an online discussion forum such as a newsgroup, SharePoint list, or electronic bulletin board.
display form: A form that is used to display a list item.
display name: A text string that is used to identify a principal or other object in the user interface. Also referred to as title.
document: An object in a content database such as a file, folder, list, or site (2). Each object is identified by a URI.
document identifier: A GUID that identifies a document.
document library: A type of list that is a container for documents and folders.
document template: (1) A file that serves as the basis for new documents.
(2) A file that contains predefined formatting, layout, text, or graphics and that serves as the basis for new documents with a similar design or purpose.
domain name: The name given by an administrator to a collection of networked computers that share a common directory. Part of the domain naming service naming structure, domain names consist of a sequence of name labels separated by periods.
draft: A version of a document or list item that does not have a publishing level of "Published" or "Checked Out".
edit form: A form that enables users to edit a list item.
editor: The user who last modified an item or document in a SharePoint list.
email address: A string that identifies a user and enables the user to receive Internet messages.
empty GUID: A 128-bit, 16-byte identification number that is represented by all zeros.
End User License Agreement (EULA): A textual description of the terms that a user or administrator accepts before an update is installed. Each EULA is identified by a GUID, and each update revision might be associated with a EULA.
endpoint: A client that is on a network and is requesting access to a network access server (NAS).
entity: An instance of an EntityType element that has a unique identity and an independent existence. An entity is an operational unit of consistency.
EntityInstance: A set of Field (3) values that have a unique identity that represents a specific instance of an Entity, and are stored in a line-of-business (LOB) system.
event: (1) Any significant occurrence in a system or an application that requires users to be notified or an entry to be added to a log.
(2) An action or occurrence to which an application might respond. Examples include state changes, data transfers, key presses, and mouse movements.
event receiver: A structured modular component that enables built-in or user-defined managed code classes to act upon objects, such as list items, lists, or content types, when specific triggering actions occur.
exclusive lock: A condition in which one protocol client or protocol server can read or write data, but no transaction can acquire a shared lock on the data until the exclusive lock is released.
Extensible Stylesheet Language (XSL): An XML vocabulary that is used to transform XML data to another form, such as HTML, by means of a style sheet that defines presentation rules.
external content type: A type of DataClass object that is stored in a line-of-business (LOB) system and whose instances have a persistent EntityInstanceId. Also referred to as Entity.
external list: A container that is within a SharePoint site and that references a set of EntityInstances that are sourced from a line-of-business (LOB) system. It has a customizable schema that is composed of one or more Fields (3).
farm: A group of computers that work together as a single system to help ensure that applications and resources are available. Also referred to as server farm.
feature: A package of SharePoint elements that can be activated or deactivated for a specific feature scope.
feature identifier: A GUID that identifies a feature.
feature scope: The scope at which a feature can be activated.
field: (1) An element or attribute in a data source that can contain data.
(2) A container for metadata within a SharePoint list and associated list items.
(3) The data elements that constitute an Entity in a line-of-business (LOB) system.
field definition: The definition of a field in the Collaborative Application Markup Language (CAML).
field group: A named collection of related fields.
field identifier: A GUID that is used to identify a field.
field internal name: A string that uniquely identifies a field in a content type or a SharePoint list.
field link: A property that specifies a reference from a content type to a field (2) or field definition.
field type: A name that identifies the action or effect that a field has within a document. Examples of field types are Author, Page, Comments, and Date.
file: A single, discrete unit of content.
file extension: The sequence of characters in a file's name between the end of the file's name and the last "." character. Vendors of applications choose such sequences for the applications to uniquely identify files that were created by those applications. This allows file management software to determine which application are to be used to open a file.
file system: A set of data structures for naming, organizing, and storing files in a volume. NTFS, FAT, and FAT32 are examples of file system types.
Finder: A type of MethodInstance that can be called to return a collection of zero or more EntityInstances of a specific Entity. Finder input is defined by the FilterDescriptors that are contained in the Method that contains the Finder.
first-stage Recycle Bin: A container for items that were deleted. Items in this container are visible only to users with the appropriate permission and site collection administrators.
floating-point number: A number that is represented by a mantissa and an exponent according to a given base. The mantissa is typically a value between "0" and "1". To find the value of a floating-point number, the base is raised to the power of the exponent, and the mantissa is multiplied by the result.
folder: A file system construct. File systems organize a volume's data by providing a hierarchy of objects, which are referred to as folders or directories, that contain files and can also contain other folders.
font: An object that defines the graphic design, or formatting, of a collection of numbers, symbols, and letters. A font specifies the style (such as bold and strikeout), size, family (a typeface such as Times New Roman), and other qualities to describe how the collection is drawn.
font scheme: A combination of complementary fonts in a theme.
form: A structured document with controls and spaces that are reserved for entering and displaying information. Forms can contain special coding for actions such as submitting and querying data.
form digest: An object that is inserted into a page and is used by a protocol server to validate client requests. The validation is specific to a user, site, and time period.
form library: A type of document library that is optimized for storing and displaying data in XML-based forms.
form template (.xsn) file: A cabinet (.cab) file with an .xsn file name extension that contains the files that comprise a form template.
full URL: A string of characters in a standardized format that identifies a document or resource on the World Wide Web.
gallery: A library that is used to store a collection of site resources, such as Web Parts, list templates, and site templates.
globally unique identifier (GUID): A term used interchangeably with universally unique identifier (UUID) in Microsoft protocol technical documents (TDs). Interchanging the usage of these terms does not imply or require a specific algorithm or mechanism to generate the value. Specifically, the use of this term does not imply or require that the algorithms described in [RFC4122] or [C706] must be used for generating the GUID. See also universally unique identifier (UUID).
group: A named collection of users who share similar access permissions or roles.
hidden: A condition of an object that prevents it from being displayed in rendered output.
historical version: Any version of a document or list item that is not one of the current versions. Depending on configuration settings, historical versions can be retained in a back-end database server, and might not be visible to specific users.
host name: The name of a physical server, as described in [RFC952].
HTTP method: In an HTTP message, a token that specifies the method to be performed on the resource that is identified by the Request-URI, as described in [RFC2616].
HTTP referer: A string in an HTTP request-header field that identifies the address of the resource that is making the current request, as described in [RFC2616].
hyperlink: A relationship between two anchors, as described in [RFC1866].
Hypertext Markup Language (HTML): An application of the Standard Generalized Markup Language (SGML) that uses tags to mark elements in a document, as described in [HTML].
Hypertext Transfer Protocol (HTTP): An application-level protocol for distributed, collaborative, hypermedia information systems (text, graphic images, sound, video, and other multimedia files) on the World Wide Web.
icon: A graphical image used to supplement alphanumeric text in the visual identification of an object on a computer monitor. Icons are typically small, relative to the size of the area on which they are displayed.
image: A rectangular grid of pixels that has a definite height and a definite width and that can be displayed in a report.
indexed field: A field that stores values in a separate indexed table.
Information Rights Management (IRM): A technology that provides persistent protection to digital data by using encryption, certificates, and authentication. Authorized recipients or users acquire a license to gain access to the protected files according to the rights or business rules that are set by the content owner.
Input Method Editor (IME): An application that is used to enter characters in written Asian languages by using a standard 101-key keyboard. An IME consists of both an engine that converts keystrokes into phonetic and ideographic characters and a dictionary of commonly used ideographic words.
item: A unit of content that can be indexed and searched by a search application.
item identifier: An integer that uniquely identifies an item in a SharePoint list.
key value pair (KVP): A set of two linked data items: a key that is an identifier for some data item, and a value that is a value associated with the data item for the identifier represented by the key.
language code identifier (LCID): A 32-bit number that identifies the user interface human language dialect or variation that is supported by an application or a client computer.
leaf name: The segment of a URL that follows the last slash. If the resource is a directory, the leaf name can be an empty string.
line-of-business (LOB) system: A software system that is used to store business data and can also contain business rules and business logic that support business processes.
link: An attribute value that refers to a directory object and whose Attribute-Schema object specifies an even value for the linkId attribute. Also referred to as forward link.
link bar: A non-hierarchical, user-defined collection of graphical or text buttons that represent hyperlinks to pages within the same website and external sites.
list: A container within a SharePoint site that stores list items. A list has a customizable schema that is composed of one or more fields.
list folder: A folder that is contained within a SharePoint list. A list folder can contain documents or list items, and it retains the characteristics of other items in the list, such as a customizable schema.
list form: A page that enables users to create, view, or edit an item in a list.
list identifier: A GUID that is used to identify a list in a site collection.
list item: An individual entry within a SharePoint list. Each list item has a schema that maps to fields in the list that contains the item, depending on the content type of the item.
list item attachment: A file that is contained within a list item and is stored in a folder in the list with the segment "Attachments".
list item identifier: See item identifier.
list schema: The Collaborative Application Markup Language (CAML) schema of a list.
list server template: A value that identifies the template that is used for a SharePoint list.
list template: An XML-based definition of list settings, including fields and views, and optionally list items. List templates are stored in .stp files in the content database.
list view: A named collection of settings for querying and displaying items in a SharePoint list. There are two types of views: Personal, which can be used only by the user who created the view; and Public, which can be used by all users who have permission to access to the site.
list view page: A Web Parts Page that displays a view of a SharePoint list.
LobSystemInstance: A type of MetadataObject that represents a specific deployed instance of a line-of-business (LOB) system, as represented by a LobSystem. LobSystemInstances are contained by LobSystems. LobSystemInstance Properties describe how to connect to an instance of the LobSystem that contains them by providing information such as the server name, connection string, and authentication mode.
locale: A collection of rules and data that are specific to a language and a geographical area. A locale can include information about sorting rules, date and time formatting, numeric and monetary conventions, and character classification.
locked: The condition of a cell, worksheet, or other object that restricts edits or modifications to it by users.
login name: A string that is used to identify a user or entity to an operating system, directory service, or distributed system. For example, in Windows-integrated authentication, a login name uses the form "DOMAIN\username".
lookup field: A field of the Lookup type that enables users to select an item from another data source.
major version: An iteration of a software component, document, or list item that is ready for a larger group to see, or has changed significantly from the previous major version. For an item on a SharePoint site, the minor version is always "0" (zero) for a major version.
marketplace billing market: A specifier that identifies the region of the credit card used to buy apps.
marketplace content market: A collection of metadata associated with each individual app that contains information such as the region and locale of the app.
marketplace deployment identifier: The identifier of the location to which app licenses are sold.
marketplace license: The proof of an app purchase that defines the usage pattern that is allowed for the app.
marketplace license token: An implementation-specific identifier used to serialize a marketplace license.
master page: An ASP.NET file that has a predefined layout that can include static text, HTML elements, and server controls.
Meeting Workspace site: A SharePoint site that is based on a Meeting Workspace site template and has a template ID value of "2". A Meeting Workspace site is used for planning, posting, and working together on meeting materials.
member: A user in the Members group of a site.
membership: The state or status of being a member of a member group. A membership contains additional metadata such as the privacy level that is associated with the membership.
message body: The main message text of an email message. A few properties of a Message object represent its message body, with one property containing the text itself and others defining its code page and its relationship to alternative body formats.
MetadataCatalog: A MetadataObject that represents a Metadata partition.
MethodInstance: A type of MetadataObject that associates a normalized or stereotypical semantic with a Method that represents a native API in a line-of-business (LOB) system. MethodInstances identify which part of the data that is returned by a Method is relevant for the semantic by defining a ReturnTypeDescriptor. MethodInstances are contained by Methods.
MIME type: A method that is used by protocol clients to associate files of a certain type with applications that can open or access files of that type.
minor version: An iteration of a software component, document, or list item that is in progress or has changed only slightly from the previous version. For an item on a SharePoint site, the minor version number is never "0" (zero) and is incremented for each new version of an item, unless a major version is explicitly published. When minor versioning is disabled on a SharePoint site, only major version numbers are incremented, and the minor version is always "0" (zero).
mobile device: A small computing device that is easily portable and can be used in various environments.
mobile list view: A view of a SharePoint list that can be accessed by using a mobile device.
moderation status: A content approval status that indicates whether a list item was approved by a moderator.
Mount: To move physical media from a library slot to a drive.
mount point: See mounted folder.
mounted folder: A file system directory that contains a linked path to a second volume. A user can link a path on one volume to another. For example, given two volumes C: and D:, a user can create a directory or folder C:\mountD and link that directory with volume D:. The path C:\MountD can then be used to access the root folder of volume D:.
navigation node: An element in the navigational structure of a site. The element is a link or a series of links to a specific page in the site.
new form: A form that enables users to create a list item.
notification: A process in which a subscribing Session Initiation Protocol (SIP) client is notified of the state of a subscribed resource by sending a NOTIFY message to the subscriber.
OAuth: The OAuth 2.0 authorization framework [RFC6749].
object: (1) A set of attributes, each with its associated values. Two attributes of an object have special significance: an identifying attribute and a parent-identifying attribute. An identifying attribute is a designated single-valued attribute that appears on every object; the value of this attribute identifies the object. For the set of objects in a replica, the values of the identifying attribute are distinct. A parent-identifying attribute is a designated single-valued attribute that appears on every object; the value of this attribute identifies the object's parent. That is, this attribute contains the value of the parent's identifying attribute, or a reserved value identifying no object. For the set of objects in a replica, the values of this parent-identifying attribute define a tree with objects as vertices and child-parent references as directed edges with the child as an edge's tail and the parent as an edge's head. Note that an object is a value, not a variable; a replica is a variable. The process of adding, modifying, or deleting an object in a replica replaces the entire value of the replica with a new value. As the word replica suggests, it is often the case that two replicas contain "the same objects". In this usage, objects in two replicas are considered the same if they have the same value of the identifying attribute and if there is a process in place (replication) to converge the values of the remaining attributes. When the members of a set of replicas are considered to be the same, it is common to say "an object" as shorthand referring to the set of corresponding objects in the replicas.
(2) In COM, a software entity that implements the IUnknown interface and zero or more additional interfaces that may be obtained from each other using the IUnknown interface. A COM object can be exposed to remote clients via the DCOM protocol, in which case it is also a DCOM object.
Office Add-in: A cloud-enabled app that integrates rich, scenario-focused content and services into an Office application or equivalent protocol client.
organization access link: An implementation of tokenized sharing link that can grant a signed-in user explicit access to content, such as a document or folder, when using the specific tokenized sharing link, so that they can directly access the content in future requests.
owner: A security principal who has the requisite permission to manage a security group.
page type: An integer that specifies the type of a page.
paged view: A view that supports one or more visual pages. A paged view is used to break large sets of data into smaller sets for increased performance and manageability.
parent list: A list that contains a list item or list folder.
parent site: The site that is above the current site in the hierarchy of the site collection.
permission: A rule that is associated with an object and that regulates which users can gain access to the object and in what manner. See also rights.
permission level: A set of permissions that can be granted to principals or SharePoint groups on an entity such as a site, list, folder, item, or document.
personal view: A view of a list that is created by a user for personal use. The view is unavailable to other users.
personalization data: Customized data that is stored for a set of Web Parts. The data can be shared by all users or be specific to an individual user.
personalization scope: A mode of the Web Part Manager that indicates whether the available data is shared by all users or specific to an individual user.
personalized Web Parts: A Web Part that has been modified by a user for personal use. The view of the Web Part is unavailable to other users.
picture library: A type of document library that is optimized for storing digital pictures or graphics.
policy: A set of rules that governs all interactions with an object such as a document or item.
policy tip: A message that is displayed in the client user interface to inform the user that an email does not comply with an email policy configured on the server.
presence: A setting for the User field that determines whether instant-messaging status information appears with user names in that field.
primary lookup field: A lookup field that returns all of the information that is needed to support lookup operations from one list to another. See also dependent lookup field.
principal: An authenticated entity that initiates a message or channel in a distributed system.
ProgID: An identifier that is used by the Windows registry to uniquely identify an object and is in the form OLEServerName.ObjectName, for example, "Excel.Sheet" or "PowerPoint.Slide."
public view: A view of a list that is available to all users who have permission to access that list.
published: A condition of portions of a workbook that are marked as being available to the user when that workbook is processed by a protocol server.
publishing level: An integer that is assigned to a document to indicate the publishing status of that version of the document.
query: A formalized instruction to a data source to either extract data or perform a specified action. A query can be in the form of a query expression, a method-based query, or a combination of the two. The data source can be in different forms, such as a relational database, XML document, or in-memory object. See also search query.
Quick Launch: A collection of links to lists and pages in a SharePoint site. By default, it appears on the side of all pages, except site administration pages, in the site.
reading order: The positioning of characters in words and the positioning of words in sentences. This can be left-to-right or right-to-left.
recycle: A process in which SMP releases a Session object so that the session identifier (SID) in use is made available again for a new session.
Recycle Bin: The location where deleted files are stored until they are either restored, if they were deleted erroneously, or destroyed permanently.
Recycle Bin item: An item that was deleted and appears in the Recycle Bin. Items in the Recycle Bin can include a document, a version of a document, a list item, a list, a folder, a folder containing lists, an attachment to a list item, or a version of a list item.
recycling: To permanently disable the creation of new component instances in an instance container.
reference: A means by which cells, objects, and chart elements can be referenced in a formula.
regional settings: See locale settings.
relationship behavior constraint: A setting that defines any dependent relationships, such as cascading or restrict behaviors, between list items.
relationship delete behavior: An 8-bit integer that specifies how to delete a list item that has related child items. It can be a cascading operation, which deletes all related child items when the parent item is deleted, or a restrict operation, which indicates that a parent item can be deleted only after all related child items are deleted.
relationship lookup field: A lookup field in a back-end database server that defines a relationship between two SharePoint lists.
resource folder: A folder that contains images, templates, and other resource files for a content type.
rich text: Text that is formatted in the Rich Text Format, as described in [MSFT-RTF].
rights: Tasks that a user is permitted to perform on a computer, site, domain, or other system resource. See also permission.
role: A symbolic name that defines a class of users for a set of components. A role defines which users can call interfaces on a component.
role assignment: An association between a principal or a site group and a role definition.
role definition: A named set of permissions for a SharePoint site. See also permission level.
root element: The top-level element in an XML document. It contains all other elements and is not contained by any other element, as described in [XML].
root folder: The folder at the top of a hierarchy of folders in a list.
schema version: An integer value that represents the version number of the schema for a deployment package.
second-stage Recycle Bin: A container for items that were deleted from a first-stage Recycle Bin. Items in a second-stage Recycle Bin are visible only to site collection administrators.
securable object: An object that can have unique security permissions associated with it.
security group: A named group of principals on a SharePoint site.
security scope: A tree structure of objects in which every object has the same security settings as the root.
security trimming: The process of filtering search results by checking the access control list (ACL) for a resource and displaying only those resources that a user has permission to view.
server-relative URL: A relative URL that does not specify a scheme or host, and assumes a base URI of the root of the host, as described in [RFC3986].
Session Initiation Protocol (SIP): An application-layer control (signaling) protocol for creating, modifying, and terminating sessions with one or more participants. SIP is defined in [RFC3261].
shared lock: A condition in which multiple protocol clients or protocol servers can read or write data concurrently, but no transaction can acquire an exclusive lock on the data until all of the shared locks have been released.
site: (1) A group of related webpages that is hosted by a server on the World Wide Web or an intranet. Each website has its own entry points, metadata, administration settings, and workflows. Also referred to as web site.
(2) A group of related pages and data within a SharePoint site collection. The structure and content of a site is based on a site definition. Also referred to as SharePoint site and web site.
site collection: A set of websites that are in the same content database, have the same owner, and share administration settings. A site collection can be identified by a GUID or the URL of the top-level site for the site collection. Each site collection contains a top-level site, can contain one or more subsites, and can have a shared navigational structure.
site collection administrator: A user who has administrative permissions for a site collection.
site collection group: A named collection of users and domain groups that can be managed for a site collection or site. A group can be used to assign permission levels, send email messages, and indicate site membership for multiple users simultaneously.
site collection quota: An option for a site collection that enables administrators to set levels for maximum storage allowed, maximum number of users allowed, and warnings that are associated with the maximum levels.
site content type: A named and uniquely identifiable collection of settings and fields that store metadata for lists within individual sites.
site definition: A family of site definition configurations. Each site definition specifies a name and contains a list of associated site definition configurations.
site definition configuration: An XML-based definition of lists, features, modules, and other data that collectively define a type of SharePoint site. Site definition configurations are stored in the ONET.xml file.
site identifier: A GUID that is used to identify a site in a site collection.
site solution: A deployable, reusable package that contains a set of features, site definitions, and assemblies that apply to sites, and can be enabled or disabled individually.
site subscription: A logical grouping of site collections that share a common set of features and service data.
site template: An XML-based definition of site settings, including formatting, lists, views, and elements such as text, graphics, page layout, and styles. Site templates are stored in .stp files in the content database.
site-relative URL: A URL that is relative to the site that contains a resource and does not begin with a leading slash (/).
SOAP: A lightweight protocol for exchanging structured information in a decentralized, distributed environment. SOAP uses XML technologies to define an extensible messaging framework, which provides a message construct that can be exchanged over a variety of underlying protocols. The framework has been designed to be independent of any particular programming model and other implementation-specific semantics. SOAP 1.2 supersedes SOAP 1.1. See [SOAP1.2-1/2003].
SpecificFinder: A type of MethodInstance that can be called to return a specific EntityInstance of a specific Entity given its EntityInstanceId. SpecificFinder input is defined and ordered by the Identifiers that are associated with the Entity that is associated with the Method that is associated with the SpecificFinder.
static CSOM method: A class method that is accessed through the type name rather than an instance of the class.
Status-Code: A 3-digit integer result code in an HTTP response message, as described in [RFC2616].
stream: An element of a compound file, as described in [MS-CFB]. A stream contains a sequence of bytes that can be read from or written to by an application, and they can exist only in storages.
strong name: A name that consists of the simple text name, version number, and culture information of an assembly, strengthened by a public key and a digital signature that is generated over the assembly.
subscription: The result of a SUBSCRIBE request from a Session Initiation Protocol (SIP) element.
subsite: A complete website that is stored in a named subdirectory of another website. The parent website can be the top-level site of a site collection or another subsite. Also referred to as subweb.
survey list: A list that is preconfigured and optimized for conducting surveys and compiling survey results into graphical views.
task: A component of an action that defines the work that actors need to do within a workflow system. An action can have zero or more tasks that are each assigned to different targets. There is a one-to-one correlation between tasks and targets.
taxonomy navigation: A hierarchy of navigation menus that represents the navigation menus in terms and term sets and are independent of where their underlying objects, such as pages, are located.
template: A file that contains pre-defined formatting including layout, text and graphics. It serves as the basis for new documents that have a similar look or purpose. See also form template (Microsoft InfoPath) and site template (SharePoint Products and Technologies).
theme: A set of unified design elements, such as colors, fonts, graphics, and styles, that define the appearance of a website, document, or data visualization.
thicket supporting file: A file that contains a graphic element, a picture, or other media that is referenced by the thicket main file and is stored in the thicket folder.
time zone: A geographical area that observes the same local time. The local time has a positive, zero, or negative offset from Coordinated Universal Time (UTC). The offset can be different during standard time and daylight saving time.
tokenized sharing link: A specialized URL where a unique server generated opaque string value for a resource is embedded within the path or as a parameter, for the purposes of granting access whenever the URL is used to access the content. Depending on the supported abilities of the server, a tokenized sharing link can potentially behave like an anonymous access link, an organization access link, or with other behaviors as defined by the implementor.
toolbar: A row, column, or block of controls that represent tasks or commands within an application. A toolbar can be either a menu toolbar, which provides access to menu commands, or a basic toolbar, which contains buttons that provide shortcuts to tasks that are frequently accessed from menus.
tooltip: A window displaying text that is created when the mouse is moved over a window or notification icon.
top-level site: The first site in a site collection. All other sites within a site collection are child sites of the top-level site. The URL of the top-level site is also the URL of the site collection.
TypeDescriptor: A type of MetadataObject that describes a subset of the structure of a Parameter of a Method of the native API of a line-of-business (LOB) system. A TypeDescriptor can contain TypeDescriptors to form hierarchies that describe Parameters representing complex types, where the leaf TypeDescriptors describe simple or primitive types. A root TypeDescriptor, together with DefaultValues for leaf TypeDescriptors can be used to instantiate an instance of a Parameter value to send to a LOB system to execute a Method.
uncustomized: A condition of a document whose content is stored in a location other than the content database. If a document is uncustomized, the front-end web server determines the location of the content by using the SetupPath value for the document. Also referred to as ghosted.
Uniform Resource Identifier (URI): A string that identifies a resource. The URI is an addressing mechanism defined in Internet Engineering Task Force (IETF) Uniform Resource Identifier (URI): Generic Syntax [RFC3986].
Uniform Resource Locator (URL): A string of characters in a standardized format that identifies a document or resource on the World Wide Web. The format is as specified in [RFC1738].
unique column constraint: A property of a field that requires all of the values in that field to be unique.
Updater: A type of MethodInstance that can be called to update an EntityInstance identified by a specified EntityInstanceId. The set of Fields (3) that is required to update the EntityInstance is referred to as the Updater View.
upgrade evaluation site collection: A copy of the current site collection, used to evaluate the functionality of a site collection after it is upgraded.
URL encode: The process of encoding characters that have reserved meanings for a Uniform Resource Locator (URL), as described in [RFC1738].
user: (1) A person who employs a web browser requestor to access a WS resource.
(2) The real person who has a member account. The user is authenticated by being asked to prove knowledge of the secret password associated with the user name.
user custom action: An extension to the user interface, such as a button on a toolbar or a link on a site settings page, that is submitted by a user of a site collection. Unlike a custom action, the definition of a user custom action is stored in a back-end database server.
user display name: A user profile property that contains the preferred name of a user. See also display name.
user information list: A list that contains items, each of which represents a security principal in a site collection. Each site collection has only one such list and it resides in the top-level site of the site collection.
UTC (Coordinated Universal Time): A high-precision atomic time standard that approximately tracks Universal Time (UT). It is the basis for legal, civil time all over the Earth. Time zones around the world are expressed as positive and negative offsets from UTC. In this role, it is also referred to as Zulu time (Z) and Greenwich Mean Time (GMT). In these specifications, all references to UTC refer to the time at UTC–0 (or GMT).
value: A data element associated with a key.
version: See displayed version, historical version, major version, and minor version.
view: See form view (Microsoft InfoPath), list view (SharePoint Products and Technologies), or View (Microsoft Business Connectivity Services).
view identifier: A GUID that is used to uniquely identify a view.
view style: A pre-defined, named collection of settings that specify how to lay out data in a list view.
visual upgrade: A feature that enables a protocol server to display an earlier version of a user interface to support backward compatibility with existing solutions.
web application: A container in a configuration database that stores administrative settings and entry-point URLs for site collections.
web discussion: A component and add-in that enables users to enter comments about documents and pages without modifying the actual content of those documents or pages.
web discussion comment: An individual comment that is added to a web discussion.
Web Distributed Authoring and Versioning Protocol (WebDAV): The Web Distributed Authoring and Versioning Protocol, as described in [RFC2518] or [RFC4918].
Web Part: A reusable component that contains or generates web-based content such as XML, HTML, and scripting code. It has a standard property schema and displays that content in a cohesive unit on a webpage. See also Web Parts Page.
Web Part identifier: A GUID that identifies a Web Part.
Web Part Page: An ASP.NET webpage that includes Web Part controls that enable users to customize the page, such as specifying which information to display. Referred to as Web Parts Page in Microsoft SharePoint Foundation 2010.
Web Part zone: A structured HTML section of a Web Parts Page that contains zero or more Web Parts and can be configured to control the organization and format of those Web Parts.
Web Part zone index: An integer that specifies the relative position of a Web Part in a Web Part zone. Web Parts are positioned from the smallest to the largest zone index. If two or more Web Parts have the same zone index they are positioned adjacent to each other in an undefined order.
website: A group of related pages and data within a SharePoint site collection. The structure and content of a site is based on a site definition. Also referred to as SharePoint site and site.
Welcome page: A page, such as default.aspx, that can be specified as the default redirect target when users browse to a URL without specifying a leaf name.
workflow: A structured modular component that enables the automated movement of documents or items through a specific sequence of actions or tasks that are related to built-in or user-defined business processes.
workflow association: An association of a workflow template to a specific list or content type.
workflow history list: A list that stores the history of actions or tasks for a business process.
workflow identifier: A GUID that is used to identify a workflow.
workflow initiation form: An implementation-specific file, typically an ASPX page, that is a part of a workflow. It contains fields and other elements that can be used to initiate a process for a list item, based on the rules and settings in a workflow template that is associated with the list that contains the item.
workflow instance: An instance of a workflow association that performs on a list item the process that is defined in a workflow template.
workflow task: An action or task in a sequence that is related to a built-in or user-defined business process.
workflow task list: A list that stores the sequence of actions or tasks for a business process.
workflow template: A definition of operations, the sequence of operations, constraints, and timing for a specific process.
XML: The Extensible Markup Language, as described in [XML1.0].
XML document: A document object that is well formed, as described in [XML10/5], and might be valid. An XML document has a logical structure that is composed of declarations, elements, comments, character references, and processing instructions. It also has a physical structure that is composed of entities, starting with the root, or document, entity.
XML element: An XML structure that typically consists of a start tag, an end tag, and the information between those tags. Elements can have attributes and can contain other elements.
XML fragment: Lines of text that adhere to XML tag rules, as described in [XML], but do not have a Document Type Definition (DTD) or schema, processing instructions, or any other header information.
XML schema: A description of a type of XML document that is typically expressed in terms of constraints on the structure and content of documents of that type, in addition to the basic syntax constraints that are imposed by XML itself. An XML schema provides a view of a document type at a relatively high level of abstraction.
MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used as defined in [RFC2119]. All statements of optional behavior use either MAY, SHOULD, or SHOULD NOT.