Web Service Agreement Specification Sample Clauses

Web Service Agreement Specification. (WS-Agreement) ñ (Xxxxxxxx et al., 2005). The Global Grid Forum (GGF) published the Web Service Agreement specification (WS-Agreement), which is an XML variant for specifying an agreement between a service provider and a consumer, and a protocol for creation of an agreement using agreement templates. The objective of the WS-Agreement draft specification is to provide an organization independent and standard way to establish and monitor SLAs. Another objective of WS-Agreement is that it should be interoperable with other negotiation protocols. The specification comprises three major elements: (i) a description format for agreement templates and agreements, (ii) a basic protocol for establishing agreements, and (iii) an interface specification to monitor agreements at runtime (Wieder et al., 2006). In the WS-Agreement specification, an agreement between a service consumer and a service provider specifies one or more Service Level Objectives (SLOs) which state the requirements and capabilities of each party on the availability of resources and service qualities. For example, an agreement may provide assurances on the bounds of service response time, service availability, or service reliability. WS-Agreement also specifies a very simple negotiation protocol. More of a ìtake it or leave itî protocol, that does not allow offer refinement (see Figure 3.8 for the Interaction Model). This is a very limited interaction model as a result it limits consumer expressiveness immensely. WS-Agreement defines three types of documents: Agreement templates, Offer and Agreement. A service provider publishes an agreement template for the services provided. The template may contain service characteristics, guarantees, as well as creating constraints, which would specify the desirable range of some values. A consumer would retrieve and xxxxx in the template.î The filled template is sent as an offer to the provider. The provider checks the offer against the template to make sure that there is compliance and decides whether to accept or reject depending on his capacity.
AutoNDA by SimpleDocs

Related to Web Service Agreement Specification

  • Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

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

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

  • Product Specifications (a) Supplier shall manufacture all Products according to the Specifications in effect as of the date of this Agreement, with such changes or additions to the Specifications of the Products related thereto as shall be requested by Buyer in accordance with this Section or as otherwise agreed in writing by the Parties. All other Products shall be manufactured with such Specifications as the Parties shall agree in writing. (b) Buyer may request changed or additional Specifications for any Product by delivering written notice thereof to Supplier not less than one hundred twenty (120) days in advance of the first Firm Order for such Product to be supplied with such changed or additional Specifications. Notwithstanding the foregoing, if additional advance time would reasonably be required in order to implement the manufacturing processes for production of a Product with any changed or additional Specifications, and to commence manufacture and delivery thereof, Supplier shall so notify Buyer, and Supplier shall not be required to commence delivery of such Product until the passage of such additional time. (c) Supplier shall be required to accommodate any change of, or additions to, the Specifications for any Product, if and only if (i) in Supplier’s good faith judgment, such changed or additional Specifications would not require Supplier to violate good manufacturing practice, (ii) the representation and warranty of Buyer deemed made pursuant to Subsection (e) below is true and correct, and (iii) Buyer agrees to reimburse Supplier for the incremental costs and expenses incurred by Supplier in accommodating the changed or additional Specifications, including the costs of acquiring any new machinery and tooling. For the avoidance of doubt, such costs and expenses shall be payable by Buyer separately from the cost of Products at such time or times as Supplier shall request. (d) Supplier shall notify Buyer in writing within thirty (30) days of its receipt of any request for changed or additional Specifications (i) whether Supplier will honor such changed or additional Specifications, (ii) if Supplier declines to honor such changed or additional Specifications, the basis therefor and (iii) if applicable, the estimated costs and expenses that Buyer will be required to reimburse Supplier in respect of the requested changes or additions, as provided in Subsection (c) above. Buyer shall notify Supplier in writing within fifteen (15) days after receiving notice of any required reimbursement whether Buyer agrees to assume such reimbursement obligation. (e) By its request for any changed or additional Specifications for any Product, Buyer shall be deemed to represent and warrant to Supplier that the manufacture and sale of the Product incorporating Buyer’s changed or additional Specifications, as a result of such incorporation, will not and could not reasonably be expected to (i) violate or conflict with any contract, agreement, arrangement or understanding to which Buyer and/or any of its Affiliates is a party, including this Agreement and any other contract, agreement, arrangement or understanding with Supplier and/or its Affiliates, (ii) infringe on any trademark, service xxxx, copyright, patent, trade secret or other intellectual property rights of any Person, or (iii) violate any Applicable Law. Buyer shall indemnify and hold Supplier and its Affiliates harmless (including with respect to reasonable attorneys’ fees and disbursements) from any breach of this representation and warranty.

  • ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

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

  • Packing Specifications 7.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • Statement of Work The Statement of Work to which Grantee is bound is incorporated into and made a part of this Grant Agreement for all purposes and included as Attachment A.

  • MSAA Indicator Technical Specification Document This Agreement shall be interpreted with reference to the MSAA Indicator Technical Specifications document.

  • Quality Specifications SANMINA-SCI shall comply with the quality specifications set forth in its Quality Manual, incorporated by reference herein, a copy of which is available from SANMINA-SCI upon request.

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