1.1 Glossary
The following terms are defined in [MS-GLOS]:
access control list (ACL)
anonymous user
Augmented Backus-Naur Form (ABNF)
code page
globally unique identifier (GUID)
language code identifier (LCID)
NULL GUID
principal
security identifier (SID)
security policy
UTC (Coordinated Universal Time)
UTF-8
XML
The following terms are specific to this document:
alert: (1) An Internet message that is automatically sent to subscribers to notify them when user-defined criteria are met. Alerts are generated automatically when items such as documents, web pages, list items, sites, or other resources on a server are changed. (2) A message that is passed to a protocol client to notify it when specific criteria are met.
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.
attachment: An external file that is included with an Internet message or associated with an item in a SharePoint list.
audit entry: Recorded information about an operation that occurs on an object that is stored on a server.
author: The user who created a list item.
back-end database server (BEDS): A server that hosts data, configuration settings, and stored procedures that are associated with one or more applications.
backward link: A hyperlink between a referenced document and a referencing party. For example, if Document A contains a hyperlink to Document B, then Document B has a backward link to Document A.
Boolean: An operation or expression that can be evaluated only as either true or false.
bot: A structured HTML comment that is processed by the front-end web server when the containing document is opened by or saved to the server. Also referred to as web bot.
build dependency set: A serialized .NET Framework object that represents a set of file dependencies.
CAML: See Collaborative Application Markup Language (CAML).
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.
character set: A mapping between the characters of a written language and the values that are used to represent those characters to a computer.
check in: The process of placing a file or project into a source repository. This releases the lock for editing and enables other users to view the updated file or check out the file. See also check out.
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. See also check in.
checked out: A publishing level that indicates that a document has been created and locked for exclusive editing by a particular user in a version control system.
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 Microsoft® SharePoint® Products and Technologies.
collapse: The process of closing a level in a dimension hierarchy on a PivotTable® report to hide or aggregate lower level details in the data.
collation order: A rule for establishing a sequence for textual information.
content database: A database that is stored on a back-end database server and contains stored procedures, site collections, and the contents of the 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 identifier: A unique identifier that is assigned to a content type.
current user: The authenticated user during processing operations in a front-end web server and 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 extensible user interface component that is defined or deployed as part of a feature.
datetime: A collection of date and time data from January 1, 1753, to December 31, 9999, with an accuracy of one three-hundredth of a second, or 3.33 milliseconds. Values are rounded to increments of .000, .003, or .007 milliseconds and are stored as two 4-byte integers. The first 4 bytes store the number of days before or after the base date, January 1, 1900, which is the system's reference date. Values earlier than January 1, 1753 are not permitted. The other 4 bytes store the time of day represented as the number of milliseconds after midnight. Seconds have a valid range of 0-59.
default view: The layout and organization of a document or list that appears automatically when a user opens that document or displays that list.
directory name: A segment of a store-relative form URL that refers to a directory. A directory name is everything that appears before the last slash in a store-relative form URL.
dirty: The condition of an entity, such as a component or a file, that indicates that the entity or properties of the entity were changed since the entity was last saved.
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.
display name: A text string that is used to identify a principal or other object in the user interface. Also referred to as title.
distribution list: A collection of users, computers, contacts, or other groups that is used only for email distribution, and addressed as a single recipient.
document: An object in a content database such as a file, folder, list, or site. Such objects are identified by a URI.
document flag: A 4-byte unsigned integer bit mask that provides metadata about the document.
document identifier: (1) An integer value that uniquely identifies a crawled item. (2) A GUID that identifies a document. (3) A string that uniquely identifies an item in a search index.
document library: A type of list that is a container for documents and folders.
document stream: A byte stream that is associated with a document, such as the content of a file. Not all documents have document streams.
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.
document version: A copy of a list item that has a version number. A document version can be either a historical version or a current version.
domain group: A container for security and distribution groups. A domain group can also contain other domain groups.
draft: A document version that does not have a publishing level of Published or Checked Out.
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.
email-enabled list: A list that is configured to accept incoming email messages.
event: (1) Any significant occurrence in a system or an application that requires a user 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 host: A site collection, site, list, list item, workflow, feature, or content type that hosts an event receiver.
event receiver: A structured modular component that allows built-in or user-defined managed code classes to act upon objects, such as list items, lists, or content types, whenever specific triggering actions occur.
event sink: A structured, modular component that allows built-in or user-defined classes to act on documents in document libraries whenever specific triggering actions occur. Event sinks are a deprecated, implementation-specific capability of Windows SharePoint Services 2.0. In Windows SharePoint Services 3.0, they are replaced by the capabilities of event receivers.
external security provider: An external object that manages permissions on a site.
feature: A package of Windows SharePoint Services 3.0 elements that can be activated or deactivated for a specific feature scope.
feature identifier: A GUID that identifies a feature.
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) A discrete unit of a record that has a name, a data type, and a value.
field definition: The definition of a field in Collaborative Application Markup Language (CAML) language.
field identifier: A GUID that is used to identify a field.
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 should be used to open a file.
folder: A file system construct. File systems organize data by providing a hierarchy of objects known as folders or directories, which contain files and can also contain other folders.
form: (1) 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.
(2) A document with a set of controls into which users can enter information. Controls on an InfoPath form are bound to groups and fields in the data source of the form. See also bind.
forward link: A forward link is a hyperlink between a referencing document and the referenced party. For example, when document A contains a hyperlink to document B, document A has a forward link to document B.
front-end web server: A server that hosts web pages, 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.
ghosted: The condition of a document whose content is stored in a location other than the content database. If a document is ghosted, the front-end web server determines the location of the content by using the SetupPath value for the document.
group: (1) An element that can contain fields and other groups in the data source for an InfoPath form. Controls that contain other controls, such as repeating tables and sections, are bound to groups. (2) A named collection of users who share similar access permissions or roles. (3) A named collection of quick links, colleagues, or memberships for the purpose of organization. (4) The process of combining like elements into a set in accordance with logical criteria. This is frequently used to combine sets of data from Online Analytical Processing (OLAP) databases or PivotTable® reports.
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.
historical version: Any version of a document that is not one of the current versions. Depending on configuration settings, historical versions can be retained in the back-end database server, and might not be visible to particular users.
home page: On the World Wide Web, a document that serves as a starting point for a set of web pages and other files in a website.
host header: An Internet host and port number that identifies a network resource.
host name: The name of a physical server, as specified in [RFC952].
HTML (HyperText Markup Language): An application of the Standard Generalized Markup Language (SGML) that uses tags to mark elements in a document, as specified in [HTML].
HTTP GET: An HTTP method for retrieving a resource, as specified in [RFC2616].
HTTP HEAD: An HTTP method for retrieving header information for a resource, as specified in [RFC2616].
internal version number: A number that increases monotonically and is used to identify conflicts when saving an item.
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.
leaf name: The part of a store-relative URL that follows the last slash. If the resource is a directory, the leaf name can be an empty string (1).
level: A relative position in a hierarchy of data. A level is frequently used when describing how to navigate a hierarchy in an Online Analytical Processing (OLAP) database or a PivotTable report.
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 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 identifier: See item identifier.
list server template: A value that identifies the template that is used for a 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 template identifier: A GUID that is used to identify a list template.
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 creates them; and Public, which can be used by all users who have access to the site.
locale: A collection of rules and data that are specific to a language and a geographical area. A locale can include information on 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 user edits or modifications.
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".
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 since the previous major version. For an item on a SharePoint site, the minor version is always zero for a major version.
master page: An ASP.NET file that has a predefined layout that can include static text, HTML elements, and server controls.
meeting instance: A collection of data for a meeting that occurs only once or a single occurrence of a meeting that occurs multiple times. The data can be stored in a client application or on a website.
Meeting Workspace site: A SharePoint site that is based on a Meeting Workspace site template and has a template ID of 2. A Meeting Workspace site is used for planning, posting, and working together on meeting materials.
member: (1) A user in the Membersgroup of a site. (2) An identity that belongs to an Office Groove 2007 shared space. (3) See OLAP member.
metadict: A dictionary that has strongly typed values.
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 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 zero.
mobile device: A small computing device that is easily portable and can be used in various environments.
moderation status: A content approval status of an item in a list.
navigation node: An element in the navigation structure of a site. The element is a link, or series of links, to a specific page in the site.
navigation node element identifier: An integer that identifies a navigation node. This value is unique for every navigation node in the navigation structure of a site.
navigation structure: A hierarchical organization of links between related content, such as lists within a site.
owner: A security principal who has the requisite permissions to a security group.
page: A file consisting of HTML that can include references to graphics, scripts, or dynamic content such as Web Parts.
parent site: The site that is above the current site in the hierarchy of the site collection.
path segment: A portion of a URI, as specified in [RFC3986]. See also path component.
permission: A rule that is associated with an object to regulate which users can gain access to the object and in what manner.
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.
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.
published version: The version of a list item that is approved and can be seen by all users. The user interface (UI) version number for a published version is incremented to the next positive major version number and the minor version is zero. See also major version and minor version.
read-only mode: An attribute that indicates that an object cannot be changed or deleted. The object can only be accessed or displayed.
Recycle Bin: The location where deleted files are stored until they are restored, if they are deleted erroneously, or if they are destroyed permanently.
request identifier: A GUID that identifies a given request. It is primarily used for tracking or logging purposes.
result set: A set of records that results from running a stored procedure or query, or applying a filter. The structure and content of the data in a result set varies according to the implementation.
return code: A code that is used to report the outcome of a procedure or to influence subsequent events when a routine or process terminates (returns) and passes control of the system to another routine. For example, a return code can indicate whether an operation was successful.
role: A symbolic name that defines a class of users for a set of components. A role defines which users are allowed to invoke 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.
role identifier: An integer that uniquely identifies a role definition within a site.
root folder: The folder at the top of the hierarchy of folders in a list.
sandboxed solution: A deployable, reusable package that contains a set of features, site definitions, and assemblies that apply to sites, and that can be enabled or disabled individually.
scope identifier: A GUID that uniquely identifies a scope within a site collection.
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 principal: (1) A unique entity that is identifiable through cryptographic means by at least one key. It frequently corresponds to a human user, but also can be a service that offers a resource to other security principals. Also referred to as principal. (2) An identity that can be used to regulate access to resources. A security principal can be a user, a computer, or a group that represents a set of users.
security provider: A Component Object Model (COM) object that provides methods that return custom information about the security of a site.
security role: A defined set of access privileges. The security role that is assigned to a user determines the tasks that a user can perform and which parts of the user interface a user can view.
security scope: A tree structure of objects in which every object has the same security settings as the root.
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 specified in [RFC3986].
setup path: The location where supporting files for a product or technology are installed.
site: See website.
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 navigation structure.
site collection administrator: A user who has administrative permissions for a site collection.
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 definition: A family of site definition configurations. Each site definition specifies a name and contains a list of the site definition configurations. See also site definition configuration.
site identifier: A GUID that is used to identify a site in a SharePoint site collection.
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 a site that contains a resource and does not start with a leading slash (/).
stored procedure: A precompiled collection of SQL statements and, optionally, control-of-flow statements that are stored under a name and processed as a unit. They are stored in a SQL database and can be run with one call from an application. Stored procedures return an integer return code and can additionally return one or more result sets.
store-relative form: See store-relative URL.
store-relative URL: A URL that consists only of a path segment and does not include the leading and trailing slash.
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.
SystemID: A binary identifier that is used to uniquely identify a security principal. For Windows® integrated authentication, it is a security identifier (SID). For an ASP.NET Forms Authentication provider, it is the binary representation that is derived from a combination of the provider name and the user login name.
thicket: A means of storing a complex HTML document with its related files. It consists of a thicket main file and a hidden thicket folder that contains a thicket manifest and a set of thicket supporting files that, together, store the referenced content of the document.
thicket folder: A hidden folder that contains a thicket manifest and a set of thicket supporting files that, together, store the referenced content of a complex HTML document.
thicket main file: The core file of a complex HTML document. It references contained elements such as graphics, pictures, or other media stored as thicket supporting files in a thicket folder. The thicket main file is the target used by the protocol client to access the content of the document.
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.
unghosted: (1) A document that has its content stored in the content database instead of the front-end file system. (2) A column or content type for which the schema is stored in the database instead of the front-end file system.
URL (Uniform Resource Locator): A string of characters in a standardized format that identifies a document or resource on the Internet.
user account directory path: A string representation of the Lightweight Directory Access Protocol (LDAP) distinguished name for an Active Directory® container. It defines a set of users, as specified in [RFC4514].
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.
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.
user interface (UI) version: A single 4-byte integer that stores the version number that appears as a document version number in the user interface. The lower nine bits correspond to the minor version number of the displayed version. The remaining 23 bits correspond to the major version number of the displayed version. See also displayed version.
user name: A unique name that identifies a user account. The user name of an account is unique among the other group names and user names within its own domain or workgroup.
version: See displayed version, historical version, major version, and minor version.
view: See form view (Microsoft® Office InfoPath®) or list view (Microsoft SharePoint® Products and Technologies).
virus scanner: Software that is used to search for and remove computer viruses, worms, and Trojan horses.
web application: (1) A container in a configuration database that stores administrative settings and entry-point URLs for site collections. (2) A software application that uses HTTP as its core communication protocol and delivers information to the user by using web-based languages such as HTML and XML.
web bot: See bot.
Web Front End (WFE): A system that implements the client side of this protocol, issuing calls to the stored procedures defined as part of the interface, typically in response to requests made via a remote file access protocol like that specified in [MS-FPSE] or [RFC2518].
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 web page.
Web Part zone identifier: A string that identifies a Web Part zone on a Web Part Page.
Windows code page: A table that relates the character codes (code point values) that are used by an application to keys on a keyboard or to characters on a display. This provides support for character sets and keyboard layouts for different countries or regions. Also referred to as character set or charset.
Windows collation name: A string identifier that follows the format of the T-SQL COLLATE clause.
workflow: (1) The automation of business processes, where business documents and tasks are passed automatically from one user to another for action, according to a set sequence. (2) 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 identifier: A GUID that is used to identify a workflow.
workflow instance: An instance of a workflow association that performs on a list item the process that is defined in a workflow template.
XML document: A document object that is well formed, as specified in [XML], 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 namespace: A collection of names that is identified by a URI reference that uniquely identifies a group of XML tags that belong to a logical category. Namespaces are used in XML documents as element types and attribute names that group related elements to ensure that element names are unique and to facilitate element discovery.
XML Path Language (XPath): A language that is used to address parts of an XML document, as specified in [XPATH]. XPath provides basic facilities for manipulation of strings, numbers, and Boolean values.
MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used as described in [RFC2119]. All statements of optional behavior use either MAY, SHOULD, or SHOULD NOT.
