Export (0) Print
Expand All

1.1 Glossary

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

Augmented Backus-Naur Form (ABNF)
FrontPage
Hypertext Transfer Protocol (HTTP)
Hypertext Transfer Protocol over Secure Sockets Layer (HTTPS)
Secure Sockets Layer (SSL)
URI
Uniform Resource Locator (URL)

The following terms are specific to this document:

collection: A resource that contains a set of URIs that identify member resources. Use of this term is consistent with what is specified in [RFC4918] section 5.2.

entity: Any document on a server that is accessible using an HTTPURL.

locking: A mechanism that is used for overwrite protection. Locking may be applied to individual resources or to entire collection hierarchies. This term "collection" is used as specified in [RFC4918] sections 3 and 5.

namespace: The entire collection (as specified in [RFC4918] section 5.2) of items under a request URI.

property: A name-value pair that associates metadata with a resource. This term is used as specified in [RFC4918] sections 1 and 6.

resource: An entity that can be identified by a URI. This term is used as specified in [RFC2068] section 1.3.

Transport Layer Security (TLS): A security protocol that supports confidentiality and integrity of messages in client and server applications that communicate over open networks. TLS supports server authentication and, optionally, client authentication by using X.509 certificates (as specified in [X509]). TLS is standardized in the Internet Engineering Task Force (IETF) TLS working group, as specified in [RFC2246].

WebDAV: Web Distributed Authoring and Versioning Protocol, as specified in [RFC4918].

WebDAV client: A computer that uses the WebDAV Protocol, as specified in [RFC4918], to retrieve data from the WebDAV server.

WebDAV server: A computer that supports the WebDAV Protocol, as specified in [RFC4918]. WebDAV clients can connect to, and retrieve data from, a WebDAV server.

web server: A computer on the web that is connected to the Internet backbone and stores web pages that a client can retrieve.

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.

 
Show:
© 2014 Microsoft