ROW models supported in ARROW Sample Clauses

ROW models supported in ARROW. As mentioned previously, the ARROW system has been designed to support different models for the management of Orphan Works, in the first instance the set up of a centralised infrastructure and the set up of interoperable National ROWs. As described in §4.2 Feeding the ROW, the information gathered along the workflow by the RII, is the basis for the initial feeding and updates of the centralised ROW and in case of the National ROWs. In both cases it is fundamental to make the public information on Orphan Works publicly searchable and enhance the possibility for rightholders to declare their rights, thus reducing the number of Orphan Works. As described in §4.3 Functional Requirements, to fulfil the purpose the following functions/services are envisaged: - Search functions - Claiming request functions - Functions for the Management of ROW (management of claiming request and history) To maximise the European impact of the ROW, a central index for searching will be built to allow any user to search on the whole corpus orphan works in Europe from a single access point. Once the central index for search will be in place, rightholders will be able to search for a work and declare their rights. The claiming request function will be implemented at centralised level on Orphan Works managed in the centralised ROW. In case a Orphan Works are managed by other systems (as National ROWs) and they have their own claiming service, appropriate redirection mechanisms will be implemented from the central layer for searching to the national service. Function for the Management of the ROW – assessment of claiming requests (approve/refuse), update of the work rights status, access to work history – will be implemented at centralised level for claiming requests on Orphan Works managed in the centralised ROW. In case Orphan Works are managed by other systems (as National ROWs) and they have their own management functions, mechanisms to ensure the update of the work status in the central layer for search shall be provided. The following figure represents how the different model supported in ARROW can coexist in a single framework built on the ARROW workflow and RII. In the following figure, RROs are assumed to play the role of the ROW Manager and maintain national ROWs.
Sample 1
AutoNDA by SimpleDocs

Related to ROW models supported in ARROW

  • Application of Funding Techniques to Programs 6.3.1 The State shall apply the following funding techniques when requesting Federal funds for the component cash flows of the programs listed in sections 4.2 and 4.3 of this Agreement.

  • Available Services Subject to the terms of this agreement, Manager may obtain any of the Available Services from Sprint Spectrum in accordance with the provisions of this Section 2.1. The Available Services offered from time to time and the fees charged for such Available Services will be set forth on the then-current Exhibit 2.1.1 (the "Available Services and Fees Schedule"). If Sprint Spectrum offers any new Available Service, it will deliver a new Exhibit 2.1.1 indicating the new service and the fee for the new service. Manager may select one or more of the categories of Available Services. If Manager selects a particular category of services it must take and pay for all of the services under the category selected; Manager may not select only particular services within that category. If Sprint Spectrum determines to no longer offer an Available Service and the service is not a Selected Service, then Sprint Spectrum may give Manager written notice at any time during the term of this agreement that Sprint Spectrum no longer offers the Available Service.

  • Purchase Order Flip via Ariba Network (AN) The online process allows suppliers to submit invoices via the AN for catalog and non- catalog goods and services. Contractors have the ability to create an invoice directly from their Inbox in their AN account by simply “flipping” the purchase order into an invoice. This option does not require any special software or technical capabilities. For the purposes of this section, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider of MFMP the right and license to use, reproduce, transmit, distribute, and publicly display within the system the information outlined above. In addition, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider the right and license to reproduce and display within the system the Contractor’s trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Red Hat Enterprise Linux Desktop Software Subscriptions Software Subscriptions for Red Hat Enterprise Linux Desktops and Workstations are subject to the parameters set forth in Table 6 below. Each Red Hat Enterprise Linux Desktop and Workstation Software Subscription includes one Red Hat Network system entitlement and one Smart Management Module, each to be used solely with a single Red Hat Enterprise Linux Desktop or Workstation System. Production Support for Red Hat Enterprise Linux Desktop subscriptions is limited to web-based support only for your helpdesk support personnel. Red Hat is not obligated to support your end users directly.

  • ACCESS TO OPERATIONS SUPPORT SYSTEMS 2.1 BellSouth shall provide Max-Tel access to operations support systems (“OSS”) functions for pre-ordering, ordering and provisioning, maintenance and repair, and billing. BellSouth shall provide access to the OSS through manual and/or electronic interfaces as described in this Attachment. It is the sole responsibility of Max-Tel to obtain the technical capability to access and utilize BellSouth’s OSS interfaces. Specifications for Max-Tel ’s access and use of BellSouth’s electronic Version R4Q01: 12/01/01 interfaces are set forth at xxx.xxxxxxxxxxxxxxx.xxxxxxxxx.xxx and are incorporated herein by reference.

  • ELECTRICITY INFORMATION EXCHANGE PROTOCOLS 31.1 Protocols for exchanging information: The Distributor and the Trader must, when exchanging information to which an EIEP listed in Schedule 3 relates, comply with that EIEP.

  • Additional Information for Product Development Projects Outcome of product development efforts, such copyrights and license agreements. • Units sold or projected to be sold in California and outside of California. • Total annual sales or projected annual sales (in dollars) of products developed under the Agreement. • Investment dollars/follow-on private funding as a result of Energy Commission funding. • Patent numbers and applications, along with dates and brief descriptions.  Additional Information for Product Demonstrations: • Outcome of demonstrations and status of technology. • Number of similar installations. • Jobs created/retained as a result of the Agreement.

  • Updated Information Submission by Interconnection Customer The updated information submission by the Interconnection Customer, including manufacturer information, shall occur no later than one hundred eighty (180) Calendar Days prior to the Trial Operation. The Interconnection Customer shall submit a completed copy of the Electric Generating Unit data requirements contained in Appendix 1 to the LGIP. It shall also include any additional information provided to the Participating TO and the CAISO for the Interconnection Studies. Information in this submission shall be the most current Electric Generating Unit design or expected performance data. Information submitted for stability models shall be compatible with the Participating TO and CAISO standard models. If there is no compatible model, the Interconnection Customer will work with a consultant mutually agreed to by the Parties to develop and supply a standard model and associated information. If the Interconnection Customer's data is materially different from what was originally provided to the Participating TO and the CAISO for the Interconnection Studies, then the Participating TO and the CAISO will conduct appropriate studies pursuant to the LGIP to determine the impact on the Participating TO’s Transmission System and affected portions of the CAISO Controlled Grid based on the actual data submitted pursuant to this Article 24.3. The Interconnection Customer shall not begin Trial Operation until such studies are completed and all other requirements of this LGIA are satisfied.

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