URL parameters Sample Clauses

URL parameters. URL parameter name Description maxObjectCount Specifies how many objects are invoked through a response. An object is one instance that contains multiple properties. maxDepth Specifies the expansion depth of the global object. This value starts from 0, and the default value is 1. Take the Host object as an example: • If the max depth is 0, the Host name and Host unique ID are returned. • If the max depth is 1, the first-level properties of the Host are returned. durationMS Specifies the time duration, including startTimeMS and endTime. If startTimeMS is not set, the endTime value is used as the current time, and the startTime value is calculated as endTime minus the specified duration.
Sample 1Sample 2Sample 3See All (5)
AutoNDA by SimpleDocs
URL parameters. For Orbitz to attribute Bookings to Clicks, the System must be able to identify the source of the lead as Kayak or otherwise. Unique tracking parameters in the URL of leads to Orbitz from a Kayak Site will designate Kayak as the source. The System must provide tracking parameters to Kayak and Kayak will include these in the linking URLs for all Kayak leads to Orbitz.
Sample 1Sample 2
URL parameters. Do not pass user identifiable information as URL parameters, as this causes them to be logged in the http logfiles. (And also sends this information in the clear if you forget to use SSL.) Instead, use hidden form fields or cookies or encrypted session IDs.
Sample 1

Related to URL parameters

  • Parameters In calculating the MtM Exposure for each Transaction, the following parameters are set on the Transaction Date: ▪ On-Peak Initial Xxxx Xxxxx ▪ Off-Peak/On-Peak Price Ratio ▪ Off-Peak Initial Xxxx Xxxxx ▪ MW-Measure: initial Capacity PLC Per Tranche ▪ On-Peak Estimated Energy Quantity Per MW-Measure for each of the twelve calendar months ▪ Off-Peak Estimated Energy Quantity Per MW-Measure for each of the twelve calendar months ▪ Number of awarded Tranches In calculating the MtM Exposure for each Transaction, the following parameters are set each Trading Day subsequent to the Transaction Date: ▪ On-Peak Forward Price ▪ Off-Peak Forward Price ▪ Current Capacity PLC Per Tranche ▪ On-Peak Estimated Energy Quantity ▪ Off-Peak Estimated Energy Quantity Process to Update the On-Peak Initial Mark Prices and Off-Peak Initial Mark Prices on a Daily Basis On each Trading Day subsequent to the Transaction Date, the Pricing Agent will contact four Reference Market-Makers to obtain price quotes for on-peak and off-peak energy for PJM Western Hub. The Pricing Agent may not rely upon quotes from Seller or any Affiliate of Seller. The updated mark for a month will be equal to the average mark for that month over all sources from which a quote is available. If a monthly quote is available from any source, only the monthly quote or monthly quotes shall be used. Where quotes provide a bid and ask, the average shall be used. Where a quote for an individual month is unavailable, but the month is quoted as part of a “packaged” quote (e.g., January 2011 is only available in the form of a January/February 2011 “packaged” quote or an annual quote): ▪ If the other month/months of the package quote is/are also unavailable, then the marks for all months of the package will be calculated by multiplying the packaged quote by the ratio of the corresponding month to the corresponding calculated package quote from the previous day. Example: There are no On-Peak quotes available on day X during the contract for July 2011 or August 2011. However, there is an On-Peak July/August 2011 packaged quote of $73.00/MWh available. The On-Peak marks from day X-1 for July 2011 and August 2011 were $73.50/MWh and $76.50/MWh respectively. The day X On-Peak mark for July 2011 is set at 73.00 * [73.50] / [( (73.50 * 352) + (76.50 * 336) ) / (352+336) ] = 73 * (73.50/ 74.97) = $71.57/MWh. The day X On-Peak mark for August 2011 is set at 73.00 * [76.50] / [( (73.50 * 352) + (76.50*336) ) / (352+336) ] = 73 * (76.50 / 74.97) = $74.49/MWh. ▪ If the other month/months of the package quote is/are available, then the mark for the month will be set such that the average of the month and the other month(s) (weighted for either the On-Peak Hours or Off-Peak Hours as applicable) equals the packaged quote (see calculation example below).

  • Measuring DNS parameters Every minute, every DNS probe will make an UDP or TCP “DNS test” to each of the public-­‐DNS registered “IP addresses” of the name servers of the domain name being monitored. If a “DNS test” result is undefined/unanswered, the tested IP will be considered unavailable from that probe until it is time to make a new test.

  • Measuring EPP parameters Every 5 minutes, EPP probes will select one “IP address” of the EPP servers of the TLD being monitored and make an “EPP test”; every time they should alternate between the 3 different types of commands and between the commands inside each category. If an “EPP test” result is undefined/unanswered, the EPP service will be considered as unavailable from that probe until it is time to make a new test.

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

  • Technical Specifications 1. A procuring entity shall not prepare, adopt or apply any technical specification or prescribe any conformity assessment procedure with the purpose or effect of creating an unnecessary obstacle to trade between the Parties.

  • Changes to Specifications All Specifications and any changes thereto agreed to by the Parties from time to time shall be in writing, dated and signed by the Parties. No change in the Specifications shall be implemented by Cardinal Health, whether requested by Reliant or requested or required by any Regulatory Authority, until the Parties have agreed in writing to such change, the implementation date of such change, and any increase or decrease in costs, expenses or fees associated with such change. Cardinal Health shall respond promptly to any request made by Reliant for a change in the Specifications, and both Parties shall use commercially reasonable, good faith efforts to agree to the terms of such change in a timely manner. If after initial Product qualification, Reliant requests a change in the Specifications for its own benefit or to comply with the requirements of a Regulatory Authority, the Specifications shall be amended as soon as [***]: Certain information on this page has been omitted and filed separately with the Commission. Confidential treatment has been requested with respect to the omitted portions. possible after a request is made for any change in Specifications, and Cardinal Health shall notify Reliant of the costs associated with such change and shall provide such supporting documentation as Reliant may reasonably require. Reliant shall pay all costs associated with such Reliant-requested changes or changes required by a Regulatory Authority as may be agreed upon by the Parties. Changes, agreed to between the Parties, for the benefit of Cardinal Health, shall be at the expense of Cardinal Health. If there is a conflict between the terms of this Agreement and the terms of the Specifications, this Agreement shall control.

  • Configuration The configuration for the Purchase Right Aircraft will be the Detail Specification for Model 767-3S2F aircraft at the revision level in effect at the time of the Supplemental Agreement. Such Detail Specification will be revised to include (i) changes required to obtain required regulatory certificates and (ii) other changes as mutually agreed upon by Boeing and Customer.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • Equipment Specifications All equipment must meet the contract specifications and all federal and State safety codes and regulations in effect at the date of manufacture. All equipment must be Original Equipment Manufacturer (OEM) equipment unless otherwise stated in the contract. Items Offered as New. All products, materials, supplies, replacement parts, and equipment offered and furnished must be new, of current manufacturer production, and must have been formally announced by the manufacturer as being commercially available, unless otherwise stated in this Contract.

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