Reference Manual Clause Samples

The Reference Manual clause establishes that a specific manual or document will serve as the authoritative source for technical standards, procedures, or requirements referenced in the agreement. In practice, this clause identifies the exact version or edition of the manual to be used, ensuring that all parties refer to the same set of guidelines or specifications when performing their obligations. By doing so, it eliminates ambiguity and potential disputes over which standards apply, thereby ensuring consistency and clarity in the execution of the contract.
Reference Manual. 10The exception to this statement is the website of the HTE edition incorporated into the 11McCracken, ‘The Exploitation of Dictionary Data and Metadata’, p. 512. 12Ibid. 13Ibid., p. 511. projects have already successfully adopted it or are in the process of adopting it – merits its recommendation as digital form in which to share lexicographical resources.14 But what exactly is RDF/OWL and what are the characteristics attributed to this “standard formalism for information graphs”? RDF and OWL are fundamental standards within the Semantic Web.15 This Web is, in essence, one of linked data, built on top of a set of data standards and technologies that aim to add “well-defined meaning” to information.16 These standards and technologies provide an “infrastructure for publishing, storing, retrieving, reusing, integrating, and analyzing data”.17 Its data form, open for anyone to use, is comprised of statements (or triples) that together form a network of information, one in which concepts are identified by IRIs (often in the form of web addresses or URLs).18 The use of IRIs allows for capturing and identifying data, reusing terminology defined elsewhere, and connecting information found in different digital resources. In effect, this identification mechanism enables thesaurus content to be reused, extended with custom labels and with links to other digital resources. These characteristics of the data form offer intrinsic support for many of the DWBP best practices and facilitate achieving the remaining ones. The underlying data format for Semantic Web information, RDF, is therefore mentioned explicitly in the DWBP documentation as highly suitable for publications on the Web. OWL provides an additional layer of expression that can be used on top of RDF for situations in which highly formal definitions and inferencing mechanisms are required.19 For more informal levels of expression, other Semantic Web standards, such as SKOS, are an alternative to OWL.20 Together, Semantic Web standards offer a well-defined formalism for information graphs. Moreover, they are said to support the functionality desired of historical language thesauri as identified in Chapter 2, since the infrastructure of the Semantic Web allows data to be “retrieved, accessed, reused, and integrated in a meaningful way”.21 Perceived benefits in using this data form are mentioned by ▇▇▇▇▇▇▇▇▇ ▇▇▇▇▇▇▇▇ et al.22 One of these benefits is the ability to merge different datasets, or relate different pe...
View SourceView Similar (3)
Reference Manual. For its facility, HBMS agrees to document in detail (e.g. in a reference manual), the methodologies used to determine the PM emission intensity as required by Section 9.1.
View Source
Reference Manual. For each of its facilities, Glencore agrees to document in detail (e.g. in a reference manual), the methodologies used to determine the PM emission intensity and sulphur capture rate as required by Section 9.1.
View Source
Reference Manual. For each of its facilities, Vale agrees to document in detail (e.g. in a reference manual), the methodologies used to determine the PM emission intensity and sulphur capture rate or sulphur dioxide mass emission limit as required by Section 9.1.
View Source
Reference Manual. For its facility, Teck agrees to document in detail (e.g. in a reference manual), the methodologies used to determine the PM emission intensity and sulphur capture rate as required by Section 9.1.
View Source
Reference Manual. For its facility, CEZinc agrees to document in detail (e.g. in a reference manual), the methodologies used to determine the PM emission intensity and sulphur capture rate as required by Section 9.1.
View Source

Related to Reference Manual

  • Maintenance Manual No later than 60 (sixty) days prior to the Project Completion Date, the Contractor shall, in consultation with the Authority’s Engineer, evolve a maintenance manual (the “Maintenance Manual”) for the regular and preventive maintenance of the Project Highway in conformity with the Specifications and Standards, safety requirements and Good Industry Practice, and shall provide 5 (five) copies thereof to the Authority’s Engineer. The Authority’s Engineer shall review the Maintenance Manual within 15 (fifteen) days of its receipt and communicate its comments to the Contractor for necessary modifications, if any.

  • REFERENCE STANDARDS Reference to the standards of any technical society, organization, or association, or to codes of local or state authorities, shall mean the latest standard, code, specification, or tentative standard adopted and published as of the date of execution of the Construction Agreement, unless specifically stated otherwise.

  • Project Manual A bound manual prepared by the Design Professional. It includes the Invitation to Bid, Instructions to Bidders, the Bid Form, the Specifications, the General Conditions and Supplementary General Conditions.

  • Submission of Grievance Information a. Upon appointment of the arbitrator, the appealing party shall, within five (5) days after notice of appointment, forward to the arbitrator, with a copy to the School Board, the submission of the grievance which shall include the following: 1. The issues involved. 2. Statement of the facts. 3. Position of the grievant. 4. The written documents relating to Section 5 of the grievance procedure.

  • Trade Errors The Sub-Advisor will notify the Manager of any Trade Error(s), regardless of materiality, promptly upon the discovery such Trade Error(s) by the Sub-Advisor. Notwithstanding Section 5, the Sub-Advisor shall be liable to the Manager, the Fund or its shareholders for any loss suffered by the Manager or the Fund resulting from Trade Errors due to negligence, misfeasance, or disregard of duties of the Sub Advisor or any of its directors, officers, employees, agents (excluding any broker-dealer selected by the Sub-Advisor), or affiliates. For purposes under this Section 6, “Trade Errors” are defined as errors due to (i) erroneous orders by the Sub-Advisor for the Series that result in the purchase or sale of securities that were not intended to be purchased or sold; (ii) erroneous orders by the Sub-Advisor that result in the purchase or sale of securities for the Series in an unintended amount or price; or (iii) purchases or sales of financial instruments which violate the investment limitations or restrictions disclosed in the Fund’s registration statement and/or imposed by applicable law or regulation (calculated at the Sub-Advisor’s portfolio level), unless otherwise agreed to in writing.