Madrid Protocol Sample Clauses

Madrid Protocol. The ACUMEN consortium organized a deployment workshop to test the portfolio in Madrid on 13 December 2013. CSIC hosted the event and invited a delegate from the Spanish Foundation for Science and Technology (FECYT) for a keynote address and a presentation of their CV policy. The program included introductory presentations on the ACUMEN project and the portfolio as well as extensive user tests from two perspectives. The target audience for the event was early-career researchers (PhDs and post-docs) from a wide representation of fields. Approximately 60 participants were expected, all working in Spain. Besides a user test from the early-career perspective, we developed a test for the early-career participants to use the ACUMEN portfolio for their supervisors’ representation as well. Testing Portfolio Concept The outline for testing ACUMEN’s portfolio in Madrid was =based on two test cases, to maximize engagement with the portfolio. However, this was not feasible due to time constraints, partly caused by the allotted slots for the FECYT. After deliberations, it has therefore been decided that there will be one comprehensive user test. The test was geared towards gaining conceptual feedback on the contents of the portfolio, rather than aiming for on-the-spot filling out of details. Participants were asked to engage in a fictive job application for their next dream job, to be able to assess how useful the portfolio is in that case. As we were aiming for feedback from researchers from different career stages, we endeavored to address not only PhDs, but also more senior academics that attended the session. In preparation for the user test, portfolio templates were constructed and ready for dissemination, online or elsewhere; we also brought user test cases as additional and explanatory materials. Complementary, the posters and brochures created for the Utrecht (see MS4) were also used in Madrid. The Even programme was as follows:
View Source
Madrid Protocol. The Madrid System for the International Registration of Marks is governed by the Madrid Agreement, adopted in 1891, and the Protocol concerning that Agreement adopted in 1989. It relates to the international registration of trademarks that takes effect in each of the Contracting Parties that have been designated.
View Source
Madrid Protocol. Budapest Treaty;
View Source

Related to Madrid Protocol

  • Protocol The attached Protocol shall be an integral part of this Agreement.

  • Signaling protocol 4.1.3.1 SS7 Signaling is AT&T-21STATE’s preferred method for signaling. Where MF signaling is currently used, the Parties agree to use their best efforts to convert to SS7. If SS7 services are provided by AT&T-21STATE, they will be provided in accordance with the provisions of the applicable access tariffs. 4.1.3.2 Where MF signaling is currently used, the Parties agree to interconnect their networks using MF or dual tone MF (DTMF) signaling, subject to availability at the End Office Switch or Tandem Switch at which Interconnection occurs. The Parties acknowledge that the use of MF signaling may not be optimal. AT&T-21STATE will not be responsible for correcting any undesirable characteristics, service problems or performance problems that are associated with MF/SS7 inter-working or the signaling protocol required for Interconnection with CLEC employing MF signaling.

  • Review Protocol A narrative description of how the Claims Review was conducted and what was evaluated.

  • Medicaid Program Parties (applicable to any Party providing services and supports paid for under Vermont’s Medicaid program and Vermont’s Global Commitment to Health Waiver):

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐▇▇▇▇▇▇-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).