Reference Manual Sample Clauses

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 Xxxxxxxxx Xxxxxxxx et al.22 One of these benefits is the ability to merge different datasets, or relate different pe...
AutoNDA by SimpleDocs
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.
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.
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.
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.
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.

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 A. The latest published edition of a reference shall be applicable to this Project unless identified by a specific edition date. B. All reference amendments adopted prior to the effective date of this Contract shall be applicable to this Project. C. All materials, installation and workmanship shall comply with all applicable requirements and standards. 1. Texas Medical Center Architectural Standards and Texas Medical Center Stormwater Management Design Guidelines are applicable to all Projects located within the Texas Medical Center. 2. Owner’s underwriter requirements are applicable to all Projects.

  • 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.

  • Line Information Database LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, ONS must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.

  • Electronic and Information Resources Accessibility and Security Standards a. Applicability: The following Electronic and Information Resources (“EIR”) requirements apply to the Contract because the Grantee performs services that include EIR that the System Agency's employees are required or permitted to access or members of the public are required or permitted to access. This Section does not apply to incidental uses of EIR in the performance of the Agreement, unless the Parties agree that the EIR will become property of the State of Texas or will be used by HHSC’s clients or recipients after completion of the Agreement. Nothing in this section is intended to prescribe the use of particular designs or technologies or to prevent the use of alternative technologies, provided they result in substantially equivalent or greater access to and use of a Product.

  • Implementation Report Within 150 days after the Effective Date, Ensign Group shall submit a written report to OIG summarizing the status of its implementation of the requirements of this CIA (Implementation Report). The Implementation Report shall, at a minimum, include: 1. the name, address, phone number, and position description of the Compliance Officer required by Section III.A, and a summary of other noncompliance job responsibilities the Compliance Officer may have; 2. the names and positions of the members of the Compliance Committee required by Section III.A; 3. the names and positions of the members of the Board of Directors who are responsible for satisfying the Board of Directors compliance obligations described in Section III.A.3; 4. a copy of Ensign Group’s Code of Conduct required by Section III.B.1; 5. the number of individuals required to complete the Code of Conduct certification required by Section III.B.1, the percentage of individuals who have completed such certification, and an explanation of any exceptions (the documentation supporting this information shall be available to OIG upon request); 6. a summary of all Policies and Procedures required by Section III.B (copies of the Policies and Procedures shall be made available to OIG upon request); 7. the following information regarding each type of training required by Section III.C: a. a description of such training, including a summary of the topics covered, the length of sessions, and a schedule of training sessions; b. the number of individuals required to be trained, percentage of individuals actually trained, and an explanation of any exceptions. A copy of all training materials and the documentation supporting this information shall be made available to OIG upon request. 8. a description of the Disclosure Program required by Section III.E; 9. the following information regarding the IRO(s): (a) identity, address, and phone number; (b) a copy of the engagement letter; (c) information to demonstrate that the IRO has the qualifications outlined in Appendix A to this CIA; (d) a summary and description of any and all current and prior engagements and agreements between Ensign Group and the IRO; and (e) a certification from the IRO regarding its professional independence and objectivity with respect to Ensign Group; 10. a description of the process by which Ensign Group fulfills the requirements of Section III.F regarding Ineligible Persons; 11. a list of all of Ensign Group’s locations (including locations and mailing addresses); the corresponding name under which each location is doing business; the corresponding phone numbers and fax numbers; each location’s Medicare and state Medicaid program provider number and/or supplier number(s); and the name and address of each Medicare and state Medicaid program contractor to which Ensign Group currently submits claims; 12. a description of Ensign Group’s corporate structure, including identification of any parent and sister companies, subsidiaries, and their respective lines of business; and

  • Operations Manual The Franchisor agrees to loan to the Franchisee one or more manuals, technical bulletins, cookbooks and recipes and other written materials (collectively referred to as “Operations Manual”) covering Factory Candy ordering, Store Candy manufacturing, processing and stocking and other operating and in-store marketing techniques for the ROCKY MOUNTAIN CHOCOLATE FACTORY Store. The Franchisee agrees that it shall comply with the Operations Manual as an essential aspect of its obligations under this Agreement, that the Operations Manual shall be deemed to be incorporated herein by reference and failure by the Franchisee to substantially comply with the Operations Manual may be considered by the Franchisor to be a breach of this Agreement.

  • Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit C. 9.2 BellSouth will provide LIDB Storage upon written request to <<customer_name>>’s Account Manager stating a requested activation date.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!