1.1 Glossary
This document uses the following terms:
add-in: Supplemental functionality that is provided by an external application or macro to extend the capabilities of an application.
application manifest: An XML file that describes the contents and requirements for a deployment package.
certification authority (CA): A third party that issues public key certificates. Certificates serve to bind public keys to a user identity. Each user and certification authority (CA) can decide whether to trust another user or CA for a specific purpose, and whether this trust should be transitive. For more information, see [RFC3280].
code access security permission set: A set of rules that are applied to an executable component to grant or restrict access to functionality and resources that are associated with that component.
deployment manifest: An XML file that describes the identity and version of a deployment package.
deployment package: A collection of files that can be used to deploy and manage customizations, such as add-ins, to a computer. It consists of an application manifest, a deployment manifest, and related package files.
digest: The fixed-length output string from a one-way hash function that takes a variable-length input string and is probabilistically unique for every different input string. Also, a cryptographic checksum of a data (octet) stream.
digital signature: A value that is generated by using a digital signature algorithm, taking as input a private key and an arbitrary-length string, such that a specific verification algorithm is satisfied by the value, the input string, and the public key corresponding to the input private key.
entry point: A starting address for an assembly that is written in the form NamespaceName.ClassName.
fully qualified class name: A class name that includes namespace information. Use of a fully qualified class name ensures that the class name is treated as unique.
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.
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.
package file: A file that is in a deployment package and is not a manifest file.
post-deployment action: A method that can run before or after deployment events.
public key: One of a pair of keys used in public-key cryptography. The public key is distributed freely and published as part of a digital certificate. For an introduction to this concept, see [CRYPTO] section 1.8 and [IEEE1363] section 3.1.
root element: The top-level element in an XML document. It contains all other elements and is not contained by any other element, as described in [XML].
strong name: A name that consists of the simple text name, version number, and culture information of an assembly, strengthened by a public key and a digital signature that is generated over the assembly.
time stamp authority: A service acknowledging that a datum existed before a specific time. The service is typically a trusted third party.
timestamp: A condition of a digital signature that indicates whether the signature was created with a valid certificate that has expired or was created with a certificate that had expired already. If the certificate expired after the signature was created, the signature can be trusted. If it expired before the signature was created, it cannot be trusted.
XML: The Extensible Markup Language, as described in [XML1.0].
XML schema definition (XSD): The World Wide Web Consortium (W3C) standard language that is used in defining XML schemas. Schemas are useful for enforcing structure and constraining the types of data that can be used validly within other XML documents. XML schema definition refers to the fully specified and currently recommended standard for use in authoring XML schemas.
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.