Outils de génération et documentation Sample Clauses

Outils de génération et documentation. Sous réserve des dispositions du présent Contrat et sauf disposition explicite contraire stipulée dans ce Contrat, Adobe vous concède une licence non exclusive et non cessible portant sur (a) l’utilisation des outils de génération et de la documentation aux seules fins de développement interne de programmes de développeur, et (b) l’utilisation des outils de génération et de la documentation dans le cadre de votre site Web dans le seul but de compiler les programmes de développeur qui sont distribués via celui-ci. En outre, le présent Contrat ne vous accorde aucun droit de distribution de la documentation, des outils de génération et du moteur d’exécution. Pour plus d’informations concernant l’obtention des droits pour la distribution de ces composants avec votre produit ou service, rendez-vous sur les sites xxxx://xxx.xxxxx.xxx/go/redistributeairsdk et xxxx://xxxxxxxxxx.xxxxx.xxx/fr/wiki/display/flexsdk/Legal+Stuff.
AutoNDA by SimpleDocs

Related to Outils de génération et documentation

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

  • Required Documentation The AGENCY is responsible for ensuring that all documents required by this Contract are current and available for the COUNTY’S review upon request. These documents may include, but are not limited to, certificate(s) of insurance, job descriptions and background check confirmations of staff.

  • 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

  • Required Fiscal Documentation A. Prior to execution of this Agreement, Contractor will have submitted to County for review and approval an annual budget covering all contracted services under this Agreement.

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

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

  • Documentation control Specify how documentation will be identified with an alpha numeric which indicates source, recipient, communication number etc. Provide details of any particular format or other constraints; for example that all contractual communications will be in the form of properly compiled letters or forms attached to e mails and not as a message in the e mail itself. State any particular routing requirements but note from TSC3 who issues what to whom.

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

  • Service Documentation The “Service Documentation” includes;

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

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