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/.
ActiveX control: A reusable software control, such as a check box or button, that uses ActiveX technology and provides options to users or runs macros or scripts that automate a task. See also ActiveX object.
ActiveX Data Objects (ADO): A data access interface that connects to, retrieves, manipulates, and updates data in Object Linking and Embedding (OLE) database-compliant data sources.
ASCII: The American Standard Code for Information Interchange (ASCII) is an 8-bit character-encoding scheme based on the English alphabet. ASCII codes represent text in computers, communications equipment, and other devices that work with text. ASCII refers to a single 8-bit ASCII character or an array of 8-bit ASCII characters with the high bit of each character set to zero.
ASP.NET control: A server-side component that encapsulates user interface and related functionality. An ASP.NET server control derives directly or indirectly from the System.Web.UI.Control class. The superset of ASP.NET server controls includes web server controls, HTML server controls, and ASP.NET mobile controls.
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.
attachment: An external file that is included with an Internet message or associated with an item in a SharePoint list.
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].
background color: A color against which characters, patterns, and graphics are displayed. See also foreground color.
blind carbon copy (Bcc) recipient: An addressee on a Message object that is not visible to recipients of the Message object.
Boolean: An operation or expression that can be evaluated only as either true or false.
border formatting: A set of properties that, as a whole, specify the appearance of a border, such as color, line style, and thickness.
browser-compatible form template: A form template that is designed for publication to a protocol server that is running InfoPath Forms Services.
built-in control: A control that is included with Microsoft InfoPath and appears by default in the Controls pane.
business object: An object that performs a defined set of operations, such as data validation or business logic rules, related to a business process or workflow.
cabinet (.cab) file: A single file that stores multiple compressed files to facilitate storage or transmission.
carbon copy (Cc) recipient: An address on a Message object that is visible to recipients of the Message object but is not necessarily expected to take any action.
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 SharePoint Products and Technologies.
column: A single set of data that is displayed vertically in a worksheet or a table.
conditional formatting: A mechanism that changes the appearance of a user interface element based on the evaluation of a rule or expression.
connection string: A series of arguments, delimited by a semicolon, that defines the location of a database and how to connect to it.
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.
control: A graphical user interface object that users interact with when working with applications, forms, documents, webpages, and other types of files.
data adapter: Code that submits data to and retrieves data from an external data source. Also referred to as data provider.
data connection: A link between an application and a data source. Data connections can be used to query and submit data.
data connection library: A SharePoint library that contains a collection of universal data connection (.udcx) and Office data connection (.odc) files.
data source: A collection of fields and groups that define and store the data for an InfoPath form. Controls in a form are bound to the fields and groups in the data sources of the form. See also main data source and secondary data source.
digital signature: A message authenticator that is typically derived from a cryptographic operation by using an asymmetric algorithm and private key. When a symmetric algorithm is used for this purpose, the authenticator is typically referred to as a Message Authentication Code (MAC).
empty string: A string object or variable that is initialized with the value "".
Extended Backus-Naur Form (EBNF): A modified version of Backus-Naur Form (BNF), which is commonly used to describe programming languages and formal languages. EBNF extends standard BNF to better enable the concise expression of such languages, as described in [ISO-14977].
Extensible Stylesheet Language (XSL): An XML vocabulary that is used to transform XML data to another form, such as HTML, by means of a style sheet that defines presentation rules.
external content type: A type of DataClass object that is stored in a line-of-business (LOB) system and whose instances have a persistent EntityInstanceId. Also referred to as Entity.
external list: A container that is within a SharePoint site and that references a set of EntityInstances that are sourced from a line-of-business (LOB) system. It has a customizable schema that is composed of one or more Fields.
field: A discrete unit of a record that has a name, a data type, and a value.
field definition: The definition of a field in the Collaborative Application Markup Language (CAML).
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.
form definition (.xsf) file: An XML file with an .xsf file name extension. The file contains information about the files and components that are used within a form, including user interface customizations, XML schemas, views, business logic, events, and deployment settings.
form file: An XML file that contains data that is entered into an InfoPath form by using a web browser or Microsoft InfoPath.
form library: A type of document library that is optimized for storing and displaying data in XML-based forms.
form security level: A setting that determines whether an InfoPath form can access data on other domains, or access files and settings on a user's computer. There are three security levels for forms: Restricted, Domain, and Full Trust.
form server: A server that can host XML-based electronic forms and that supports rendering those forms in a web browser.
form template: A file or set of files that defines the data structure, appearance, and behavior of a form.
form template (.xsn) file: A cabinet (.cab) file with an .xsn file name extension that contains the files that comprise a form template.
form view: A display setting that is saved with an InfoPath form template and specifies which controls and data appear on a form when the form is being filled out.
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: 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.
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.
HTTP method: In an HTTP message, a token that specifies the method to be performed on the resource that is identified by the Request-URI, as described in [RFC2616].
Hypertext Markup Language (HTML): An application of the Standard Generalized Markup Language (SGML) that uses tags to mark elements in a document, as described in [HTML].
Hypertext Transfer Protocol (HTTP): An application-level protocol for distributed, collaborative, hypermedia information systems (text, graphic images, sound, video, and other multimedia files) on the World Wide Web.
identifier: A string value that is used to uniquely identify a component of the CSDL and that is of type SimpleIdentifier.
Information Rights Management (IRM): A technology that provides persistent protection to digital data by using encryption, certificates, and authentication. Authorized recipients or users acquire a license to gain access to the protected files according to the rights or business rules that are set by the content owner.
language code identifier (LCID): A 32-bit number that identifies the user interface human language dialect or variation that is supported by an application or a client computer.
left-to-right: A reading order in which characters in words are read from left to right, and words are read from left to right in sentences.
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.
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 created the view; and Public, which can be used by all users who have permission to access to the site.
LobSystemInstance: A type of MetadataObject that represents a specific deployed instance of a line-of-business (LOB) system, as represented by a LobSystem. LobSystemInstances are contained by LobSystems. LobSystemInstance Properties describe how to connect to an instance of the LobSystem that contains them by providing information such as the server name, connection string, and authentication mode.
locale: A collection of rules and data that are specific to a language and a geographical area. A locale can include information about sorting rules, date and time formatting, numeric and monetary conventions, and character classification.
lookup field: A field of the Lookup type that enables users to select an item from another data source.
main data connection: The primary connection between an InfoPath form and a data source that stores or provides data for the form. The main data connection defines the structure of the main data source of the form.
main data source: An XML document or XML schema that defines the collection of fields and groups that store data for an InfoPath form.
MIME type: A method that is used by protocol clients to associate files of a certain type with applications that can open or access files of that type.
mobile device: A small computing device that is easily portable and can be used in various environments.
named property: A property that is identified by both a GUID and either a string name or a 32-bit identifier.
postback: A process in which a webpage sends data back to the server that hosts the page.
print view: A document view that displays a document as it will appear on a printed page.
query: A formalized instruction to a data source to either extract data or perform a specified action. A query can be in the form of a query expression, a method-based query, or a combination of the two. The data source can be in different forms, such as a relational database, XML document, or in-memory object. See also search query.
red-green-blue (RGB): A color model that describes color information in terms of the red (R), green (G), and blue (B) intensities in a color.
repeating group: A group that can occur more than once in the data source for an InfoPath form. Controls such as repeating sections and repeating tables can be bound to repeating groups. See also bind.
Representational State Transfer (REST): A class of web services that is used to transfer domain-specific data by using HTTP, without additional messaging layers or session tracking, and returns textual data, such as XML.
right-to-left: A reading and display order that is optimized for right-to-left languages.
row: A single set of data that is displayed horizontally in a worksheet or a table.
rule: A condition or action, or a set of conditions or actions, that performs tasks automatically based on events and values.
secondary data connection: Any auxiliary connection between an InfoPath form and a data source that stores or provides data for the form.
secondary data source: An XML data file, a database, or a web service that is used to populate controls or provide values in an InfoPath form.
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].
SHA-256: An algorithm that generates a 256-bit hash value from an arbitrary amount of input data.
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.
SOAP action: The HTTP request header field used to indicate the intent of the SOAP request, using a URI value. See [SOAP1.1] section 6.1.1 for more information.
SOAP message: An XML document consisting of a mandatory SOAP envelope, an optional SOAP header, and a mandatory SOAP body. See [SOAP1.2-1/2007] section 5 for more information.
SpecificFinder: A type of MethodInstance that can be called to return a specific EntityInstance of a specific Entity given its EntityInstanceId. SpecificFinder input is defined and ordered by the Identifiers that are associated with the Entity that is associated with the Method that is associated with the SpecificFinder.
SQL statement: A complete phrase in SQL that begins with a keyword and completely describes an action to be taken on data.
Structured Query Language (SQL): A database query and programming language that is widely used for accessing, querying, updating, and managing data in relational database systems.
submit: The process of sending data to an external data source such as a web service, database, Internet message, or SharePoint site.
symbol file: A file that contains information about an executable image, including the names and addresses of functions and variables.
toolbar: A row, column, or block of controls that represent tasks or commands within an application. A toolbar can be either a menu toolbar, which provides access to menu commands, or a basic toolbar, which contains buttons that provide shortcuts to tasks that are frequently accessed from menus.
Unicode: A character encoding standard developed by the Unicode Consortium that represents almost all of the written languages of the world. The Unicode standard [UNICODE5.0.0/2007] provides three forms (UTF-8, UTF-16, and UTF-32) and seven schemes (UTF-8, UTF-16, UTF-16 BE, UTF-16 LE, UTF-32, UTF-32 LE, and UTF-32 BE).
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].
Uniform Resource Name (URN): A string that identifies a persistent Internet resource, as described in [RFC2141]. A URN can provide a mechanism for locating and retrieving a schema file that defines a specific namespace. Although a URL can provide similar functionality, a URN can refer to more than one URL and is not location-dependent.
Universal Data Connection (.udc, .udcx) file: An XML file that has a .udc or .udcx file name extension that contains user credentials and other authentication information that is used to connect to a data source.
Universal Naming Convention (UNC): A string format that specifies the location of a resource. For more information, see [MS-DTYP] section 2.2.57.
user agent: An HTTP user agent, as specified in [RFC2616].
user name: A unique name that identifies a specific user account. The user name of an account is unique among the other group names and user names within its own domain or workgroup.
UTF-16: A standard for encoding Unicode characters, defined in the Unicode standard, in which the most commonly used characters are defined as double-byte characters. Unless specified otherwise, this term refers to the UTF-16 encoding form specified in [UNICODE5.0.0/2007] section 3.9.
Web Distributed Authoring and Versioning Protocol (WebDAV): The Web Distributed Authoring and Versioning Protocol, as described in [RFC2518] or [RFC4918].
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 connection: An element in a Web Parts Page that defines a provider-consumer data relationship between two Web Parts. When a Web Parts Page is rendered, data provided by one Web Part can affect how and what is rendered by the other Web Part.
web service: A unit of application logic that provides data and services to other applications and can be called by using standard Internet transport protocols such as HTTP, Simple Mail Transfer Protocol (SMTP), or File Transfer Protocol (FTP). Web services can perform functions that range from simple requests to complicated business processes.
Web Services Description Language (WSDL): An XML format for describing network services as a set of endpoints that operate on messages that contain either document-oriented or procedure-oriented information. The operations and messages are described abstractly and are bound to a concrete network protocol and message format in order to define an endpoint. Related concrete endpoints are combined into abstract endpoints, which describe a network service. WSDL is extensible, which allows the description of endpoints and their messages regardless of the message formats or network protocols that are used.
workflow: 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.
XML: The Extensible Markup Language, as described in [XML1.0].
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 element: An XML structure that typically consists of a start tag, an end tag, and the information between those tags. Elements can have attributes and can contain other elements.
XML fragment: Lines of text that adhere to XML tag rules, as described in [XML], but do not have a Document Type Definition (DTD) or schema, processing instructions, or any other header information.
XML node: The smallest unit of a valid, complete structure in an XML document. For example, a node can represent an element, an attribute, or a text string.
XML schema: A description of a type of XML document that is typically expressed in terms of constraints on the structure and content of documents of that type, in addition to the basic syntax constraints that are imposed by XML itself. An XML schema provides a view of a document type at a relatively high level of abstraction.
XML schema document: See XML schema.
XPath expression: An expression that searches an71 XML document and can extract and manipulate data in elements or attributes within that document.
XSL Transformation (XSLT): A declarative, XML-based language that is used to present or transform XML data. It is designed for use as part of the Extensible Stylesheet Language (XSL).
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.