This describes all of the qualified supplementary components and business information entities for the OASIS Universal Business Language (UBL) 2.0 vocabulary. In UBL 2.1 qualified data types are anonymous (in that they are not expressly named or identified) and UBL information items with qualifications are addressed in this document and associated with their respective value qualifications. At this time all value qualifications are code lists, which are a type of value list (the other type being identifier lists). Instance metadata for UBL is described by the UN/CEFACT Core Component Technical Specification (CCTS) Version 2.01. The document contexts are all of the supplementary components and business entities in a UBL instance that have qualified values. These list all of the genericode files of code lists used by UBL information items whose values are qualified by code lists. The unique identifer xml:id= is used later in this file when describing the context for each entity that has a qualified value. The URI value points to the genericode file associated with the identifer. The URI is hyperlinked in this report to a rendering of the contents of the genericode file that follows the rendering of the contexts. A supplementary component is a piece of metadata describing a property of the list of values in which a particular value is found. For example, each code list of currency values has a version and when a currency value is specified in a UBL document it may be important to specify which version of the currency code list that value is found. By knowing the list from which a value is found, the semantics representated by that value are unambiguous. These sets of supplementary components describe where instance-level metadata is found that contains values of list-level metadata from genericode files. Each set is identified in a context using that set's unique xml:id= attribute. Each component pairs an XPath address of the supplementary component (specified in address=) relative to the item with the code list value in the UBL document, with the XPath address of the corresponding list-level metadata item in the genericode file (specified in identification=) relative to the <Identification> element in the code list file. All supplementary components in UBL are defined by the UN/CEFACT Core Component Technical Specification (CCTS) Version 2.01 dated 15 November 2003 http://www.unece.org/cefact/ebxml/CCTS_V2-01_Final.pdf. Table 8-2 "Approved Core Component Type Content and Supplementary Components" lists the various supplementary components available. The UN/CEFACT UnqualifiedDataTypeSchemaModule-2.0.xsd schema fragment specifies the names of the attributes for supplementary components. The Amount. Type supplementary component. There are no supplementary components for the Binary Object. Type. The Code. Type supplementary components. The Identifier. Type supplementary components. The Measure. Type supplementary component. The Quantity. Type supplementary components. The contexts in which various items with a qualified value are specified. The address= attribute is an XPath address that satisfies all of the UBL items in the instance that are qualified with the indicated value lists using the indicated associated set of instance-level metadata items. Each context identifies the collection of supplementary components (by its identifier) where instance-level metadata is found, then all value lists (by their identifier) that apply to the item being addressed. The contexts are listed first for attribute items and then for element items.