Portal interoperability Sample Clauses

Portal interoperability. To achieve a federation of labs and to increase the potential uptake of the Go- Lab software, interchangeability of the portal components and interoperability using open specifications is important. The Go-Lab architecture achieves the technical, syntactic, semantic and pragmatic interoperability levels of the Con- ceptual Interoperability Model (Turnitsa, 2005). This section elaborates on in- teroperability enabled through the labs, metadata and the interfaces between components. Lab interoperability enables the integration of labs with an ILS platform, which is often difficult due to the wide variety of labs and their technical differences (e.g., implemented as a Java Applet or a Flash application). To make labs in- teroperable with learning environments different approaches are possible. For instance, the XxXx project (Xxxxxxx et al., 2011) bundles labs in SCORM (Xxxx, Scheuhase, Xxxxxxx, & Xxxxxx, 2002) packages, but this does not always en- able proper interoperability since SCORM is not designed for interactive labs and the support of the latest versions of SCORM by learning environments is low. In Go-Lab, online labs will be provided as smart devices (Xxxxxx, Xxxx, Xxxxxxx, & Xxxxxxxx, 2013) (see D4.1) that make labs more ubiquitous, au- tonomous and self-aware. The smart device paradigm abstracts the details of each lab on the server-side by providing a specified set of web services (Gillet et al., 2013). This interoperability layer allows the ILS platform to run any lab supporting the smart device paradigm and smart device compatible apps can be reused to operate numerous labs. Making existing online labs smart device compliant might require the implemen- tation of the specified web services. In some cases it will be impossible to change the lab implementation. To enable interoperability with such labs, we will provide a smart gateway (see D4.1) that transforms existing labs offered by third parties to be conform to the smart device specification (Xxxxxx et al., 2013). Through both the smart device and smart gateway, interoperability between any online lab and the ILS platform is enabled. Metadata interoperability is the ability to exchange metadata with minimal loss of content and functionality between different systems (NISO Press, 2004). Several initiatives (Xxxxxxxxx Xxxxx, 2010; X. Xxxxxxx & Xxxxx, 2012) are cur- rently working on metadata specifications to describe online labs and related resources. Their main reason is to allow wider discov...
AutoNDA by SimpleDocs

Related to Portal interoperability

  • Interoperability To the extent required by applicable law, Cisco shall provide You with the interface information needed to achieve interoperability between the Software and another independently created program. Cisco will provide this interface information at Your written request after you pay Cisco’s licensing fees (if any). You will keep this information in strict confidence and strictly follow any applicable terms and conditions upon which Cisco makes such information available.

  • Technical Interfaces 3.2.6.1 The Interconnection facilities provided by each Party shall be formatted using either Alternate Xxxx Inversion (AMI) line code with Superframe format framing or Bipolar 8-Zero Substitution with Extended Superframe (B8ZS ESF) format framing or any mutually agreeable line coding and framing.

  • Registry Interoperability and Continuity Registry Operator shall comply with the Registry Interoperability and Continuity Specifications as set forth in Specification 6 attached hereto (“Specification 6”).

  • Evaluation Software If the Software is an evaluation version or is provided to You for evaluation purposes, then, unless otherwise approved in writing by an authorized representative of Licensor, Your license to use the Software is limited solely for internal evaluation purposes in non-production use and in accordance with the terms of the evaluation offering under which You received the Software, and expires 90 days from installation (or such other period as may be indicated within the Software). Upon expiration of the evaluation period, You must discontinue use of the Software, return to an original state any actions performed by the Software, and delete the Software entirely from Your system and You may not download the Software again unless approved in writing by an authorized representative of Licensor. The Software may contain an automatic disabling mechanism that prevents its use after a certain period of time. RESTRICTIONS

  • 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.

  • Antivirus software All workstations, laptops and other systems that process and/or store PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY must have installed and actively use comprehensive anti-virus software solution with automatic updates scheduled at least daily.

  • 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.

  • Compatibility 1. Any unresolved issue arising from a mutual agreement procedure case otherwise within the scope of the arbitration process provided for in this Article and Articles 25A to 25G shall not be submitted to arbitration if the issue falls within the scope of a case with respect to which an arbitration panel or similar body has previously been set up in accordance with a bilateral or multilateral convention that provides for mandatory binding arbitration of unresolved issues arising from a mutual agreement procedure case. 2. Nothing in this Article and Articles 25A to 25G shall affect the fulfilment of wider obligations with respect to the arbitration of unresolved issues arising in the context of a mutual agreement procedure resulting from other conventions to which the Contracting States are or will become parties.”.

  • End User This agreement shall bind the ordering activity as end user but shall not operate to bind a Government employee or person acting on behalf of the Government in his or her personal capacity.

  • Required hardware and software The minimum system requirements for using the DocuSign system may change over time. The current system requirements are found here: xxxxx://xxxxxxx.xxxxxxxx.xxx/guides/signer-guide- signing-system-requirements.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!