1.1 Glossary

This document uses the following terms:

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/.

anonymous user: A user who presents no credentials when identifying himself or herself. The process for determining an anonymous user can differ based on the authentication protocol, and the documentation for the relevant authentication protocol should be consulted.

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.

assembly name: The name of a collection of one or more files that is versioned and deployed as a unit. See also assembly.

authenticated user: A built-in security group specified in [MS-WSO] whose members include all users that can be authenticated by a computer.

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.

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.

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.

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.

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 library: A type of list that is a container for documents and folders.

event: An action or occurrence to which an application might respond. Examples include state changes, data transfers, key presses, and mouse movements.

event handler: A software routine that executes in response to an event.

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.

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 receiver: A server-side code routine that is called when a feature is activated, deactivated, installed, uninstalled, or upgraded on a computer, server farm, or server cluster.

feature scope: The scope at which a feature can be activated.

field: A container for metadata within a SharePoint list and associated list items.

form digest validation: A type of security validation that helps prevent an attack wherein users are tricked into posting data to a server.

front-end web server: A server that hosts webpages, performs processing tasks, and accepts requests from protocol clients and sends them to the appropriate back-end server for further processing.

full URL: A string of characters in a standardized format that identifies a document or resource on the World Wide Web.

fully qualified class name: A class name that includes namespace information. Use of a fully qualified class name ensures that the class name is treated as unique.

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).

hash: A fixed-size result that is obtained by applying a one-way mathematical function, which is sometimes referred to as a hash algorithm, to an arbitrary amount of data. If the input data changes, the hash also changes. The hash can be used in many operations, including authentication and digital signing.

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].

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.

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.

list: (1) A container within a SharePoint site that stores list items. A list has a customizable schema that is composed of one or more fields.

(2) An organization of a region of cells into a tabular structure in a workbook.

list identifier: A GUID that is used to identify a list (1) 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 (1) with the segment "Attachments".

list item identifier: See item identifier.

list server template: A value that identifies the template that is used for a SharePoint list.

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".

managed code: Code that is executed by the common language runtime (CLR) environment rather than directly by the operating system. Managed code applications gain CLR services, such as automatic garbage collection, runtime type checking, and security support. These services provide uniform behavior that is independent of platform and language.

personal view: A view of a list that is created by a user for personal use. The view is unavailable to other users.

personal Web Part: A Web Part that was added to the personal view of a Web Parts Page and is available only to the user who added it.

public key: One of a pair of keys used in public-key cryptography. The public key is distributed freely and published as part of a digital certificate. For an introduction to this concept, see [CRYPTO] section 1.8 and [IEEE1363] section 3.1.

request identifier: A GUID that is used to identify a specific action or procedure that is sent to a protocol server or a protocol client.

server-activated object (SAO): A server object that is created on demand in response to a client request. See also marshaled server object.

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].

shared view: A view of a list or Web Parts Page that every user who has the appropriate permissions can see.

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 identifier: A GUID that identifies a site collection. In stored procedures, the identifier is typically "@SiteId" or "@WebSiteId". In databases, the identifier is typically "SiteId/tp_SiteId".

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.

SOAP operation: An action that can be performed by a Simple Object Access Protocol (SOAP) service, as described in [SOAP1.1].

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.

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].

user code: Managed code that can be uploaded to a site by a site collection administrator, without approval from the server farm administrator. It cannot access code or data on other site collections.

user identifier: An integer that uniquely identifies a security principal as distinct from all other security principals and site groups within the same site collection.

web application: A container in a configuration database that stores administrative settings and entry-point URLs for site collections.

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 chrome: A set of common user interface elements that frame a Web Part within a given zone. The Web Part chrome includes a border, a title bar, and the icons, title text, and verbs menu that appear within the title bar.

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 property: A configurable characteristic of a Web Part that determines the behavior of the Web Part.

Web Part type identifier: A unique 16-byte value that is assigned to each Web Part type.

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 identifier: A string that identifies a Web Part zone on a Web Parts Page.

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.

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 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.

XML: The Extensible Markup Language, as described in [XML1.0].

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.