Developer Documentation Sample Clauses

Developer Documentation. Licensee’s use of the APIs and display of the Content must comply with the technical documentation, these terms of use, usage guidelines, and other documentation (“Developer Documentation”) maintained at Company’s developer site located at (xxxxxxx.xxx)
Sample 1
AutoNDA by SimpleDocs
Developer Documentation. The developer documentation is centring around the OmNom tool description on source code level, the model specifications and the server documentation. The OmNom tool documentation for developers is directly in the source code but can also be browsed in a more user friendly way in an HTML representation of these Javadocs. The link to the source code documentation is also listed in the wiki. Configurations that were made in order to deploy the various tools and services that are used in the ingestion infrastructure are documented as well. An overview of the deployment is also part of this deliverable and includes brief descriptions of the OmNom, server and Silk deployments. The server and tool deployments are explained more detailed and also written as a living document in the wiki as the configurations can still change. Specifications of the DM2E model, the OmNom vocabulary and the OmNom-Types vocabulary can directly be accessed via their namespaces URIs: • DM2E model: xxxx://xxxx.xx0x.xx/schemas/dm2e/ • OmNom vocabulary: xxxx://xxxx.xx0x.xx/omnom/ • OmNom-Types: xxxx://xxxx.xx0x.xx/omnom-types/ The URIs opened in an html browser lead directly to the representation of the models on Neologism26. Here, the whole model as well as the individual properties and classes of the respective models are displayed. Every of these resources has its own definition. In addition, the DM2E model is described more detailed in a textual model description. This was especially needed as a help for data providers in the scope of the project. The latest published specification as well as the model for further (local) usage in an OWL-file can be accessed via the documentation wiki. Intermediate model versions can be found on the projects internal wiki on Redmine. As soon as a new model version is stabilised, it will appear in the open DM2E wiki and also be available from outside the project.
Sample 1
Developer Documentation. ARP Developer represents and warrants to GSFA that all documentation, certificates, licenses, information and data (collectively, “Documentation”) provided to GSFA as part of ARP Developer’s application package is/are true, accurate and complete in all respects. ARP Developer shall notify GSFA in writing within three (3) business days of the date that ARP Developer has knowledge of any inaccuracy or change in the status of any Documentation.
Sample 1

Related to Developer Documentation

  • Licensed Documentation If commercially available, Licensee shall have the option to require the Contractor to deliver, at Contractor’s expense: (i) one (1) hard copy and one (1) master electronic copy of the Documentation in a mutually agreeable format; (ii) based on hard copy instructions for access by downloading from the Internet

  • Other Documentation Administrative Agent shall have received all documents and instruments that Administrative Agent has then reasonably requested, in addition to those described in this Section 4.1. All such additional documents and instruments shall be reasonably satisfactory to Administrative Agent in form, substance and date.

  • Project Documentation All documentation provided to the City other than Project drawings shall be furnished on a Microsoft compatible compact disc.

  • Technical Documentation Prior to commencement of the Tests on Completion, the Contractor shall supply to the Engineer the technical documentation as specified in the Employer’s Requirements. The Works or Section shall not be considered to be completed for the purposes of taking- over under sub-clause 10.1 [Taking Over of the Works and Sections] until the Engineer has received the technical documentation as defined in this sub-clause 5.7, the "history file" including design calculations and certain certification as well as any other documents required to meet the CE Marking requirements.

  • Supporting Documentation Upon request, the HSP will provide the LHIN with proof of the matters referred to in this Article.

  • Product Documentation You should review the policy documents carefully to ensure they accurately reflect the cover, conditions, limits, and other terms that you require. Particular attention should be paid to policy conditions and warranties as failure to comply with these could invalidate your policy. It is important that you retain and keep safely all documents associated with your policy so that you can refer to them in the event of a claim.

  • Medical Documentation The teacher must supply a letter from a medical 3 doctor, who treated the patient, stating that in his/her opinion, there is a strong 4 probability that the illness was contracted at school.

  • Tax Documentation Xxxxxx agrees to provide a completed IRS 1099 for its payments to, and Xxxxxxx agrees to provide IRS W-9 forms for, each of the following payees under this Settlement Agreement:

  • Instrumentation The acceleration shall be recorded during the test, using equipment in accordance with channel frequency class 1000 as specified in the latest version of ISO 6487.

  • Software and Documentation Licensee may make as many copies of the Software necessary for it to use the Software as licensed. Each copy of the Software made by Licensee must contain the same copyright and other notices that appear on the original copy. Licensee will not modify the Documentation. Documentation may: (a) only be used to support Licensee’s use of the Software; (b) not be republished or redistributed to any unauthorized third party; and (c) not be distributed or used to conduct training for which Licensee, or any other party, receives a fee. Licensee will not copy any system schema reference document related to the Software.

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