Domain-Specific Languages Sample Clauses

Domain-Specific Languages. ‌ The bugs mention a number of different Domain-Specific Languages (DSL’s). For example, bug #377d7be involves communicating with the Motoman controller through a series of codes that have to follow the language rules (instructions and code have to obey some specific order). The ROS driver code for Motoman issues these codes in the wrong order. In another case, the STL files (3D modeling and mesh files) are stored with a wrong prefix (bug #eadbcb8). A similar problem is seen in bug #0829607. An interesting variation can be seen in bug #778c1ac, where a Launch XML file violates the schema, because the location of parameters have been changed in the schema. The bugs in domain-specific languages are interesting from the language research perspective. Some of them can be addressed by incorporating schema checkers in the build system, especially for languages following standard technology stacks such as XML, JSON, or YAML (launch files, xacro files, and urd files and package files belong to this group). Some other of these bugs are much more difficult to handle, and require a more elaborate action than simple process improvement. Especially the problem of synthesizing correct scripts is a difficult research challenge in software language engineering. We will make examples of this bugs available for fellow researchers in this field, hoping to reduce this kind of problems long-term.
View Source

Related to Domain-Specific Languages

  • Contract Language The following language shall be included in contracts for City projects between the Consultant and any Subcontractors, vendors, and suppliers: Contractor shall not discriminate on the basis of race, gender, gender expression, gender identity, religion, national origin, ethnicity, sexual orientation, age, or disability in the solicitation, selection, hiring, or treatment of subcontractors, vendors, or suppliers. Consultant shall provide equal opportunity for Subcontractors to participate in opportunities. Consultant understands and agrees that violation of this clause shall be considered a material breach of the contract and may result in contract termination, debarment, or other sanctions.

  • Languages 20.1 The Proclamation of Sale, these conditions of sale and the Memorandum may have been translated and published in different forms and languages. In the event of any discrepancy, misstatement, omission or error appearing in the various forms or languages, this English version shall prevail.

  • Sample Language The following provides a sample contract clause: Compliance with the ▇▇▇▇▇▇▇▇ “Anti-Kickback” Act.

  • Suggested Language The following provides a debarment and suspension clause. It incorporates an optional method of verifying that contractors are not excluded or disqualified. (1) This contract is a covered transaction for purposes of 2 C.F.R. pt. 180 and 2 C.F.R. pt. 3000. As such, the contractor is required to verify that none of the contractor’s principals (defined at 2 C.F.R. § 180.995) or its affiliates (defined at 2 C.F.R. § 180.905) are excluded (defined at 2 C.F.R. § 180.940) or disqualified (defined at 2 C.F.R. § 180.935). (2) The contractor must comply with 2 C.F.R. pt. 180, subpart C and2 C.F.R. pt. 3000, subpart C, and must include a requirement to comply with these regulations in any lower tier covered transaction it enters into. (3) This certification is a material representation of fact relied upon by the Participating Public Agency. If it is later determined that the contractor did not comply with 2 C.F.R. pt. 180, subpart C and 2 C.F.R. pt. 3000, subpart C, in addition to remedies available to the Participating Public Agency, the Federal Government may pursue available remedies, including but not limited to suspension and/or debarment. (4) The bidder or proposer agrees to comply with the requirements of 2 C.F.R. pt. 180, subpart C and 2 C.F.R. pt. 3000, subpart C while this offer is valid and throughout the period of any contract that may arise from this offer. The bidder or proposer further agrees to include a provision requiring such compliance in its lower tier covered transactions.

  • Technical Specifications The purpose of the Technical Specifications (TS), is to define the technical characteristics of the Goods and Related Services required by the Procuring Entity. The Procuring Entity shall prepare the detailed TS consider that: