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/.
access control list (ACL): A list of access control entries (ACEs) that collectively describe the security rules for authorizing access to some resource; for example, an object or set of objects.
alternate access mapping: A mapping of URLs to web applications. Incoming alternate access mappings are used to provide multiple URL entry points for the same set of content. Outgoing alternate access mappings are used to ensure that content is rendered in the correct URL context.
Augmented Backus-Naur Form (ABNF): A modified version of Backus-Naur Form (BNF), commonly used by Internet specifications. ABNF notation balances compactness and simplicity with reasonable representational power. ABNF differs from standard BNF in its definitions and uses of naming rules, repetition, alternatives, order-independence, and value ranges. For more information, see [RFC5234].
base field type: An XML-based schema that defines the type of data, such as formatted text or an integer, that can be entered and stored in a field in a list. Every field in a list is derived from a specific base field type.
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.
base URL: A URL that is specified for a web resource to convert all relative URLs in that resource to absolute URLs. A base URL ends with either a file name, such as http://www.example.com/sample.htm, or a slash, such as http://www.example.com/subdir/. See also absolute URL.
computed field: A field that can perform data manipulation and display functions by using the contents of other fields.
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.
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.
content type schema: An XML definition that describes the contents of a content type.
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 URL that refers to a directory. A directory name is everything that appears before the last slash in a store-relative form URL.
document library: A type of list that is a container for documents and folders.
Document Workspace site: A SharePoint site that is based on a Document Workspace site template and has a template identifier value of "1". A Document Workspace site is used for planning, posting, and working together on a document or a set of related documents.
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.
field: A container for metadata within a SharePoint list and associated list items.
field internal name: A string that uniquely identifies a field in a content type or a SharePoint list.
field type: A name that identifies the action or effect that a field has within a document. Examples of field types are Author, Page, Comments, and Date.
file: A single, discrete unit of content.
folder: A file system construct. File systems organize a volume's data by providing a hierarchy of objects, which are referred to as folders or directories, that contain files and can also contain other folders.
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.
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).
group: A named collection of users who share similar access permissions or roles.
item identifier: An integer that uniquely identifies an item in a SharePoint list.
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 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.
lookup field: A field of the Lookup type that enables users to select an item from another data source.
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.
Meeting Workspace site: A SharePoint site that is based on a Meeting Workspace site template and has a template ID value of "2". A Meeting Workspace site is used for planning, posting, and working together on meeting materials.
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 "0" (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 "0" (zero).
navigation node: An element in the navigational structure of a site. The element is a link or a 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 navigational structure of a SharePoint site.
principal: An authenticated entity that initiates a message or channel in a distributed system.
ProgID: An identifier that is used by the Windows registry to uniquely identify an object and is in the form OLEServerName.ObjectName, for example, "Excel.Sheet" or "PowerPoint.Slide."
publishing level: An integer that is assigned to a document to indicate the publishing status of that version of the document.
role definition: A named set of permissions for a SharePoint site. See also permission level.
securable object: An object that can have unique security permissions associated with it.
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 described in [RFC3986].
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 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 definition: A family of site definition configurations. Each site definition specifies a name and contains a list of associated site definition configurations.
site identifier: A GUID that is used to identify a site in a 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.
store-relative URL: A URL that consists only of a path segment and does not include the leading and trailing slash.
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.
uncustomized: A condition of a document whose content is stored in a location other than the content database. If a document is uncustomized, the front-end web server determines the location of the content by using the SetupPath value for the document. Also referred to as ghosted.
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 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 9 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.
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 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.
XML document: A document object that is well formed, as described in [XML10/5], 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 Path Language (XPath): A language used to create expressions that can address parts of an XML document, manipulate strings, numbers, and Booleans, and can match a set of nodes in the document, as specified in [XPATH]. XPath models an XML document as a tree of nodes of different types, including element, attribute, and text. XPath expressions can identify the nodes in an XML document based on their type, name, and values, as well as the relationship of a node to other nodes in the document.
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.