Time Limit for Student Body Registration and Hall Information Day. 1. Zone 1 The maximum duration for new students shall not exceed 2.5 hours, while that for students enrolled in double-degree programmes shall not exceed 5 hours.
Time Limit for Student Body Registration and Hall Information Day Sample Clauses
Related to Time Limit for Student Body Registration and Hall Information Day
Periodic Access to Thin Registration Data In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-‐to-‐date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.
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.
Why We Collect Information and For How Long We are collecting your data for several reasons: · To better understand your needs and provide you with the services you have requested; · To fulfill our legitimate interest in improving our services and products; · To send you promotional emails containing information we think you may like when we have your consent to do so; · To contact you to fill out surveys or participate in other types of market research, when we have your consent to do so; · To customize our website according to your online behavior and personal preferences. The data we collect from you will be stored for no longer than necessary. The length of time we retain said information will be determined based upon the following criteria: the length of time your personal information remains relevant; the length of time it is reasonable to keep records to demonstrate that we have fulfilled our duties and obligations; any limitation periods within which claims might be made; any retention periods prescribed by law or recommended by regulators, professional bodies or associations; the type of contract we have with you, the existence of your consent, and our legitimate interest in keeping such information as stated in this Policy.
Publication of Registration Data Registry Operator shall provide public access to registration data in accordance with Specification 4 attached hereto (“Specification 4”).
Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.
Review Procedures for Identifying Entity Accounts With Respect to Which Reporting Is Required For Preexisting Entity Accounts described in paragraph B of this section, the Reporting Finnish Financial Institution must apply the following review procedures to determine whether the account is held by one or more Specified U.S. Persons, by Passive NFFEs with one or more Controlling Persons who are U.S. citizens or residents, or by Nonparticipating Financial Institutions:
Registration Data Upon placing an order for Pilot Voice, and at subsequent times as requested by Pilot, Customer agrees to provide Pilot with its (i) true, accurate, current, and complete business name, (ii) physical addresses where Voice Service will be used, (iii) 911 registered address for each applicable endpoint, (iv) a designated Account Administrator, and (v) user email addresses, phone numbers, and any other requested data which may be necessary to administer its Voice Service account (the “Account”) (collectively, “Registration Data”). Customer represents and warrants that the information it provides is accurate, current, and complete, and agrees to promptly update any of the information if it changes. If Customer provides Registration Data that is false, inaccurate, not current, incomplete, fraudulent, or otherwise unlawful, Pilot has the right, in its sole discretion, to suspend or terminate the Voice Services and refuse any and all current or future use of all Voice Services by Customer, its business(es), affiliates and all users of its Account. Upon provision of all Registration Data and acceptance of Customer’s Service Order, Pilot may provide Customer’s designated Account Administrator and other Pilot Voice users with, as applicable, administrator or user web portal logins and other Account information. Customer is solely liable for any transactions or activities by it or any third- party that occurs on its Account. Customer shall immediately notify Pilot of any unauthorized use of its Account or if any other breach of security has occurred. In no event shall Pilot be liable for any unauthorized, third-party use of your Account.
Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-‐to-‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.
Information Transfer and Storage Supplier will use Industry Standard encryption to encrypt Accenture Data that is in transit. Supplier will also use Industry Standard encryption to restrict access to Accenture Data stored on physical media that is transported outside of Supplier facilities.
NYS OFFICE OF INFORMATION TECHNOLOGY SERVICES NOTIFICATION All New York State Agencies must notify the Office of Information Technology Services of any and all plans to procure IT and IT -related products, materials and services meeting required thresholds defined in Technology Policy NYS–P08-001: xxxxx://xxx.xx.xxx/sites/default/files/documents/NYS-P08-001.pdf, as may be amended, modified or superseded. SALES REPORTING REQUIREMENTS Contractor shall furnish OGS with quarterly sales reports utilizing Appendix I - Report of Contract Sales. Purchases by Non- State Agencies, political subdivisions and others authorized by law shall be reported in the same report and indicated as required. All fields of information shall be accurate and complete. OGS reserves the right to unilaterally make revisions, changes and/or updates to Appendix I - Report of Contract Sales or to require sales to be reported in a different format without processing a formal amendment and/or modification. Further, additional related sales information and/or detailed Authorized User purchases may be required by OGS and must be supplied upon request. Reseller Sales Product sold through Reseller(s) must be reported by Contractor in the required Appendix I – Report of Contract Sales. Due Date The Appendix I - Report of Contract Sales will be quarterly (January - March, April - June, July - September and October - December). Reports will be due 1 month after the closing quarter. SERVICE REPORTS FOR MAINTENANCE/SUPPORT AND WARRANTY WORK Service Reports for Authorized User An Authorized User in an RFQ may require compliance with any or all of this section. If requested by the Authorized User, the Contractor shall furnish the Authorized User with service reports for all Maintenance/support and warranty work upon completion of the services. The service reports may include the following information in either electronic or hard copy form as designated by the Authorized User: Date and time Contractor was notified Date and time of Contractor’s arrival Make and model of the Product Description of malfunction reported by Authorized User Diagnosis of failure and/or work performed by Contractor Date and time failure was corrected by Contractor Type of service – Maintenance/support or warranty Charges, if any, for the service Service Reports for OGS
