Developer Documentation Sample Clauses

Developer Documentation. Licensee’s use of the APIs and display of the Content must comply with the technical documentation, usage guidelines, call volume limits, and other documentation (“Developer Documentation”) maintained at Company’s developer site located at https: /▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇▇▇▇.▇▇▇/ (“Developer Site”). In the event of any conflict between the Developer Documentation and this Agreement, this Agreement shall prevail.
View SourceView Similar (2)
Developer Documentation. Partner agrees that use of the Interoperable Messaging Services by it and Partner Parties is governed by and must be solely in accordance with this Agreement (including all incorporated Developer Documentation (and all updates thereto)).
View Source
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.
View Source
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: ▇▇▇▇://▇▇▇▇.▇▇▇▇.▇▇/schemas/dm2e/ • OmNom vocabulary: ▇▇▇▇://▇▇▇▇.▇▇▇▇.▇▇/omnom/ • OmNom-Types: ▇▇▇▇://▇▇▇▇.▇▇▇▇.▇▇/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.
View Source

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.