Supporting Contextualization Sample Clauses

Supporting Contextualization. ‌ Context information added to the preserved content is meant to ease the interpretation of such content in case of re-activation. The information contextualization is investigated in WP6 (see for example deliverables D6.1 [ForgetIT, 2013c]). Context information can be gained in different ways, since (a) it can be provided by the Active System at the time content is sent to the DPS, (b) the PoF Middleware can automatically extract information from the provided content and other sources such as e.g. a domain specific ontology or external knowledge sources (e.g. Wikipedia) and (c) it can be a mix of the previous two approaches. If this is possible in the considered Active System, harvesting context information which is already explicated in the Active System (option (a) above) looks more promising. In this way a richer and more quality-controlled form of context can be provided, with respect to what can be automatically extracted in the preservation process. For example in the Semantic Desktop (see WP9) content is already annotated using a ontology, i.e. the Per- xxxxx Information MOdel (PIMO). This annotation, obviously, is a good source of context information for preservation. However, option (a) also puts higher requirements on the Active System: (1) explicated context has to be available (or it has to be explicated for this purpose) and (2) the Active System has to be extended with a functionality that is able to attach context information to the content information sent for preservation.
Sample 1
AutoNDA by SimpleDocs
Supporting Contextualization. ‌ Context information added to the preserved content is meant to ease the interpretation of such content in case of re-activation. The information contextualization is investigated in WP6 (see deliverables D6.1 [Xxxxxxxxx et al., 2013], D6.2 [Xxxxxxxxx et al., 2014], D6.3 [Xxxxxxxxx et al., 2015], and D6.4 [Xxxxxxxxx et al., 2016]). Context information can also be gained in different ways, since (a) it can be provided by the Active System at the time content is sent to the DPS, (b) the PoF Middleware can automatically extract information from the provided content and other sources such as
Sample 1

Related to Supporting Contextualization

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

  • Functionality Customer is entitled to additional functionality previously purchased or bundled with the software if available in the version or update released on or after the start date of the Agreement. Customer acknowledges that certain functionality in current and previous software versions may not be available in future upgrades. Added functionality may require additional paid services (clinical and technical) to configure and support.

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

  • Interfaces Bellcore’s GR-446-CORE defines the interface between the administration system and LIDB including specific message formats. (Bellcore’s TR-NWP-000029, Section 10)

  • Programming (a) Pursuant to Section 624 of the Cable Act, the Licensee shall maintain the mix, quality and broad categories of Programming set forth in Exhibit 4, attached hereto and made a part hereof. Pursuant to applicable federal law, all Programming decisions, including the Programming listed in Exhibit 4, attached hereto, shall be at the sole discretion of the Licensee.

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

  • Internet Connectivity School must provide sufficient hardline internet connectivity and the required network configurations (provided in Exhibit A) for each Pixellot System to allow live broadcasts. PlayOn will provide the point-to-point wireless internet base station (“Point to Point”) when needed to deliver hardline internet connectivity to Pixellot Systems installed in outdoor venues; provided that PlayOn is able to select the make and model of the Point to Point system. In the event that School requests, or requires, a specific Point to Point system that is different from what is provided by PlayOn, then School must provide and install the Point to Point system at its own expense.

  • User Content Certain areas of the Platform may enable you to post comments, send messages, correspond with others and/or otherwise post content (“User Content”) in connection with various features that Spectra may elect to offer, such as information libraries, e-mail service, bulletin boards, chatrooms, electronic postcards, chats with special guests, e-mails, and forums to communicate with others (“Message Features”). You must use the Message Features in a responsible manner and you are fully responsible for all User Content that you provide to us or others. Your License to Us. By submitting User Content, you grant us and our designees a royalty-free, irrevocable, perpetual, non-exclusive, worldwide, fully sub-licensable, transferable, license to publish, reproduce, distribute, display, perform, edit, adapt, modify, translate, create derivative works, make, sell, offer for sale, export, and otherwise use and exploit your User Content (or any portion thereof) in any way that we want and in any form, media, or technology now known or later developed. You hereby waive any moral rights you may have in your User Content in favor of Spectra and any of its designees. You represent that you have obtained all necessary permissions necessary to grant us those rights, including from any person identified in or implicated by your submission (including those shown in photographic content), and, in the case of minors, also from their parents or legal guardians, as appropriate. No Obligation to Publish. We are not obligated to publish, transmit or use your User Content. Spectra is not in any manner endorsing any User Content that it may publish or post on the Platform and cannot, and will not, vouch for its reliability. Spectra is not responsible for any User Content and has no duty to monitor User Content. You use any information contained in User Content at your own risk. Spectra and its designees have the right, in their sole discretion, to monitor, review, edit, remove, delete, disable, refuse, restrict, or terminate access to your User Content or the Platform (in whole or in part) at any time, without prior notice and in our sole discretion, for any or no reason. The obligations that you have to us under these Terms shall survive termination of the Platform, any use by you of the Platform, any User Content on the Platform, or these Terms. You will not continue to post any User Content that Spectra has previously advised you not to post.

  • Customer Content As part of the Services provided under this Agreement, Customer Data will be stored and processed in the data center region specified in the applicable Ordering Document. Axway shall not access Customer Content except in response to support or technical issues where Customer provides Axway with prior Customer’s written authorization required to access such Customer Content. Axway is not responsible for unauthorized access, alteration, theft or destruction of Customer Content arising from Customer’s own or its authorized users’ actions or omissions in contravention of the Documentation. Customer’s ability to recover any lost data resulting from Axway’s misconduct is limited to restoration by Axway from the most recent back-up.

  • Expansive Protocols Where the capability exists, originating or terminating traffic reroutes may be implemented by either party to temporarily relieve network congestion due to facility failures or abnormal calling patterns. Reroutes will not be used to circumvent normal trunk servicing. Expansive controls will only be used when mutually agreed to by the parties.

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