Test Registration Outcome Sample Clauses

Test Registration Outcome. The test has finished successfully with the following details: Correctness of response (semantically)
AutoNDA by SimpleDocs
Test Registration Outcome. The test has finished successfully with the following details: Correctness of response (semantically) Accepted. - The response of the system has been { traffic, verkehr, verkeer } as expected. It should be noticed that the TRN has only been storing a very limited number of entries in the test. In real world scenarios, terms should be imported from existing terminology repositories. Correctness of data format (syntactically) Accepted. – The output format has been returned correctly and was compliant to the W3C specification: <?xml version='1.0' encoding='UTF-8'?> <sparql xmlns='xxxx://xxx.x0.xxx/2005/sparql-results#'> <head> <variable name='subject'/> <variable name='name'/> <variable name='language'/> <variable name='languagecode'/> </head> <results> <result> <binding name='language'> <uri>xxxx://xxx.xxx.xx/egovshare/trn.owl#enus</uri> </binding> <binding name='languagecode'> <literal datatype='xxxx://xxx.x0.xxx/2001/XMLSchema#string'>US</literal> </binding> <binding name='subject'> <uri>xxxx://xxx.xxx.xx/egovshare/trn.owl#Term20</uri> </binding> <binding name='name'> <literal datatype='xxxx://xxx.x0.xxx/2001/XMLSchema#string'>Traffic</literal> </binding> </result> <result> <binding name='language'> <uri>xxxx://xxx.xxx.xx/egovshare/trn.owl#dede</uri> </binding> <binding name='languagecode'> <literal datatype='xxxx://xxx.x0.xxx/2001/XMLSchema#string'>DE</literal> </binding> <binding name='subject'> <uri>xxxx://xxx.xxx.xx/egovshare/trn.owl#Term21</uri> </binding> <binding name='name'> <literal datatype='xxxx://xxx.x0.xxx/2001/XMLSchema#string'>Verkehr</literal> </binding> </result> <result> <binding name='language'> <uri>xxxx://xxx.xxx.xx/egovshare/trn.owl#nlnl</uri> </binding> <binding name='languagecode'> <literal datatype='xxxx://xxx.x0.xxx/2001/XMLSchema#string'>NL</literal> </binding> <binding name='subject'> <uri>xxxx://xxx.xxx.xx/egovshare/trn.owl#Term21</uri> </binding> <binding name='name'> <literal datatype='xxxx://xxx.x0.xxx/2001/XMLSchema#string'>Verkeer</literal> </binding> </result> </results> </sparql> Speed of response

Related to Test Registration Outcome

  • NERC Registration If and to the extent any of the NTO’s facilities are NERC jurisdictional facilities, the ISO will register for certain NERC functions applicable to those NTO facilities. Such functions may include, without limitation, those functions designated by NERC to be “Reliability Coordinator” and “Balancing Authority” and “Transmission Planner” and “Planning Coordinator.” The Parties agree to negotiate in good faith the compliance obligations for the NERC functions applicable to, and to be performed by, each Party with respect to the NTO’s facilities. Notwithstanding the foregoing, the ISO shall register for the “Transmission Operator” function for all NTO Transmission Facilities under ISO Operational Control identified in Appendix A-1 of this Agreement.

  • Account Registration (a) Custodian shall open and maintain one or more custody accounts in the name of Customer and shall act pursuant to the terms of this Agreement. Each such account opened and maintained by Custodian shall be referred to herein as a “

  • Domain Name Registration If Customer submits a Service Order(s) for domain name registration services, the following terms shall also apply:

  • Service Registration Certain of our Services require you to register to use them. In such case, you agree that a l information you provide is truthful, current and complete. If there is any change to your registration information, you agree to provide us with updated information immediately. To the extent any of the Services are password protected, you agree to keep such password confidential and not to share it with any third party. You also agree that you wil not access any Services for which a password is required by using any third party’s password. If you discover any use of your password other than by you, you agree to immediately notify us. If you become aware of unauthorized account access, you similarly agree to immediately notify us. At the end of any use of a password protected Service, you agree to exit and logout out of your user session. Under no circumstances sha l we be responsible for any loss or damage that may result if you fail to comply with these requirements.

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

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

  • Registration Process In connection with the registration of the Registrable Securities pursuant to Section 4.1, the Company shall:

  • Registration of Contractor All contractors and subcontractors must comply with the requirements of Labor Code Section 1771.1(a), pertaining to registration of contractors pursuant to Section 1725.5. Bids cannot be accepted from unregistered contractors except as provided in Section 1771.1. This project is subject to compliance monitoring and enforcement by the Department of Industrial Relations. After award of the contract, Contractor and each Subcontractor shall furnish electronic payroll records directly to the Labor Commissioner in the manner specified in Labor Code Section 1771.4.

  • Registration of Contractors Contractor and all subcontractors must comply with the requirements of labor code section 1771.1(a), pertaining to registration of contractors pursuant to section 1725.5. Registration and all related requirements of those sections must be maintained throughout the performance of the Contract.

  • DIR Registration California Labor Code Section 1725.5 requires the Contractor and all subcontractors performing Public Works services to be currently registered with the DIR, as specified in California Labor Code Section 1725.5. California Labor Code Section 1771.1 provides that a contractor or subcontractor shall not be qualified to bid on, be listed in a bid proposal (subject to the requirements of Section 4104 of the California Public Contract Code), or engage in the performance of any contract for Public Work, unless currently registered and qualified to perform Public Work in accordance with California Labor Code Section 1725.5. Further information can be found on DIR’s website at xxxx://xxx.xxx.xx.xxx/Public-Works/Contractors.html. The above summary is provided solely for informational purposes and does not in any way affect the Contractor’s and subcontractors’ obligation to comply in all respects with all other applicable laws and regulations. The Contractor shall disseminate these provisions to all subcontractors. Before the performance of work by Contractor or any subcontractor(s) under this Contract, Contractor shall furnish Contractor’s and any subcontractors’ current DIR registration number(s). The Contractor’s current DIR registration number and the current DIR registration number of all subcontractors will be listed on the Subcontractor and LBE Participation Verification Form, incorporated herein.

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