This document uses the following terms:
after event: An event whose handler runs only after the action that raised the event is complete. Unlike a before event, an after event handler cannot cancel the action that caused the event. See also before event.
assembly: A collection of one or more files that is versioned and deployed as a unit. An assembly is the primary building block of a .NET Framework application. All managed types and resources are contained within an assembly and are marked either as accessible only within the assembly or as accessible from code in other assemblies. Assemblies also play a key role in security. The code access security system uses information about an assembly to determine the set of permissions that is granted to code in the assembly.
before event: A synchronous event whose handler runs completely before the action that raised the event is finalized. Unlike an after event, a before event handler can cancel the action that caused the event, before that action or related actions are complete. See also after event.
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.
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.
current user: The user who is authenticated during processing operations on a front-end web server or a back-end database server.
Document Information Panel: A pane that displays property information about a Word document, Excel workbook, or PowerPoint presentation that is stored in a library on a SharePoint site. The pane hosts a custom InfoPath form.
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 (1), or content types, when specific triggering actions occur.
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.
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.
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.
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).
(2) An organization of a region of cells into a tabular structure in a workbook.
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.
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.
resource folder: A folder that contains images, templates, and other resource files for a content type.
retention action: An action that occurs on an object, such as a document or site, in response to an event defined by a retention formula in a larger retention policy. Examples of retention actions are delete, move to a different location, and delete previous versions.
retention formula: A logical equation or function that is used to calculate when a retention action occurs on an object, such as a document or content type, as defined by a larger retention policy that applies to that object.
retention schedule: A sequence of stages that defines the retention lifecycle of an object such as a document, list item, list, content type, or site. Each stage consists of an event/action pair that specifies what action to perform on an object before or after that stage.
retention stage: One of a sequence of phases in a retention policy that defines the retention lifecycle of an object such as a document, list item, list, content type, or site. Each stage consists of an event/action pair that specifies what action to perform on an object before or after that stage.
RSS item: An item element in an RSS feed, as described in [RSS2.0].
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].
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.
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.
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.
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.
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].
Uniform Resource Name (URN): A string that identifies a persistent Internet resource, as described in [RFC2141]. A URN can provide a mechanism for locating and retrieving a schema file that defines a specific namespace. Although a URL can provide similar functionality, a URN can refer to more than one URL and is not location-dependent.
view: See form view (Microsoft InfoPath), list view (SharePoint Products and Technologies), or View (Microsoft Business Connectivity Services).
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.
XML namespace prefix: An abbreviated form of an XML namespace, as described in [XML].
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.