Consistent URL Sample Clauses

Consistent URL. As all the components expose a RESTful interface, all references to records within the system should conform to a consistent URL pattern. The pattern is: /<module>/<provider>/<Set, Group, Batch>/<action>/<record id>?parameters Where: <module> is the root path for the module being called (eg. Set, PIDGeneration, Validation, Preview/Template) <provider> is the provider code for the owner of the record(s) <Set, Group, Batch> is the set / group or batch the record(s) belongs to <action> is the action to be performed, which will obviously vary between modules <record id> is the id of the record that an action needs to be performed against, this will not be required for all actions, for some modules this may not be required at all. If a single record is supplied as a parameter then it is assumed to be a single operation and the result is expected to be returned immediately. If a zip file is supplied then it is assumed to be a batch operation, the module will return immediately with the http code 202 (Accepted). Once a batch has been accepted then the action “status” can be called on that batch to retrieve the status of the operation (complete, in progress, queued etc.). When the status action reports that the batch operation has been completed a “fetch” action can be performed against the batch to retrieve the results in a zip file. It could be that even though only 1 record is supplied the module might want to treat it as a batch operation in which case the client will need to accept this. If batch is not supported by the module, then it should return the http error code 501 (Not Implemented). To obtain statistics form a module then the action “statistics” can be used, if the module has used the statistics module to store its statistics then the information can be retrieved from there, otherwise it will need to manage its statistics in some manner, if statistics are not supported by the module then it should return the http error code 501.
Sample 1
AutoNDA by SimpleDocs

Related to Consistent URL

  • Consistent Application The Employer agrees that management rights will not be exercised in a manner inconsistent with the express provisions of this Agreement.

  • Principles of cooperation The Parties shall apply the following principles to cooperation activities covered by this Agreement:

  • PRINCIPLES OF GOOD EMPLOYMENT PRACTICE The Supplier shall, and shall procure that each Sub-Contractor shall, comply with any requirement notified to it by the Customer relating to pensions in respect of any Transferring Former Supplier Employee as set down in: the Cabinet Office Statement of Practice on Staff Transfers in the Public Sector of January 2000, revised 2007; HM Treasury's guidance “Staff Transfers from Central Government: A Fair Deal for Staff Pensions of 1999; HM Treasury's guidance: “Fair deal for staff pensions: procurement of Bulk Transfer Agreements and Related Issues” of June 2004; and/or the New Fair Deal. Any changes embodied in any statement of practice, paper or other guidance that replaces any of the documentation referred to in Paragraph 5.1 shall be agreed in accordance with the Variation Procedure.

  • Technical Standards Applicable to a Wind Generating Plant i. Low Voltage Ride-Through (LVRT) Capability A wind generating plant shall be able to remain online during voltage disturbances up to the time periods and associated voltage levels set forth in the standard below. The LVRT standard provides for a transition period standard and a post-transition period standard.

  • COVID-19 Protocols Contractor will abide by all applicable COVID-19 protocols set forth in the District’s Reopening and COVID-19 Mitigation Plan and the safety guidelines for COVID-19 prevention established by the California Department of Public Health and the Ventura County Department of Public Health.

  • PRINCIPLES OF COLLABORATION The parties agree to adopt the following principles when carrying out the Project (Principles):

  • RESTOCKING (EXCHANGES AND RETURNS) There will be no restocking charge to the Customer for return or exchange of any item purchased under the terms of any award. If the Customer wishes to return items purchased under an awarded contract, the Contractor agrees to exchange, these items for other items, with no additional charge incurred. Items must be returned to Contractor within thirty (30) days from date of delivery. If there is a difference in price in the items exchanged, the Contractor must notify H-GAC and invoice Customer for increase price or provide the Customer with a credit or refund for any decrease in price per Customer’s preference. On items returned, a credit or cash refund will be issued by the Contractor to Customer. This return and exchange option will extend for thirty (30) days following the expiration of the term of the Contract. All items returned by the Customer must be unused and in the same merchantable condition as when received. Items that are special ordered may be returned only upon approval of the Contractor.

  • Deceptive Trade Practices; Unfair Business Practices 1) Vendor represents and warrants that neither Vendor nor any of its Subcontractors has been (i) found liable in any administrative hearing, litigation or other proceeding of Deceptive Trade Practices violations as defined under Chapter 17, Texas Business & Commerce Code, or (ii) has outstanding allegations of any Deceptive Trade Practice pending in any administrative hearing, litigation or other proceeding.

  • Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.

  • File Naming Conventions Files will be named according to the following convention: {gTLD}_{YYYY-­‐MM-­‐DD}_{type}_S{#}_R{rev}.{ext} where:

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