Open Issues. (a) Notwithstanding any provision of the Registry Agreement to the contrary (including Sections 7.6 and 7.7 thereof), Registry Operator agrees that the following requirements, procedures and provisions of the Registry Agreement (including the documents incorporated by reference therein) may be modified and amended by ICANN after the date hereof, without the consent of Registry Operator:
Open Issues. Notwithstanding any provision of the Registry Agreement to the contrary (including Sections 7.6 and 7.7 thereof), Registry Operator agrees that the following requirements, procedures and provisions of the Registry Agreement (including the documents incorporated by reference therein) may be modified and amended by ICANN after the date hereof, without the consent of Registry Operator: Specification 6 – Registry Interoperability and Continuity Specifications; Trademark Clearinghouse Requirements (§ 1 of Specification 7 of the Registry Agreement); Trademark Post-Delegation Dispute Resolution Procedure (§ 2.a of Specification 7 of the Registry Agreement); Registration Restriction Dispute Resolution Procedure (§ 2.a of Specification 7 of the Registry Agreement); Uniform Rapid Suspension (§ 2.b of Specification 7 of the Registry Agreement); Specification 11 – Public Interest Commitments (including the Public Interest Commitment Dispute Resolution Process); and any provision or term of the Registry Agreement that is the subject of advice or comment from the Governmental Advisory Committee (including any advice or comment to include new provisions in the Registry Agreement). Any such modifications and amendments are referred to herein as a “Required Change.” ICANN’s right to implement Required Changes under this Supplement shall expire on 15 January 2014. ICANN agrees that when it determines to make a Required Change, ICANN will provide Registry Operator written notice of such Required Change, which notice shall specify the terms of the Required Change (a “Change Notice”). Registry Operator agrees that, following its receipt of a Change Notice, the Required Change related thereto will be immediately effective and binding on ICANN and Registry Operator, and shall be incorporated by reference into the Registry Agreement without any action of the parties. If requested by ICANN, Registry Operator shall execute an amendment to the Registry Agreement to reflect any Required Change. Within thirty (30) calendar days of receipt of a Change Notice, Registry Operator may terminate the Registry Agreement upon five (5) calendar days written notice to ICANN; provided, however, that Registry Operator may not terminate the Registry Agreement pursuant to this Section 1(c) following the first delegation of the TLD to nameservers designated by Registry Operator into the root-zone. Upon expiration of such thirty (30) calendar day period, Registry Operator may not thereafter terminate ...
Open Issues. 1.5 If a Notice of Disagreement has been received by the Buyer pursuant to paragraph 1.2 of this Schedule 3, the parties shall try to amicably resolve the issue. Should they fail to do so within twenty (20) Business Days of the end of the aforesaid objection period of forty-five (45) days (for the purpose of this Schedule the “Disagreement Date”) then any such unresolved issue (for the purpose of this Schedule the “Open Issues”) shall be submitted to and settled by an accountant of a firm of international repute and with sufficient and relevant expertise (for the 132 purpose of this Schedule the “Accountant”) to be jointly appointed by the parties within fourteen (14) days of the Disagreement Date or, if the parties fail to agree on such appointment within that period, each party may make an application to the President of the Institute of Chartered Accountants in England and Wales to appoint the Accountant.
Open Issues. 4-21 1.4 LIST OF ILLUSTRATIONS FIGURE 2-1: FEEDER NETWORK BUILDING BLOCKS........................................2-8 FIGURE 3-1: CENTRAL STATION RELEASE 1 - REDUNDANT CONFIGURATION..................3-16 FIGURE 3-2: CENTRAL STATION RELEASE 2 - REDUNDANT CONFIGURATION..................3-17 FIGURE 3-3: CSC BLOCK DIAGRAM....................................................3-18 FIGURE 3-4: TERMINAL STATION DIGITAL CARD (SIC)..................................3-19 TABLE 2-I: AIRSTAR AND FEEDER PRODUCT TERMINOLOGY.................................2-8 TABLE 3-1: TRAFFIC TRANSPORT FUNCTIONS............................................3-9 TABLE 3-2: TRAFFIC CAPACITY OPTIONS...............................................3-9 TABLE 3-3: RADIO SPECIFICATIONS (26 GHZ).........................................3-10 TABLE 3-4: RADIO SPECIFICATIONS (10 GHZ).........................................3-12 TABLE 3-5: TERMINAL STATION......................................................3-14
Open Issues. A comprehensive and consolidated list of all outstanding SOW-related prob- lems identified by Denver Water and Consultant that remain to be resolved.
Open Issues. Notwithstanding the widespread acceptance of the Sxxxxx Bros. and Eastgroup analysis, three important issues remain unsettled: the importance of the traditional elements, what constitutes necessity for consolidation, what constitutes prejudice to an objecting creditor’s interests, and the relationship between creditor reliance and necessity. [ ], 2000 Page 24
Open Issues. In the first 6 months of the project, work in WP3 focused on the most crucial architectural questions, with the aim of laying the architectural foundations for the technical work in the project. Naturally, it was not possible to answer all questions in this limited amount of time. Some open issues were identified that will have to be addressed in the next iteration of the work on the FogProtect architecture. The most important open issues are: ● Pre-run-time architectural issues. The current architecture focuses on the components and their interaction during run time. But there has to be some work done before the system enters this phase. For example, the creation of policies and the provision of a safe configuration to start from are necessary, and it is not yet clear if the Reference Model should contain a pre-deployment (e.g. design time) model of the starting configuration or all possible configuration variants for a system. The interplay of components pre-run-time is not trivial and has to be investigated further. ● Protecting the FogProtect system itself. While the applications protected by FogProtect are run in a data mesh, this may not apply to all the FogProtect components themselves. Hence, it is not clear yet how the security of the FogProtect system can be guaranteed. Of course, the core FogProtect components are less numerous and diverse than application components and resources, so it can be secured more easily by ‘conventional’ means. ● Distribution and decentralization. The current high-level architecture abstracts from the question of how the FogProtect components are to be distributed in the computing continuum. This remains a challenging question, also considering the potential issues stemming from decentralized decision-making.
Open Issues. The partners will discuss further when project progresses, to refine; The list of datasets and their confidentiality level. This will be assessed considering the re-used pre-existing data, the confidentiality of the process/ object they describe, and the exploitation potential if these datasets are kept and protected by consortium partners. Of course, data related to publications in open access will be open. The datasets naming rules The classification rules for data access, storage and archiving The platforms to be used to share datasets identified as « open », possibly, as mentioned above: « Conventional » platforms for open data storage or data repositories such as Zenodo, Dryad, Figshare, etc. The partners will investigate whether the chosen external repositories are permanent and will ensure that the entity in charge of this repository does not take the ownership of the data. They will also ensure the creation of a DOI (Digital Object Identifier), commonly used to identify journals/data when published in scientific journals. Overviews of repositories can be found on ROAR, OpenDOAR, Re3data, and OpenAIRE provides guidance on proper depositing. The project website, xxxx://xxx.xxxxxxx-xxxxxx.xx/ , EU-funded data repositories such as OpenAIRE xxx.xxxxxxxx.xx and ZENODO xxxxx://xxxxxx.xxx , Journals websites1, etc Data archiving rules and costs. This will include a risk analysis to determine the relevance of data retention (scientific, strategic, legal, heritage value), including: Legal or contractual obligation to retain certain data for a specified period by making them available on request in certain cases. (a priori not applicable for SPIDER) Transparency of research and traceability. Indeed, publishers may request to link data to publications. Data which are non-reproducible or too expensive to reproduce. Political and heritage issues: capitalization of data (a priori not applicable for SPIDER). The type of data to be archived will also be assessed according to the project and its objectives. Data sampling will be considered, to reduce the archive volume, assessing if a selection of data is sufficiently representative of the set. 1 publishers may request to link data to publications.
Open Issues. 1. Format of MFcR2 commands/status/parameters needs to be expanded to handle compelled signalling.
Open Issues. (i) Any open issues should be specified in the CR.
