Edits Sample Clauses

Edits. The records will be edited against the CIBERNET standards, ----- using a 60-day standard for the Call Age Edit. Any records which do not satisfy these standards (noted below) will be returned to the serving carrier.
AutoNDA by SimpleDocs
Edits. Dubbing occurs when a music track is lifted from one commercial spot and is then used in another commercial spot in the same medium (as opposed to a conversion, which is when the spot is used in a separate medium). This is highly common; just think of how many brands have a musical “tag” that gets used in every single commercial for that brand. The tag was only recorded once, but is then dubbed into each successive commercial for that brand. As mentioned earlier, a dub pays the same as a conversion, which pays the same as a standard re-use. In many instances, this fee may be referred to generally as a “dubbing fee,” even when the payment is not being made for a dub.
Edits. The partnership seeks to guide the evolution protect and restore the Bay ecosystem to benefit. Comment: Again, this language continues to use narrow wording that excludes values that are important to people. Further, it does not embrace the range of goals and outcomes included in the draft agreement. Alternative more inclusive language is: “The partnership seeks to protect and restore the GIT Chairs Editorial Board health, heritage, natural resources, and social and economic value of the nation’s largest estuarine ecosystem and the natural sustainability of its watershed.” Insert new language at end: “We are committed to a future that sustains highly valued ecosystem benefits and makes the region resilient to development pressure.”
Edits. The resulting tape must not be edited by anyone for any purpose whatsoever and may not be copied, with the exception of the tape forwarded to Equity.
Edits. Each translated document may be returned to you once for editing at the sole discretion of Xxxxxx Xxxxxxxxxxx. Edits will be avoided at all costs and are not anticipated except in extreme circumstances. Edits will be performed by you within 72 hours of return, or forfeiture of publishing the document will ensue. Representations and Warranties of Writer. By submitting an Article to Website, Writer represents and warrants that the Article is Writer’s original work, that the Article is not owned by any third party, that the Article is accurate, that the Article has not been obtained by unlawful means, that the Article has not been previously published in any manner or medium, specifically including, but not limited to, print or electronic means, and that publication of the article by Website will not violate any copyright or other intellectual property right of any third party.
Edits. Each of these layers is used by the ECRF to perform a geographic query to determine which Emergency Service Providers are responsible for providing service to a location in the event a selective transfer is desired, to direct an Emergency Incident Data Document to a secondary PSAP for dispatch, or to display the responsible agencies at the PSAP. In addition, Emergency Service Boundaries are used by PSAPs to identify the appropriate entities/first responders to be dispatched. Each Emergency Service Boundary layer may contain one or more polygon boundaries that define the primary emergency services for that geographic area. As new emergency response services are added to, or change in an area, this boundary file will need to be modified accordingly. Communications must be regularly preserved with all fire, law, and emergency medical responders to obtain the information required to maintain updated boundaries. These Emergency Service Boundaries should adhere to the specifications of CAPCOG’s QC systems and have no gaps or overlaps within a topology tolerance of +/- 3 feet. The ESBs can be created by dissolving the Emergency Service Zones polygon data. These items and other geometric relationships are referred to as “topology”, and especially important for NG9-1-1 purposes. In addition, it is very important that all features with identical attribute information are merged into one multipart polygon There MUST be a separate Emergency Service Boundary layer for each type of service. The set of Emergency Service Boundaries MUST include, at a minimum, the following: • Law Enforcement; • Fire; and • Emergency Medical Services (EMS). Other Emergency Service Boundaries MAY include, but are not limited to: • Poison Control; • Forest Service; and • Animal Control.
Edits. Match errors between these datasets that are returned by the quality control systems should be reviewed and corrected accordingly. This could mean either by making corrections to the GIS data or by providing suggested changes to the ALI database. The ALI data are not owned by CAPCOG or PUBLIC AGENCY, but instead by telephone service providers. Suggested edits to the ALI databases should be made by providing Change Requests (CR) via the Intrado 911Net or GIS Director applications
AutoNDA by SimpleDocs
Edits. The resulting recordings must not be edited for any purpose whatsoever.

Related to Edits

  • Review Protocol A narrative description of how the Claims Review was conducted and what was evaluated.

  • Protocols Each party hereby agrees that the inclusion of additional protocols may be required to make this Agreement specific. All such protocols shall be negotiated, determined and agreed upon by both parties hereto.

  • Programming (a) Pursuant to Section 624 of the Cable Act, the Licensee shall maintain the mix, quality and broad categories of Programming set forth in Exhibit 4, attached hereto and made a part hereof. Pursuant to applicable federal law, all Programming decisions, including the Programming listed in Exhibit 4, attached hereto, shall be at the sole discretion of the Licensee.

  • Functionality Customer is entitled to additional functionality previously purchased or bundled with the software if available in the version or update released on or after the start date of the Agreement. Customer acknowledges that certain functionality in current and previous software versions may not be available in future upgrades. Added functionality may require additional paid services (clinical and technical) to configure and support.

  • Interfaces Bellcore’s GR-446-CORE defines the interface between the administration system and LIDB including specific message formats. (Bellcore’s TR-NWP-000029, Section 10)

  • Outputs 8. The objectives and outcomes of this Agreement will be achieved through a range of outputs. The outputs include the:

  • System Upgrades The Connecting Transmission Owner shall procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement. To the extent that design work is necessary in addition to that already accomplished in the Class Year Interconnection Facilities Study for the Interconnection Customer, the Connecting Transmission Owner shall perform or cause to be performed such work. If all the Parties agree, the Interconnection Customer may construct System Upgrade Facilities and System Deliverability Upgrades.

  • Protocol The attached Protocol shall be an integral part of this Agreement.

  • Technical changes The parties agree to make any technical changes that are mutually agreed prior to the collective agreement going out for ratification. The parties on signing this document acknowledge, subject to any subsequent agreed editorial and technical changes, that this reflects the agreements reached in the settlement of the Primary Teachers’ Collective Agreement 2019-2022. Signed in Wellington on 13 June 2019: Xxxx Xxxxxx Advocate for NZEI Te Riu Roa Xxx Xxxxxxxx Advocate for the Secretary for Education Witnessed: Xxxxxxx Xxxxx for NZSTA Attachment A: Elements from Previous Settlements

  • Updates “Updates” are changes that do not require a change to the established Centralized Contract terms and conditions. Updates may include: Centralized Contract changes and updates made in accordance with the previously approved pricing formula (e.g. discount from list price); adding new products or services within the established, previously approved pricing structure; lowering pricing of products or services already on Contract, deleting products or services available through the Centralized Contract, adding product or service that do not fall under the previously established price structure or discounts under the Contract, re-bundled products, and other updates not listed above that are deemed to be in the best interest of the State and do not result in a change to the established Centralized Contract terms and conditions. Updates must be submitted to OGS for review, and must be accompanied by a justification of reasonableness of price if the change results in a change in pricing methodology. OGS will notify Contractor in writing if approved.

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