Interface overview Sample Clauses

Interface overview. In the next sections, we present the interfaces involved in integrating the collaboration services within the Dicode workbench. We present in particular the user interface, related to the way users experience and interact with the integrated collaboration services, and technical interfaces, which aim to provide the necessary operations that the workbench can execute to facilitate a tighter integration with the collaboration services. With respect to the user interface, as described previously, the collaboration services have been integrated into the Dicode workbench as widgets, which display collaboration workspaces using the IFRAME HTML element. The following images illustrate how the integration of collaboration services is visible to end users. A tab-based approach is used to visualize the previously described views of a single collaboration workspace: each tab is a widget displaying a different view of the same collaboration workspace. Figures 3.4, 3.5 and
Sample 1
Interface overview. In order to be integrated within the Dicode Workbench, a widget based interface will be developed. A preliminary design of such an interface is shown in Figure 3.10. Users files Report 1 File 1 File 2 Report 2 Document 1 Upload file... Configure About This widget will display a generic label to identify the service on the top (“Storage service”). There will be a menu with, at least, three options: • “Upload file…”, this option will allow users to upload files to the storage service. A new window (Figure 3.11) will be opened to capture the metadata information from users, and select the file and its location. Once the uploading process is finished successfully, the new file will be shown within the tree view. • “Configure”, this option will allow users to configure some parameters of the storage service. • “About”, this option will display information about the developers, dates, licenses and useful information about the service. In the widget body, the list of available files will be shown using a tree view. Users will be able to retrieve the files by just clicking on the name. Additionally, the widget will allow dragging any file and dropping it over another service/widget within the workbench. Scrolls will be shown whenever needed. As mentioned before, when users want to upload a file, they will click on the “Upload file…” option and a new window will appear. This window will contain a form to capture the metadata information about the file. A preliminary design of this form is presented in Figure 3.11. The form in Figure 3.11 presents the following fields to be completed by the user: • Name: textual identifier of the file that will be used to display in the tree view. • Description: textual description of the file and its contents. • File format: this field allows users to specify the format of the file. This format will be selected from a fixed list. The list of supported file formats will be retrieved using the semantic services (DON).
Sample 1

Related to Interface overview

  • Interfaces GTE provides the CLECs with choices for access to OSS pre-ordering, ordering, maintenance and repair systems. Availability of the interfaces is fundamental to the CLEC being able to effectively do business with GTE. Additionally, in many instances, CLEC personnel must work with the service personnel of GTE. Measurements in this category assess the availability to the CLECs of systems and personnel at GTE work centers.

  • Interface A defined set of transmission facilities that separate Load Zones and that separate the NYCA from adjacent Control Areas. Investor-Owned Transmission Owners. A Transmission Owner that is owned by private investors. At the present time these include: Central Xxxxxx Gas & Electric Corporation, Consolidated Edison Company of New York, Inc., New York State Electric & Gas Corporation, Niagara Mohawk Power Corporation, Orange and Rockland Utilities, Inc., and Rochester Gas and Electric Corporation.

  • Program Overview Microsoft extends to eligible partners the opportunity to participate in the Program referenced above subject to these Program Terms & Conditions (“Program Terms”). Each entity participating in the Program is hereinafter referred to as a “Participant.” Participation in the Program is voluntary. The Program is governed by the Program Terms, which incorporate by reference the Microsoft Partner Network Agreement (as in effect between Microsoft and Participant, the “MPN Agreement”). Capitalized terms used but not defined in these Program Terms have the meanings assigned to them in the MPN Agreement. These Program Terms are subject to local requirements and may vary by jurisdiction, and Participant retains sole discretion to set pricing for sales of applicable products.

  • Overview (a) The Employer is committed to maintaining a stable and skilled workforce, recognising its contribution to the operation of the Employer. As such, full time direct and ongoing employment is a guiding principle of this Agreement. (b) The Employer will take all measures to achieve employment security for the direct permanent employees of the Employer. The Parties agree upon the measures in this Clause to protect and enhance the employment security, health and safety, terms and conditions of employment and career development of the employees. (c) The employer agrees that it is highly important to ensure that work is performed effectively, efficiently and without undue pressure or bullying, and in a way that promotes OHS and EO principles and practices in the workplace and appropriate representation of employees should they so request. The employer will ensure that its employment practices are consistent with the above principles and practices.

  • Project Overview Project Title [Drafting note: ARENA to complete. Insert full long name in accordance with ARENA’s naming convention] i.e. [GMS Number] [Powerworks, voltage control on the Pacific Islands Study] [GMS Number] [study/ project/ fellowship/ scholarship/ R&D Project] Contract Number [Drafting note: ARENA to complete – to be obtained from ARENA’s GMS] Recipient [Drafting note: Recipient to insert full legal name and ABN] Guidelines and policies Advancing Renewables Program – Program Guidelines, 2020 (xxxxx://xxxxx.xxx.xx/xxxxxx/0000/00/XXXXX_XXX_Xxxxxxxxxx_XX_Xxxxxx_Xxxxx_XXXXX.xxx) ARENA Variation Policy (xxxxx://xxxxx.xxx.xx/xxxxxx/0000/00/xxxxx-xxxxxxx-xxxxxxxxx-xxxxxxxxx-xxxxxx.xxx) ARENA Report Writing Guidelines (xxxxx://xxxxx.xxx.xx/xxxxxx/0000/00/xxxxx-xxxxxx-xxxxxxx-xxxxxxxxxx.xxx)

  • Operation and Maintenance Manuals Receipts for transmittal of Operation and Maintenance Manuals, Brochures and Data to the Design Professional (or Commissioning Agent) as required by Section 6.1.1.5.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If ECI chooses to subtend a Verizon access Tandem, ECI’s NPA/NXX must be assigned by ECI to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 ECI shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from ECI’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office ECI utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow ECI’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Architecture The Private Improvements shall have architectural features, detailing, and design elements in accordance with the Project Schematic Drawings. All accessory screening walls or fences, if necessary, shall use similar primary material, color, and detailing as on the Private Improvements.

  • Network Interface Device 4.1 The NID is defined as any means of interconnection of end-user customer premises wiring to BellSouth’s distribution plant, such as a cross-connect device used for that purpose. The NID is a single-line termination device or that portion of a multiple-line termination device required to terminate a single line or circuit at the premises. The NID features two independent xxxxxxxx or divisions that separate the service provider’s network from the End User’s on-premises wiring. Each chamber or division contains the appropriate connection points or posts to which the service provider and the End User each make their connections. The NID provides a protective ground connection and is capable of terminating cables such as twisted pair cable. 4.1.1 BellSouth shall permit Al-Call to connect Al-Call ’s loop facilities to on-premises wiring through the BellSouth NID or at any other technically feasible point.