Unauthorised use We shall not be liable for any loss, liability or cost whatsoever arising from any unauthorised use of the Electronic Service. You shall on demand indemnify, protect and hold us harmless from and against all losses, liabilities, judgements, suits, actions, proceedings, claims, damages and costs resulting from or arising out of any act or omission by any person using an Electronic Service by using your designated passwords, whether or not you authorised such use.
Unauthorized Access Using service to access, or to attempt to access without authority, the accounts of others, or to penetrate, or attempt to penetrate, security measures of Company’s or a third party’s computer software or hardware, electronic communications system, or telecommunications system, whether or not the intrusion results in disruption of service or the corruption or loss of data.
Unauthorized Work The contractor is not authorized at any time to commence task order performance prior to issuance of a signed TO or other written approval provided by the CO to begin work.
Authorised Users individuals who are authorised by the Institution to access the Institution's information services whether on-site or off-site via Secure Authentication and who are affiliated to the Institution as a current student (including but not limited to undergraduates, postgraduates and guest students), member of staff (whether on a permanent or temporary basis including retired members of staff and any teacher who teaches Authorised Users) or contractor or registered user of the Institution. Persons who are not currently a student, member of staff, contractor or registered user of the Institution, but who are permitted to access the Institution's information services from computer terminals or otherwise within the physical premises of the Institution ["Walk-In Users"] are also deemed to be Authorised Users, only for the time they are within the physical premises of the Institution.
Unauthorized Leave Leave other than that provided for in this section may be cause for disciplinary action.
Unauthorised Use of Intellectual Property a) The Supplier/Service Provider agrees to notify Transnet in writing of any conflicting uses of, and applications of registrations of Patents, Designs and Trade Marks or any act of infringement, unfair competition or passing off involving the Intellectual Property of Transnet of which the Supplier/Service Provider acquires knowledge and Transnet shall have the right, as its own option, to proceed against any party infringing its Intellectual Property.
b) It shall be within the sole and absolute discretion of Transnet to determine what steps shall be taken against the infringer and the Supplier/Service Provider shall co-operate fully with Transnet, at Transnet’s cost, in whatever measure including legal action to bring any infringement of illegal use to an end.
c) The Supplier/Service Provider shall cooperate to provide Transnet promptly with all relevant ascertainable facts.
d) If proceedings are commenced by Transnet alone, Transnet shall be responsible for all expenses but shall be entitled to all damages or other awards arising out of such proceedings. If proceedings are commenced by both Parties, both Parties will be responsible for the expenses and both Parties shall be entitled to damages or other awards arising out of proceedings.
CONTRACTOR INVOICE Contractor shall submit to Purchaser’s designated invoicing contact properly itemized invoices. Such invoices shall itemize the following:
(a) Master Contract No. 02120
(b) Contractor name, address, telephone number, and email address for billing issues (i.e., Contractor Customer Service Representative)
(c) Contractor’s Federal Tax Identification Number
(d) Date(s) of delivery
(e) Invoice amount; and
(f) Payment terms, including any available prompt payment discounts. Contractor’s invoices for payment shall reflect accurate Master Contract prices. Invoices will not be processed for payment until receipt of a complete invoice as specified herein.
Name Collision Occurrence Assessment 6.2.1 Registry Operator shall not activate any names in the DNS zone for the Registry TLD except in compliance with a Name Collision Occurrence Assessment provided by ICANN regarding the Registry TLD. Registry Operator will either (A) implement the mitigation measures described in its Name Collision Occurrence Assessment before activating any second-‐level domain name, or (B) block those second-‐level domain names for which the mitigation measures as described in the Name Collision Occurrence Assessment have not been implemented and proceed with activating names that are not listed in the Assessment.
6.2.2 Notwithstanding subsection 6.2.1, Registry Operator may proceed with activation of names in the DNS zone without implementation of the measures set forth in Section 6.2.1 only if (A) ICANN determines that the Registry TLD is eligible for this alternative path to activation of names; and (B) Registry Operator blocks all second-‐level domain names identified by ICANN and set forth at <xxxx://xxxxxxxx.xxxxx.xxx/en/announcements-‐and-‐ media/announcement-‐2-‐17nov13-‐en> as such list may be modified by ICANN from time to time. Registry Operator may activate names pursuant to this subsection and later activate names pursuant to subsection 6.2.1.
6.2.3 The sets of names subject to mitigation or blocking pursuant to Sections 6.2.1 and 6.2.2 will be based on ICANN analysis of DNS information including "Day in the Life of the Internet" data maintained by the DNS Operations, Analysis, and Research Center (DNS-‐OARC) <xxxxx://xxx.xxx-‐xxxx.xxx/xxxx/xxxx/xxxx>.
6.2.4 Registry Operator may participate in the development by the ICANN community of a process for determining whether and how these blocked names may be released.
6.2.5 If ICANN determines that the TLD is ineligible for the alternative path to activation of names, ICANN may elect not to delegate the TLD pending completion of the final Name Collision Occurrence Assessment for the TLD, and Registry Operator’s completion of all required mitigation measures. Registry Operator understands that the mitigation measures required by ICANN as a condition to activation of names in the DNS zone for the TLD may include, without limitation, mitigation measures such as those described in Section 3.2 of the New gTLD Name Collision Occurrence Management Plan approved by the ICANN Board New gTLD Program Committee (NGPC) on 7 October 2013 as found at <xxxx://xxx.xxxxx.xxx/en/groups/board/documents/resolutions-‐ new-‐gtld-‐annex-‐1-‐07oct13-‐en.pdf>.
Authorised Representatives Each of the Parties shall by notice in writing designate their respective authorised representatives through whom only all communications shall be made. A Party hereto shall be entitled to remove and/or substitute or make fresh appointment of such authorised representative by similar notice.
Authorised Representative The Issuer will notify the Dealers immediately in writing if any of the persons named in the list referred to in paragraph 3 of Part 1 of the Initial Documentation List ceases to be authorised to take action on its behalf or if any additional person becomes so authorised together, in the case of an additional authorised person, with evidence satisfactory to the Dealers that such person has been so authorised.
