The following terms are defined in [MS-GLOS]:
ASCII
Augmented Backus-Naur Form (ABNF)
domain
domain name (2)
FILETIME
globally unique identifier (GUID)
language code identifier (LCID)
Unicode
UTF-8
The following terms are specific to this document:
bot: A structured HTML comment, also known as a Web bot, that is evaluated and executed when an author saves a page or, in some cases, when a site visitor browses to a page.
cascading style sheets (CSS): A simple style sheet mechanism that allows authors and readers to attach formatting information to HTML documents. CSS is human readable and writable, and it expresses style in common desktop publishing terminology. CSS sheets cascade; authors can attach a preferred style sheet, and readers may have a personal style sheet to adjust for their own preferences.
daycount: The number of days elapsed since January 1, 1899.
default Web page: All folders on a site have a default Web page (also called a home page). This page is displayed when a user browses to that folder. The default Web page is usually Index.htm or Default.htm, although it can be any page that the site creator or the user specifies.
derived documents folder: Server implementations may need to generate temporary intermediate files or files not directly uploaded by the client. These files are commonly stored in a folder whose service-relative URL is named _derived. On Windows implementations, it includes *.htx files created by the FrontPage Search component and composite text on .gif images, such as those used for theme elements. The contents of the folder are considered a server implementation detail, but the list documents (section 3.1.5.3.20) method allows the client to ask the server to filter out the contents of this folder.
dictionary: A collection of pairs of items. Each pair consists of a key, which is a string and a value that can be of any type. Items in the dictionary are retrieved by providing a key for which the dictionary returns the associated value.
document: A file contained within a document library, List, or site. In a document library, a document is stored as a List item.
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 (such as Draft, Checked-In, Checked-Out, and Published).
executable folder: Web servers commonly support the notion of a server-side executable in which pages are rendered by running a routine rather than by returning static contents from a file. These servers generally allow the administrator to enable and disable this feature on a folder-by-folder basis. A folder is called an executable folder if this feature is enabled for files within it.
folder: A container within a site or List that acts like a file system directory. A folder can contain other folders, documents, or List items.
folder name: The part of a service-relative URL that refers to a folder. The folder name is composed of everything before the last slash in a service-relative URL.
form: A page that allows the creation, viewing, or editing of list items in a List.
hidden documents: Files and folders whose URLs contain a path component that begins with an underscore (_).
internal name: A GUID used for internal identification of a List.
link fixup: Some document formats support the notion of a link, where one document references another document. The server can discover these links to referenced documents and rewrite the links as documents are moved or copied so that the links do not go to stale references. As the server rewrites these links, it is said to be doing link fixup.
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 may have versioning capabilities enabled that allow multiple historic versions of a document or List item to be tracked. The implementation-specific Lists in Windows SharePoint Services include but are not limited to Surveys, Issues Lists, Task Lists, and Discussion Boards.
long-term checkout: A document checkout that rejects edits against the file by other clients but, unlike a short-term checkout, does not expire unless the client application sends the uncheckout document request, as specified in section 3.1.5.3.40.
manifest: An XML document that contains information used to specify the site other than the actual contents of the documents on the site, such as the names, locations, and metadata for the service, folder, and documents; the Web structure; and the List schemas and data. It may also recursively include subsites.
master Web page: Used to create a consistent layout for Web pages. Individual content pages then merge with the master page to produce output that combines the master page layout with the content page content. A master page is an ASP.NET file with the extension .master (for example, MySite.master) with a predefined layout that can include static text, HTML elements, and server controls. The master page is identified by a special @ Master (for more information, see [MSDN-@Master]) directive that replaces the @ Page (for more information, see [MSDN-@Page]) directive used for ordinary .aspx pages.
In addition to the @ Master directive, the master page also contains all of the top-level HTML elements for a page, such as html, head, and form. In addition to static text and controls that appear on all pages, the master page also includes one or more ContentPlaceHolder controls. (For more information, see [MSDN-CTNTPLHLD].) These placeholder controls define regions where replaceable content will appear. In turn, the replaceable content is defined on individual content pages. Individual content pages are bound to a specific master page in the content page's @ Page directive by including a MasterPageFile attribute (for more information, see [MSDN-PageMSTPGFile]) that points to the master page to be used. Multiple master pages can be used to define different layouts for different parts of a site, with a different set of content pages for each master page.
metadata: Data that describes objects such as documents, folders, and Web sites, and that contains the information necessary for the server to track these objects.
metadictionary: A dictionary for metadata about the files, folders, and Web sites in a server. A metadictionary contains strings, or metakeys, that are mapped to strongly typed data.
metakey: The string used to look up a value in a metadictionary.
nesting level: A count used during the formatting of messages. It is the number of times an open-bracket (OBRACKET) is sent, minus the number of times a close-bracket (CBRACKET) is sent. For details, see section 2.2.1.1.3.
page: A document consisting of HTML that may contain dynamic content, such as Web Parts that are interpreted before display to a client application.
root site: The parent site in a site collection. All other sites within a site collection are child sites of the root site. The URL of the root site is also the URL of the site collection.
server-relative: A URL that defines the location of an item in relation to the root of the server. A server's URL can be determined by using the url to web url method, as specified in section 3.1.5.3.6.
service: See site.
service-relative: A URL that defines the location of an item in relation to the root of the site. For example, if a page is located in the root folder of a site, the service-relative URL consists simply of the page name. The FrontPage Server Extensions: Website Management Protocol often returns service-relative URLs that the client must interpret. A service's URL can be determined by using the url to web url method, as specified in section 3.1.5.3.6.
shared themes folder: Microsoft FrontPage implements a feature in which HTML pages can be authored to contain common style elements. These elements are called shared themes, and their HTML contents are stored in the shared themes folder. The service-relative URL of the shared themes folder is _themes.
short filename: A file name that consists of up to eight characters, a period, and up to three characters.
short-term checkout: A document checkout that automatically expires after a set period of time. While a client application has a short-term checkout of a file, edits against the file by other clients are rejected. If the client application does not renew the short-term checkout, edits by other clients are allowed after the short-term checkout expires.
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 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.
structure element: A node within the Web structure of a site. A structure element can have parent elements, child elements, a URL, a type, and an ID. The ID can be either a temporary element ID or a permanent ID.
subsite: A site with a URL that is composed in part by the URL of a parent site within the same site collection. A subsite's parent may be either the root site of the site collection or another subsite. Each subsite can have independent administration, authoring, and browsing permissions from the root site and other subsites.
subweb: See subsite.
task-list files: The FrontPage client has a task-list feature that stores information in two files on the server. The task-list files are always stored in the service-relative URLs _vti_pvt/_x_todo.htm and _vti_pvt/_x_todoh.htm.
templated document: A document that was created automatically as part of the creation of a site and that has not been modified since then. The unmodified contents of this document can be stored in faster storage than other user content as a performance optimization. When the contents of the document have been modified, it is no longer a templated document.
temporary element ID: When making changes to the Web structure, the client constructs structure elements to indicate which nodes to create or move by modifying a copy of the server's Web structure on the client. When the client creates a new node, it gives that node a temporary element ID. When the server applies the changes, it replaces all the temporary element IDs received from the client with permanent element IDs.
thicket: A group of supporting files and folders on the server that together store the contents of one logical document —for example, a page or Microsoft Word document that includes pictures.
untemplated document: A document that has its content stored in the content database.
Web package: A single file that contains a saved version of a site. The Web package contains a manifest, which defines the structure and metadata of the site and its contents, and a set of files, which contain all the file contents from that site.
Web Part: A structured XML component within a pagedocument that SharePoint can recognize and interpret.
Web Parts Tool Pane: A user interface element that can be inserted onto pages that contain Web Parts. This tool pane allows users to modify properties of a particular Web Part on that page.
Web site: See site.
Web structure: The navigation structure for a site. Web structures are hierarchical and are usually rendered into a set of navigational links on all the Web pages within a site. The structure is composed of a set of structure elements.
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.