Loopholes Sample Clauses

Loopholes. A. Contractor recognizes that by performing Services under this Agreement, Contractor may become aware of methods by which Market Participants could manipulate or “game” the ERCOT system ("Loopholes") and thereby take unethical advantage of the ERCOT system. B. Contractor agrees that to the extent Contractor becomes aware of such information, it will promptly notify a member of ERCOT management of the existence of such Loopholes and that it will treat such information as Confidential Information.
Sample 1Sample 2Sample 3See All (9)
AutoNDA by SimpleDocs
Loopholes. There are times when loopholes seem to be the only source of true innovation in the DNS – it was a loophole in the RAA that allowed for the marketing of proxy registration services; it was loopholes in the accreditation process that allowed for the creation of “phantom registrars” that only exist as a device to gain access to the deleted names pool. Loopholes can allow for future gaming of the new gTLD LandRush cycles, they can inhibit enforcement activities, and they can cripple dispute resolution to the point that a “walking dead” registrar can seriously impact the registrant community. Loopholes can become the bane of our community… and they are not easy to spot. When the proposed revised RAA is published, the document will need to be examined under a microscope. It will require a dedicated team to analyze the implications of each clause and paragraph. While the registrars and ICANN have been “reviewing” the RAA since 2005, those of us that hail from the at-large world have never before attempted a comprehensive review of this legal document. With that thought in mind, perhaps we can take some guidance from the instructions given to the registrar constituency by their Chair back in 2005 when Review issues first arose: Hi all, ICANN is currently reviewing the RAA and intends to make changes and come up with a new RAA by Xxxx. This is very important to all of us from the following perspectives - * to merge some of the consensus policies into the RAA * to come up with alternative options to enforce compliance for Registrars who are not currently in compliance with their RAA (such as for instance a contractual provision that would allow ICANN to temporarily suspend ADDs of a Registrar if they are not in compliance) * there have been a few circumstances highlighted in the ICANN Contracts which conflict with local law in other countries such as Germany. There maybe possible changes that could be made to the RAA to circumvent those I would ask everyone in the Registrars Constituency to sit with a copy of the RAA and a marker and highlighting other areas that ICANN should review, this maybe an opportunity for us to give feedback on certain contractual modifications that the RAA should have which would benefit us as a community. Couple of areas that we could look at are - - Compliance Any feedback that you may have on suggestions in the RAA review process - send them out to the list. If you wish to send them directly to ICANN – feel free to send them to Xxx Xxxx...
Sample 1

Related to Loopholes

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

  • Architecture The Private Improvements shall have architectural features, detailing, and design elements in accordance with the Project Schematic Drawings. All accessory screening walls or fences, if necessary, shall use similar primary material, color, and detailing as on the Private Improvements.

  • Unbundled Channelization (Multiplexing) 5.7.1 To the extent NewPhone is purchasing DS1 or DS3 or STS-1 Dedicated Transport pursuant to this Agreement, Unbundled Channelization (UC) provides the optional multiplexing capability that will allow a DS1 (1.544 Mbps) or DS3 (44.736 Mbps) or STS-1 (51.84 Mbps) Network Elements to be multiplexed or channelized at a BellSouth central office. Channelization can be accomplished through the use of a multiplexer or a digital cross-connect system at the discretion of BellSouth. Once UC has been installed, NewPhone may request channel activation on a channelized facility and BellSouth shall connect the requested facilities via COCIs. The COCI must be compatible with the lower capacity facility and ordered with the lower capacity facility. This service is available as defined in NECA 4. 5.7.2 BellSouth shall make available the following channelization systems and interfaces: 5.7.2.1 DS1 Channelization System: channelizes a DS1 signal into a maximum of twenty- four (24)

  • Elements Defines the individual components under each indicator

  • Interfaces GTE provides the CLECs with choices for access to OSS pre-ordering, ordering, maintenance and repair systems. Availability of the interfaces is fundamental to the CLEC being able to effectively do business with GTE. Additionally, in many instances, CLEC personnel must work with the service personnel of GTE. Measurements in this category assess the availability to the CLECs of systems and personnel at GTE work centers.

  • Compatibility 1. Any unresolved issue arising from a mutual agreement procedure case otherwise within the scope of the arbitration process provided for in this Article and Articles 25A to 25G shall not be submitted to arbitration if the issue falls within the scope of a case with respect to which an arbitration panel or similar body has previously been set up in accordance with a bilateral or multilateral convention that provides for mandatory binding arbitration of unresolved issues arising from a mutual agreement procedure case. 2. Nothing in this Article and Articles 25A to 25G shall affect the fulfilment of wider obligations with respect to the arbitration of unresolved issues arising in the context of a mutual agreement procedure resulting from other conventions to which the Contracting States are or will become parties.”.

  • Interoperability To the extent required by applicable law, Cisco shall provide You with the interface information needed to achieve interoperability between the Software and another independently created program. Cisco will provide this interface information at Your written request after you pay Cisco’s licensing fees (if any). You will keep this information in strict confidence and strictly follow any applicable terms and conditions upon which Cisco makes such information available.

  • Firmware 7.1 The Supplier must deliver the equipment, Goods or hardware equipped with all the firmware required to use all the Goods or hardware’s functions. Any software embedded in the equipment, Goods or hardware, including the firmware, is provided to the Local Government with a license to use this software, with all license costs and royalties being included in the Fee Schedule (Schedule C). All firmware will be the most recent version available at the time of shipping.

  • Weapons We have a zero tolerance of the possession of weapons (sword, knives etc) or firearms (guns etc) in the Room, Building or Common Property. If You are found in possession of weapons, firearms or implements associated with their use in the Room, Building or Common Property We will immediately terminate this agreement and inform the relevant UNSW and legal authorities.

  • Components Patheon will purchase and test all Components (with the exception of Client-Supplied Components) at Patheon’s expense and as required by the Specifications.

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