Providing Metadata to MetaPub Sample Clauses

Providing Metadata to MetaPub. NPR provides the MetaPub metadata delivery service to ContentDepot users and other authorized third parties such as metadata service providers. The MetaPub metadata delivery service enables the provision and delivery of metadata associated with Content. You may provide metadata associated with your Content directly through the ContentDepot, or through one or more application programming interfaces which may also be used to deliver metadata from MetaPub to authorized users of the Content to which such metadata relates (collectively, the “MetaPub API”). For all metadata that you provide to MetaPub, you grant NPR the right to allow public radio stations, other public telecommunications entities, and authorized third parties to access and use such metadata in accordance with the terms of this Agreement for the purpose of enhancing the Content. You further grant NPR the right to obtain metadata associated with your Content (by gathering metadata programmatically or through manual means) for the purpose of enhancing the Content. You hereby give NPR permission to manage such metadata, whether provided to NPR by you or obtained otherwise by NPR, on your behalf for, and in any manner consistent with, the Distribution Purpose. NPR will not be liable to you for the use of any such metadata (whether provided by you or obtained otherwise by NPR) so long as NPR’s use of the metadata is consistent with the Distribution Purpose. You hereby authorize NPR to provide metadata associated with your Content to other third-party services that deliver metadata. Without limiting the foregoing, you hereby authorize NPR to allow third-party radio device manufacturers to access and use worldwide the metadata in their devices. As part of such authorization, you permit such device manufacturers (i) to use caching to improve the technical performance of their radio devices provided that no metadata may be stored longer than the caching time stipulated at the time of providing the metadata, and (ii) to use a truncated version of the metadata as long as the truncation does not unreasonably distort or misrepresent the metadata, and that the original metadata can be readily accessed on the radio device by the end users. All copyright, trademarks and other intellectual property rights in metadata will remain vested in you or your licensors. If you do not want your metadata to be delivered to third-party services, you may opt out any such delivery by informing NPR. Notwithstanding anything to...
AutoNDA by SimpleDocs

Related to Providing Metadata to MetaPub

  • Access to Network Interface Device (NID 2.4.3.1. Due to the wide variety of NIDs utilized by BellSouth (based on subscriber size and environmental considerations), Mpower may access the on-premises wiring by any of the following means: BellSouth shall allow Mpower to connect its loops directly to BellSouth’s multi-line residential NID enclosures that have additional space and are not used by BellSouth or any other telecommunications carriers to provide service to the premise. Mpower agrees to install compatible protectors and test jacks and to maintain the protection system and equipment and to indemnify BellSouth pursuant to Section 8 of the General Terms and Conditions of this Agreement.

  • Purchase Order Flip via Ariba Network (AN) The online process allows suppliers to submit invoices via the AN for catalog and non- catalog goods and services. Contractors have the ability to create an invoice directly from their Inbox in their AN account by simply “flipping” the purchase order into an invoice. This option does not require any special software or technical capabilities. For the purposes of this section, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider of MFMP the right and license to use, reproduce, transmit, distribute, and publicly display within the system the information outlined above. In addition, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider the right and license to reproduce and display within the system the Contractor’s trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • Access to Software Access Rights to Software which is Results shall comprise: Access to the Object Code; and, where normal use of such an Object Code requires an Application Programming Interface (hereafter API), Access to the Object Code and such an API; and, if a Party can show that the execution of its tasks under the Project or the Exploitation of its own Results is technically or legally impossible without Access to the Source Code, Access to the Source Code to the extent necessary. Background shall only be provided in Object Code unless otherwise agreed between the Parties concerned.

  • Data Use Each party may use Connected Account Data in accordance with this Agreement and the consent (if any) each obtains from each Connected Account. This consent includes, as to Stripe, consent it receives via the Connected Account Agreement.

  • Modification of Licensed Materials The Participating Institutions or the Authorized Users shall not modify or manipulate the Licensed Materials without the prior written permission of the Licensor.

  • Meteorological Data Reporting Requirement (Applicable to wind generation facilities only) The wind generation facility shall, at a minimum, be required to provide the Transmission Provider with site-specific meteorological data including: • Temperature (degrees Fahrenheit) • Wind speed (meters/second) • Wind direction (degrees from True North) • Atmosphere pressure (hectopascals) • Forced outage data (wind turbine and MW unavailability)

  • Unbundled Voice Loop – SL2 (UVL-SL2 Loops may be 2-wire or 4-wire circuits, shall have remote access test points, and will be designed with a DLR provided to NewPhone. SL2 circuits can be provisioned with loop start, ground start or reverse battery signaling. OC is provided as a standard feature on XX0 Xxxxx. The OC feature will allow NewPhone to coordinate the installation of the Loop with the disconnect of an existing customer’s service and/or number portability service. In these cases, BellSouth will perform the order conversion with standard order coordination at its discretion during normal work hours.

  • Technical Standards Applicable to a Wind Generating Plant i. Low Voltage Ride-Through (LVRT) Capability A wind generating plant shall be able to remain online during voltage disturbances up to the time periods and associated voltage levels set forth in the standard below. The LVRT standard provides for a transition period standard and a post-transition period standard.

  • XXX Hosting 10.1 XXX Hosting is not required for resale in the BellSouth region.

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