1.1 Glossary
The following terms are defined in [MS-GLOS]:
access control list (ACL)
class identifier (CLSID)
COM
directory service (DS)
GUID
Hypertext Transfer Protocol (HTTP)
language code identifier (LCID)
principal
security provider
UTC (Coordinated Universal Time)
The following terms are specific to this document:
attachment: An external file that is included with an Internet message or associated with an item in a SharePoint list.
author: The user who created a list item.
back-end database server: 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.
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.
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.
character set: A mapping between the characters of a written language and the values that are used to represent those characters to a computer.
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.
collation: A set of rules that determines how data is compared, ordered, and presented.
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 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.
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.
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.
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. Such objects are 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 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: 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 version of a document or list item that does not have a publishing level of Published or Checked Out.
empty string: A string object or variable that is initialized with the value "".
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 Sharepoint Services 2.0. In Sharepoint Services 3.0, they are replaced by the capabilities of event receivers.
feature: A package of Sharepoint Services 3.0 elements that can be activated or deactivated for a specific feature scope.
field: An element or attribute in a data source that can contain data.
field definition: The definition of a field in Collaborative Application Markup Language (CAML) language.
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: 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.
forward link: A hyperlink between a referenced document and a referencing party. For example, if 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.
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: A named collection of users who share similar access permissions or roles.
integrated Windows authentication: A configuration setting that enables negotiation of authentication protocols in Internet Information Services (IIS). Integrated Windows authentication is more secure than basic authentication, because the user name and password are hashed instead of plaintext.
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.
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.
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.
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 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 server template: A value that identifies the template that is used for a 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 integrated windows authentication, a login name uses the form "DOMAIN\username".
metadict: A dictionary that has strongly typed values.
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.
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.
page type: An integer that specifies the type of a page.
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.
property bag: A container that stores data but is not defined in the schema for a SharePoint list. Instead of interpreting data in a property bag, the server only passes the data in response to requests. See also metadict.
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.
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 definition: A named set of permissions for a SharePoint site. See also permission level.
security principal: A unique entity, also referred to as a principal, that can be authenticated by Active Directory. It frequently corresponds to a human user, but also can be a service that offers a resource to other security principals. Other security principals might be a group, which is a set of principals. Groups are supported by Active Directory.
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].
short-term lock: A type of check-out process in Windows SharePoint Services. Short-term checkouts are implicit and are done when a file is opened for editing. A lock is applied to the file while it is being edited in the client application so that other users cannot modify it. After the client application is closed, the lock is released.
site: 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 Web sites 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 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.
SQL (Structured Query Language): A database query and programming language that is widely used for accessing, querying, updating, and managing data in relational database systems.
SQL authentication: One of two mechanisms for validating attempts to connect to instances of SQL Server. Users specify a SQL Server login ID and password when they connect. The SQL Server instance ensures that the login ID and password combination are valid before allowing the connection to succeed. Windows authentication is the preferred authentication mechanism.
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 Web site that is stored in a named subdirectory of another Web site. The parent Web site 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 integrated windows 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.
T-SQL (Transact-Structured Query Language): A language that contains the commands that are used to administer instances of SQL Server, create and manage all objects in an instance of SQL Server, and to insert, retrieve, modify, and delete all data in SQL Server tables. Transact-SQL is an extension of the language that is defined in the SQL standards that are published by the International Standards Organization (ISO) and the American National Standards Institute (ANSI).
type information: A collection of information that describes the characteristics and capabilities of an object, including the properties, events, and methods for the object.
unghosted: A document whose content is stored in a content database instead of a front-end file system.
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 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.
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).
view identifier: A GUID that is used to uniquely identify a view.
virus scanner: Software that is used to search for and remove computer viruses, worms, and Trojan horses.
Web bot: See bot.
Web discussion: A component and add-in that allow users to enter comments about documents and pages without modifying actual content.
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 Page: An ASP.NET Web page that includes Web Part controls that enable users to customize the page, such as specifying the information that they want to display. Referred to as Web Parts Page in Microsoft SharePoint Foundation 2010.
WebDAV (Web Distributed Authoring and Versioning Protocol): The Web Distributed Authoring and Versioning Protocol, as specified in [RFC2518].
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.
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.
