Annotation of Quality and Provenance Sample Clauses

Annotation of Quality and Provenance. A key aspect for choosing an appropriate data source is the quality of the provided source. Determining the complete quality requires identification of the quality of the source (e.g. a sensor or a social stream), which is made available through a wrapper service, as well as the quality of the provided data (e.g. temperature values, traffic conditions). Hence, in the CityPulse project quality is considered as the combination of QoS and QoI metrics. A clear distinction of metrics in each category is not always possible, since there can be a close relationship between their meanings. For example, the Precision of a sensor and the Accuracy of a sensor value may describe the identical metric. An observation made in the real world is announced as an instance of StreamData. CityPulse considers a StreamData instance as a composition of one or more Segments provided by an Entity,
AutoNDA by SimpleDocs

Related to Annotation of Quality and Provenance

  • INCORPORATION OF GUIDES BY REFERENCE The Seller/Servicer acknowledges that it has received and read the Guides. All provisions of the Guides are incorporated by reference into and made a part of this Contract, and shall be binding upon the parties; provided, however, that the Seller/Servicer shall be entitled to sell Loans to and/or service Loans for Residential Funding only if and for so long as it shall have been authorized to do so by Residential Funding in writing. Specific reference in this Contract to particular provisions of the Guides and not to other provisions does not mean that those provisions of the Guides not specifically cited in this Contract are not applicable. All terms used herein shall have the same meanings as such terms have in the Guides, unless the context clearly requires otherwise.

  • Inspection of Goods 8.1 The Buyer shall inspect the goods upon delivery.

  • Malicious Use of Orphan Glue Records Registry Operator shall take action to remove orphan glue records (as defined at xxxx://xxx.xxxxx.xxx/en/committees/security/sac048.pdf) when provided with evidence in written form that such records are present in connection with malicious conduct.

  • Vendor’s Specific Warranties, Terms, and License Agreements Because TIPS serves public entities and non-profits throughout the nation all of which are subject to specific laws and policies of their jurisdiction, as a matter of standard practice, TIPS does not typically accept a Vendor’s specific “Sale Terms” (warranties, license agreements, master agreements, terms and conditions, etc.) on behalf of all TIPS Members. TIPS may permit Vendor to attach those to this Agreement to display to interested customers what terms may apply to their Supplemental Agreement with Vendor (if submitted by Vendor for that purpose). However, unless this term of the Agreement is negotiated and modified to state otherwise, those specific Sale Terms are not accepted by TIPS on behalf of all TIPS Members and each Member may choose whether to accept, negotiate, or reject those specific Sale Terms, which must be reflected in a separate agreement between Vendor and the Member in order to be effective.

  • Review of legality and data minimisation (a) The data importer agrees to review the legality of the request for disclosure, in particular whether it remains within the powers granted to the requesting public authority, and to challenge the request if, after careful assessment, it concludes that there are reasonable grounds to consider that the request is unlawful under the laws of the country of destination, applicable obligations under international law and principles of international comity. The data importer shall, under the same conditions, pursue possibilities of appeal. When challenging a request, the data importer shall seek interim measures with a view to suspending the effects of the request until the competent judicial authority has decided on its merits. It shall not disclose the personal data requested until required to do so under the applicable procedural rules. These requirements are without prejudice to the obligations of the data importer under Clause 14(e).

  • Technical Standards The Generation System shall be installed and operated by the Interconnection Customer consistent with the requirements of this Agreement; the Technical Requirements; the applicable requirements located in the National Electrical Code (NEC); the applicable standards published by the American National Standards Institute (ANSI) and the Institute of Electrical and Electronic Engineers (IEEE); and local building and other applicable ordinances in effect at the time of the installation of the Generation System.

  • EVENTS CONSTITUTING MATERIAL BREACH OF AGREEMENT The Applicant shall be in Material Breach of this Agreement if it commits one or more of the following acts or omissions (each a “Material Breach”):

  • Suspension of unsafe Construction Works (i) Upon recommendation of the Authority’s Engineer to this effect, the Authority may by notice require the Contractor to suspend forthwith the whole or any part of the Works if, in the reasonable opinion of the Authority’s Engineer, such work threatens the safety of the Users and pedestrians.

  • Data Security and Unauthorized Data Release The Requester and Approved Users, including the Requester’s IT Director, acknowledge NIH’s expectation that they have reviewed and agree to manage the requested controlled-access dataset(s) and any Data Derivatives of controlled-access datasets according to NIH’s expectations set forth in the current NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy and the Requester’s IT security requirements and policies. The Requester, including the Requester’s IT Director, agree that the Requester’s IT security requirements and policies are sufficient to protect the confidentiality and integrity of the NIH controlled-access data entrusted to the Requester. If approved by NIH to use cloud computing for the proposed research project, as outlined in the Research and Cloud Computing Use Statements of the Data Access Request, the Requester acknowledges that the IT Director has reviewed and understands the cloud computing guidelines in the NIH Security Best Practices for Controlled-Access Data Subject to the NIH GDS Policy. The Requester and PI agree to notify the appropriate DAC(s) of any unauthorized data sharing, breaches of data security, or inadvertent data releases that may compromise data confidentiality within 24 hours of when the incident is identified. As permitted by law, notifications should include any known information regarding the incident and a general description of the activities or process in place to define and remediate the situation fully. Within 3 business days of the DAC notification, the Requester agrees to submit to the DAC(s) a detailed written report including the date and nature of the event, actions taken or to be taken to remediate the issue(s), and plans or processes developed to prevent further problems, including specific information on timelines anticipated for action. The Requester agrees to provide documentation verifying that the remediation plans have been implemented. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. All notifications and written reports of data security incidents and policy compliance violations should be sent to the DAC(s) indicated in the Addendum to this Agreement. NIH, or another entity designated by NIH may, as permitted by law, also investigate any data security incident or policy violation. Approved Users and their associates agree to support such investigations and provide information, within the limits of applicable local, state, tribal, and federal laws and regulations. In addition, Requester and Approved Users agree to work with the NIH to assure that plans and procedures that are developed to address identified problems are mutually acceptable and consistent with applicable law.

  • Manufacturers’ Warranties If a Lease Vehicle is covered by a Manufacturer’s warranty, the Lessee, during the Vehicle Term for such Lease Vehicle, shall have the right to make any claims under such warranty that the Lessor could make.

Time is Money Join Law Insider Premium to draft better contracts faster.