1.1 Glossary

The following terms are defined in [MS-GLOS]:

access control list (ACL)

globally unique identifier (GUID)

language code identifier (LCID)

security identifier (SID)

security provider

UTF-8

The following terms are specific to this document:

active user: A user is considered "active" if he or she created or modified any data in the site collection.

attachment: A document contained within a list item. Attachments are stored in a folder in the list with the path segment "Attachments".

Back End Database Server (BEDS): A system that implements the server side of this protocol. The Back End Database Server provides access to databases containing persistently stored documents and their metadata.

backward link: A backward link is a hyperlink between a referenced document and the referencing party. For example, when document A contains a hyperlink to document B, document B has a backward link to document A.

bot: A structured HTML comment, also known as a Web bot, that is processed by the WFE server when the containing document is opened by or saved to the server, as specified in [MS-FPSE] section 1.1.

Build Dependency Set: Represents dependencies for a file. A .NET class (specifically System.Web.Compilation.BuildDependencySet) that represents a set of file dependencies managed by the .NET Build Manager (System.Web.Compilation.BuildManager).

build version: The version of the binary files of the software.

change log: A log of changes to items that can be accessed by applications that need to synchronize with the site. The change log contains information about item actions: Add, Update, Delete, Rename, Move away, and Move into, at the list, Web site, site collection, and content database levels.

checked out: A document version, which has been created and locked long-term for exclusive editing by a particular user under the version control system, which has a publishing level of checked out. The checked out version may be discarded, or it may be checked in, which will either promote its Publishing Level to draft if draft versions are enabled, or promote its Publishing Level to published if moderation is not required, or signal that it is ready for approval if configured to require moderation approval to mark a document as published.

content database: A database stored on the BEDS, which holds the stored procedures, site collections, and the contents of the site collection.

content type: A named and uniquely identifiable collection of one or more fields that allow item specific metadata to be added to individual list items. Content types may be built-in or user-defined. List items may have associated content types. One or more content types can be associated with a list or document library, restricting the contents to items of those content types.

Current User: All processing in the WFE and the BEDS is done using the identity and permissions of the currently authenticated user, which may be a system process. This user is referred to as the current user.

current version: A document under version control may have as many as three versions that can be considered the current version. A user will see one of these three versions as the current version depending on the user's permissions, the document's publishing level, and whether the user has the document checked out. A user with minimal permissions can see only the most recent published version of the document, which has a positive major version number and a minor version number of zero. A user with permission to see draft versions of the document can see the most recently checked in draft version of the document. The user who has a document checked out can also see the checked out version, which has the next incremental version number after the most recent checked in draft or published version. All of these versions are considered the current version, even though only one is returned to a particular user as the current version when requested, depending on these criteria. Older versions are considered historical versions

Database Build Version: The version of the binary files that have created the Database.

Deleted: Documents, list items, and user information can be marked as Deleted, which removes them from the WFE display but does not drop the corresponding entries from the database, allowing them to be subsequently restored.

Dictionary: A collection of key/value pairs. Each pair consists of a key, which is a string, and a value that can be of any type. Values in the Dictionary are retrieved by providing a key for which the Dictionary returns the associated value.

Directory Name: The part of a Store-Relative Form URL that refers to a directory. The Directory Name is composed of everything before the last slash in a Store-Relative Form URL. For documents in the root directory, the Directory Name is an empty string.

display name: A text string used to identify a principal or other SharePoint object in the WFE. Sometimes referred to as a title.

Displayed Version: Document version number information in the format displayed by the UI. The UI displays version number information in the format MajorVersion.MinorVersion, where MajorVersion is the published version number and MinorVersion is the draft version number, separated by a decimal point. Displayed Version number information is stored internally as a single 4-byte integer; see UI version for details.

document: An object in the SharePoint Store that can be identified by a URI, such as a directory, file (including attachments and Web pages), folder, list item, list, document library, or site. Under the version control system, a document can have multiple versions stored in the BEDS, each with a unique UI version number. A document may be further distinguished by its publishing level (whether it is a checked out version, a draft version or a published version). The most recent of each publishing level of the document is a current version; older versions are historical versions.

document identifier: A GUID used to uniquely identify a document within a site collection. Document identifiers include Site Identifiers and List Identifiers.

document library: A list created as a container for documents. A document library stores documents and folders. A document library can support publishing status values for documents (draft, checked in, checked out, and published).

document stream: A byte stream associated with a document, such as the content of a file. Not all documents have document streams.

Domain Group: A principal that represents a collection of users and Domain Groups. A Domain Group is an external group.

