Time Limit for Claims No Indemnified Party may make a Claim for indemnification under Section 6.1 in respect of any Claim unless notice in writing of the Claim, incorporating a statement setting out in reasonable detail the grounds on which the Claim is based, has been given by the Indemnified Party prior to the expiration of the applicable Survival Period as set forth in Part VI of Appendix B.
Copies of Documents Relating to Title Exceptions Copies of all recorded documents listed as exceptions to title or otherwise referred to in the Additional Mortgage Policy or title report delivered pursuant to clause (iv) or (v) above;
Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.
Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.
Malicious Use of Orphan Glue Records Registry Operator shall take action to remove orphan glue records (as defined at xxxx://xxx.xxxxx.xxx/en/committees/security/sac048.pdf) when provided with evidence in written form that such records are present in connection with malicious conduct.
Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-‐based Directory Service at <whois.nic.TLD> providing free public query-‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry.
1.1. The format of responses shall follow a semi-‐free text format outline below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database.
1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value.
1.3. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together.
1.4. The fields specified below set forth the minimum output requirements. Registry Operator may output data fields in addition to those specified below, subject to approval by ICANN, which approval shall not be unreasonably withheld.
Unpaid Claims If a claim for indemnification (following the final disposition of such action, suit or proceeding) or advancement of expenses under this Section 10.02 is not paid in full within thirty (30) days after a written claim therefor by any person described in Section 10.02(a) has been received by the Partnership, such person may file proceedings to recover the unpaid amount of such claim and, if successful in whole or in part, shall be entitled to be paid the expense of prosecuting such claim. In any such action the Partnership shall have the burden of proving that such person is not entitled to the requested indemnification or advancement of expenses under applicable Law.
Claims relating to Intellectual Property Rights 29.1. The Contractor must not infringe any Intellectual Property Rights of any third party in providing the Services or otherwise performing its obligations under the Framework Agreement and must ensure that the provision of the Services and the use or possession of the Deliverables does not infringe such Intellectual Property Rights.
29.2. The Contractor must promptly notify the Authority if any claim or demand is made or action brought against the Contractor for infringement or alleged infringement of any Intellectual Property Right which may affect the use or possession of the Deliverables or which may affect the provision of the Services.
29.3. Where a claim to which this clause applies is made, the Contractor must, at its expense, use its best endeavours to:
29.3.1. modify the Services or Deliverables or substitute alternative Services or Deliverables (in any case without reducing performance or functionality) so as to avoid the infringement or alleged infringement of the Intellectual Property Rights; or
29.3.2. procure the grant of a licence or licences from the pursuer, claimant or complainer, on terms acceptable to the Authority, so as to avoid the infringement or alleged infringement of the Intellectual Property Rights of the pursuer, claimant or complainer.
29.4. The Contractor must not without the consent of the Authority make any admissions which may be prejudicial to the defence or settlement of any claim to which this clause applies.
Contract (Rights of Third Parties) Xxx 0000 22.1 No person who is not a party to this Grant Agreement shall have the right to enforce any of its terms.
Paid Claims without Supporting Documentation Any Paid Claim for which Xxxxxxx cannot produce documentation shall be considered an error and the total reimbursement received by Xxxxxxx for such Paid Claim shall be deemed an Overpayment. Replacement sampling for Paid Claims with missing documentation is not permitted.