draft: A document version that is not published or checked out has a publishing level of draft. Depending on configuration settings and user permissions, draft support may not be enabled, or a user may not have permission to see draft versions of a document. If minor version numbering is enabled, a draft is given the next available minor version number.

Dynamic Web Template: An HTML-based master copy of a page containing settings, formatting, and elements such as text, graphics, page layout, styles, and regions of a page that can be modified.

End-User Client (EUC): The HTTP-enabled program running on the end-user's local machine and communicating with the BEDS.

event host: The 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 document libraries, 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 have been deprecated. They are replaced by the capabilities of event receivers.

external group: A group principal defined by an external Role Provider, such as a domain group from Active Directory, provided by Windows Integrated Authentication, or a role from ASP.NET Forms Authentication. External groups are distinguished from site groups, which are created and managed within Windows SharePoint Services.

feature: A structured modular component that allows built in or user defined classes or objects to extend the WFE. Schemas of lists or document libraries or new content types are examples of Features. Features are an implementation-specific capability of Windows SharePoint Services 3.0.

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

Fine-Grained Permissions (FGP): A site is said to have FGP when any of the lists it contains has permissions that differ from the permissions in effect on the site. A list is said to have FGP when any of its items has permissions that differ from the effective permissions on the list. If a list has FGP, then so does the site that contains it directly.

folder: A container within a list that acts like a file system directory. A folder can contain other folders, documents, or list items.

form: A page that allows the creation, viewing or editing of list items in a list.

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.

Ghosted: A document that does not have its content stored in the content database. The WFE server server determines the location of the content as specified by the SetupPath value of the document that is ghosted.

Group Identifier: A Site Group Identifier.

historical version: Any version of a document that is not one of the current versions is considered a historical version. Depending on configuration settings, historical versions may or may not be retained in the BEDS and may or may not be visible to particular users.

host header mode: Windows SharePoint Services supports hosting multiple domain-named sites in a single virtual server. This is called host header mode, because Windows SharePoint Services uses the HTTP host header or domain name to resolve the different sites.

Leaf Name: The part of a Store-Relative Form URL that refers to a specific target item. The Leaf Name is composed of everything after the last slash mark in the Store-Relative Form URL of a document. The Leaf Name may be an empty string if the document is a directory.

level: A publishing level.

link: A backward link or forward link to or from a document, folder, site, list or list item. A collection of meta-information is maintained for these links.

list: A container within a site that stores list items. A list has a customizable schema composed of one or more columns that are composed of fields. A list can have versioning capabilities enabled, allowing multiple historic versions of a document or list item to be tracked. Implementation-specific specialized lists exist within Windows SharePoint Services including but not limited to surveys, issues lists, task lists, and discussion boards.

list identifier: A document identifier for a list.

list item: An individual entry within a list. Each list item has a schema corresponding to the list that contains it by having matching fields depending on the content type of the list item.

List Item Identifier: A List Item Identifier is a 4-byte integer value used to uniquely identify a list item within a site collection.

login name: The account name used to identify a principal, as specified by the authentication role provider. For example, using Windows-integrated authentication, this takes the form 'DOMAIN\username'.

metadata: Data that describes an object. Metadata can be associated with site collections, sites, documents, and other objects.

Metadict: A dictionary for metadata with strongly typed values, as specified in [MS-FPSE] section 2.2.2.2.11.

minor versioning: A version numbering scheme that enables tracking of both major and minor version numbers. A list can be configured to enable minor versioning. When minor versioning is enabled, only minor version numbers are incremented for each new version of a list item in the list unless a major version is explicitly published. When minor versioning is disabled, only the major version number is incremented, and the minor version is always zero.

moderation: A feature of a document library or list that, when enabled, enforces a simple approval workflow on all documents before they are published. When enabled, a document that is submitted to be published must be either approved or rejected by a user who is configured with the necessary approval privileges.

page: A document consisting of HTML, which can contain dynamic content such as Web parts, which are interpreted before display to a client application.

personal view: A view of a list created by users for their own personal use, which is unavailable to other users of the list or document library.

principal: A unique identity that can be used to regulate access to resources. A principal can be a human user, a service entity running on a computer, or a domain group that represents a set of users and domain groups. Sometimes referred to as a security principal.

public view: A view of a list configured for the use of all users of a list or document library.

published: A document version that has been approved and promoted to visibility for all users has a publishing level of published. Configurations can require moderation approval to publish a document. A published document has its UI version number incremented to the next positive major version number, with its minor version set to zero. Depending on the configuration settings for support for draft versions, users may have permissions to demote published documents to draft, which restores the previous UI version number of the document and sets its publishing level to draft.

publishing level: The publishing status of a document version. A particular version of a document can be published (or approved), or it can be a draft, which in turn can be checked out. The publishing status of each version of a document with a publishing level. A published document has a major version number of one or higher and a minor version of zero. A document with a nonzero minor version number is considered a draft. Support for draft versions is optional and configurable. User permissions can be configured to allow only some users to see draft versions. Only the user who has checked out a document can see the checked out version.

Recycle Bin: A Windows SharePoint Services implementation-specific attributed collection of objects that have been marked as deleted, that can be restored.

Result Set: A result set is similar in structure to a database table and is used to return structured data from a query or stored procedure call. The order and content of the data in the result set is a function of the query or is implementation-specific.

return code: A scalar integer result value returned from a stored procedure.

Role: A role definition.

Role Assignment: A principal or site group can be associated with a scope through a Role Assignment, which is a membership collection with common role definitions associated with the scope. Built-in Role Assignments include "Owners," "Contributors," and "Visitors," and additional Role Assignments with custom role definitions can be added.

Role Definition: A collection of Windows SharePoint Services rights that can be bound to a specific principal or site group. Also known as a role. Role Definitions that are provided by default within Windows SharePoint Services are Administrator, with a title of "Full Control"; Reader (also known as Browser) with a title of "Read"; Contributor, with a title of "Contribute"; Web Designer, with a title of "Design"; and Guest, with a title of "Limited Access". Custom Role Definitions can also be created.

root site: The first site in a site collection. All other sites within a site collection are children of the root site. The URL of the root site is also the URL of the site collection.

scope: A scope represents a URL subtree hierarchy that shares the same security permissions. A securable object can either have its own security permissions or inherit them from its parent. A securable object with unique security permissions, and all descendants that inherit those security permissions, form a scope, with the securable object as the root of that scope. A scope cannot span more than a single site collection, but it can span multiple sites. Every item is the root or a member of a containing scope, and every scope has an associated identifier.

scope identifier: A GUID that is used to uniquely identify a scope within a site collection.

securable: An object is securable if it can have unique security permissions associated with it. The security permissions of a securable object can be unique or can be inherited from a parent. All nonsecurable objects inherit the security permissions of their parent. The site collection, site, list, and list item are securable. A folder or document within a list is securable because it gets its permissions through the underlying list item. Pages that do not belong to any list are not securable; they always inherit their security permissions from the containing site. Attachment files and thicket files are not directly securable either; they always inherit the permissions of the associated list item. Each securable object has its security permissions set by its ACL and other security metadata.

security principal: A principal.

security principal object: An object corresponding to a principal. A security principal object contains an identifier, used by the system and applications to name the principal, and a secret shared only with the principal. The shared secret allows the principal to authenticate itself through an authentication provider such as Windows Integrated Authentication or ASP.NET Forms Authentication.

Server-Relative: A Server-Relative URL is a Store-Relative URL with a leading slash mark ('/') character.

site: An autonomous Web service with a contiguous URL namespace. Each site is a member of a site collection and has its own entry points, metadata, and independent administration, authoring, and browsing permissions. A site is a container that may contain documents, document libraries, lists, and child sites known as subsites. The structure and content of sites, when created, are based on implementation-specific site templates such as but not limited to team sites, document workspaces, and meeting workspaces. Also referred to as a Web site.

site administrator: A principal which has administrative permissions for a site collection.

site collection: A collection of one or more hierarchically nested sites within a single content database that are managed as a single unit. A site collection can be identified by a unique GUID value or by the URL of the root site of the site collection.

Site Group: A container within a site collection used as a security structure for granting rights to principals.

Site Group Identifier: A Site Group Identifier is a 4-byte integer value used to uniquely identify a site group within a site collection. Site Group Identifiers are assigned from the same numbering space as User Identifiers and cannot overlap. Values of -1 and 0 are reserved to indicate invalid or unknown Site Group Identifiers. For example, by default, WSS 3.0 creates three implementation-specific site groups with default Site Group Identifiers for use in role assignments when provisioning a new site collection: "Site Owners" (3), "Site Visitors" (4), and "Site Members" (5).

site identifier: A document identifier for a site.

stored procedure: A subroutine in T-SQL that executes a series of T-SQL statements and returns an integer Return Code. The T-SQL statements can additionally return zero or more Result Sets to the caller of the stored procedure.

Store-Relative Form: A URL in Store-Relative Form consists only of a path segment, where leading and trailing slash characters have been stripped.

Structured Query Language (SQL): ISO/IEC standard language for querying database systems, as specified in [ISO/IEC-9075] and [FIPS127]. See also T-SQL.

subsite: A site whose URL is composed in part by the URL of a parent site within the same site collection. A subsite parent may be either the root site of the site collection or another subsite.

System Account: The service entity principal running on the WFE, which is used for internal processes in the site collection requiring a User Identifier. The System Account has a login name of "SHAREPOINT\system" and always has a User Identifier value of 1073741823 and a binary SystemId value of 0x010100000000000000000000.

SystemID: A binary identifier used to uniquely identify a principal. If using Windows Integrated Authentication, this is a security identifier (SID). If using an ASP.NET Forms Authentication provider, this is the binary representation of the login name of the form provider: username, with every character converted to lowercase.

thicket: A complex HTML document may be stored as a thicket, which consists of the thicket main file along with a hidden thicket folder containing a thicket manifest and a set of thicket supporting files that together store the referenced content of the document (for example, a Web page or Word HTML document that includes graphics, pictures, or other media is a thicket).

thicket folder: A hidden folder containing a thicket manifest and a set of thicket supporting files that together store the referenced content of a complex HTML document (for example, a Web page or Microsoft Word HTML document that includes graphics, pictures, or other media). A thicket folder has a name based on the name of the thicket main file, with a suffix added that is recognized as a thicket folder.

thicket main file: The main file of an HTML document that references contained elements such as graphics, pictures, or other media stored as thicket supporting files in a thicket folder.

thicket manifest: An XML file containing a manifest for the set of thicket supporting files that together store the referenced content of a thicket main file, which by convention is named filelist.xml and is contained in a hidden thicket folder.

thicket supporting file: A file containing a graphic element, a picture, or other media that is referenced by a thicket main file and stored in a thicket folder as part of a thicket.

title: A display name.

Transact-Structured Query Language (T-SQL): Microsoft implementation of, and extensions to, the ISO/IEC Structured Query Language.

UI version: A document version number information in the format used to store displayed version numbers internally. UI version number information is stored as a single 4-byte integer. The lower 9 bits correspond to the minor version number of the displayed version, while the remaining 23 bits refer to the major version number. For example, a document with a displayed version number of 4.7 would have a UI version value of (4 * 512) + 7 = 2055.

unghosted: A document that has its content stored in the content database.

user: A person or service entity using the WFE server. A user must be authenticated as a principal by an authentication provider such as Windows Integrated Authentication or ASP.NET Forms Authentication.

user identifier: A user identifier is a 4-byte integer value used to uniquely identify a principal within a site collection. User identifiers are assigned from the same numbering space as Site Group Identifiers and cannot overlap. Certain user identifiers are predefined, such as the system account (1073741823), the site collection owner (1), and the secondary site collection contact (2). Values of -1 and 0 are reserved to indicate invalid or unknown user identifiers.

version: A set of numbers used to indicate a program's stage of development. The version is represented by a string that contains these numbers separated by periods; for example, 12.0.34.0. When two versions are compared, the leftmost has the most weight, and the weight decreases in each of the numbers going from left to right. The version increases when the product enters a later stage of development.

view: A sorting, display, and querying system for a list or document library. A view can be exposed by a Web part. Users with the appropriate permissions can create new personal views for their own personal use or public views for the use of all users of the list or document library.

Web application: A container of site collections, corresponding to an Internet Information Services (IIS) Web site with a unique application pool.

Web bot: See bot.

Web discussions: A component of Windows SharePoint Services that allows users to enter comments about documents and pages without modifying their actual content.

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 structured modular component that can generate HTML in a page on the WFE server server.

Web part page: A page dedicated to displaying Web parts in Web part zones.

Web Part Zone: A structured HTML section of a page that provides a location for Web parts . A Web Part Zone can contain zero or more Web parts. A Web Part Zone with no Web parts is presented as an empty tag in the page HTML source when sent to the user.

welcome page: An optional page, such as default.aspx, which may be specified as the default redirect target when browsing to a site URL without specifying a Leaf Name.

Windows code page: Also called a "character set" or "charset." A code page is an ordered set of characters of a given script in which a numeric index (a code-point or code position value) is associated with each character. Windows defines code pages for multiple locales and identifies each with a specific integer; for example, the default Windows code page, known variously as the "ANSI Latin 1" or Windows-1252" or "Western European (Windows)" code page, has an integer identifier of 1252. The set of code pages supported on any particular instance of Windows is version-dependent and setup-dependent.

Windows SharePoint Services (WSS): Web services that provide a feature-rich team collaboration environment.

workflow: A structured modular component that can allow built-in or user-defined activities to act upon list items or documents in lists or document libraries.

MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used as specified in [RFC2119]. All statements of optional behavior use either MAY, SHOULD, or SHOULD NOT.

Show: