Travelling Object Clause Samples

The 'Travelling Object' clause defines the terms and conditions under which an object, such as equipment, goods, or materials, is transported from one location to another. Typically, this clause outlines responsibilities for the care, custody, and control of the object while in transit, specifying who bears the risk of loss or damage during the journey. For example, it may state whether the sender, carrier, or recipient is liable for any incidents that occur while the object is being moved. The core function of this clause is to allocate risk and clarify liability during transportation, thereby preventing disputes and ensuring all parties understand their obligations.
Travelling Object. ‌ Section 6.1. To make in-house formats compatible with the TO, service providers had to develop a conversion tool. Most partners have adapted the Java tool developed by ILSP (called FormatConverter) which is documented in D4.2 Section 4. FormatConverter has been used to modify data inside a web service (web service with the tool and FormatConverter). However, some partners have deployed the FormatConverter as a web service (one web service with the tool and another web service with FormatConverter). ILSP also developed an XSLT stylesheet to visualize the TO in a more user friendly way than XML. It is documented in D4.2 Section 4 and it is posted on the PANACEA web site7.
View SourceView Similar (2)
Travelling Object. The Travelling Object (TO) is the data object that is being exchanged between the platform components. The TO can be different depending on the situation and the components connected and has been chosen following already existing standards. As presented in ▇▇▇▇ and Bel (2011), there have been relevant proposals from the Language Resources community to reach a consensus about formats to represent annotated corpora. The aim of the PANACEA developers has been to use already defined and used standards for each scenario that required a common data format.
View SourceView Similar (2)
Travelling Object. This section deals with the conversion of the different input/output formats of the aligners from and to the Travelling Object (TO) format (defined in Deliverable 3.1, section 6.1). 7 ▇▇▇▇://▇▇▇▇.▇▇▇▇▇▇.▇▇▇/p/berkeleyaligner/ 8 ▇▇▇▇://▇▇▇▇▇▇▇▇▇▇.▇▇▇/ aligner2to is a webservice that can convert the output of any11 of the aligners that have been integrated into PANACEA to the TO. It calls the FormatConverter tool, originally developed by ILSP (see section 4 of Deliverable 4.2), which has been extended with additional processors in order to handle the formats of the aforementioned aligners. sentalg_tok_to2word_alg is a webservice that takes three inputs in TO format (source and target corpus, both sentence-split and tokenised, and sentence alignment) and outputs two files (the subset of sentences in the source and target corpus that have 1-to-1 sentence alignments) in the plain sentence-split and tokenised format that the sub-sentential alignment webservices take as input. sentsplit_tok2to is a webservice that was required by sentalg_tok_to2word_alg; it converts sentence-split and tokenised files to the TO format. This section presents several workflows of webservices developed in Taverna (Hull et al., 2006),12 showing possible usages of aligners in the platform, the interactions that arise, etc. The first workflow, depicted in Figure 1, presents a pipeline that performs sentence alignment on bilingual text crawled from the web. It is made up of two sequential workflows: • bicrawler_to_text processes the output of the Focused Bilingual Crawler (see section 3.2 of Deliverable 4.2 for more details) for a pair of languages A and B producing three outputs: plain text versions of the source and target corpora acquired and the bilingual header in XCES format.13 • sentence_alignment takes as input the output from bicrawler_to_text and performs sentence alignment using Hunalign. In order to do so, the text of each language is preprocessed with a sentence splitter and a tokeniser. Finally, the workflow outputs three objects whose format is compliant with the TO: the sentence alignment and the source and target corpora sentence-split and tokenised. 11 The only exception is Anymalign, whose output is not straightforward convertible into the TO. This aligner has been integrated anyway, as it is considered useful for deriving bilingual dictionaries (work-package 5.2). 12 ▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇.▇▇▇.▇▇/ 13 ▇▇▇▇://▇▇▇.▇▇▇▇.▇▇▇/schema/#align Figure 2 and Figure 3 show modified ve...
View SourceView Similar (2)
Travelling Object. The Travelling Object (TO) has been used to transport data between components in PANACEA and it has not been changed from its original design. It was documented in deliverable D3.1 Section 6.1.
View Source
Travelling Object. TO-GR-01: Define/choose simple TO - Design of the first version of the travelling object (simple TO). - Inline annotation. TO-GR-02: Conversion tools (simple TO) - Develop scripts or tools to convert in-house formats to TO format (simple TO). TO-GR-03: Define/choose complex TO - Design of a second version of the travelling object (complex TO). - Stand-off annotation? - New features and improvements. TO-GR-04: Conversion tools (complex TO) - Develop scripts or tools to convert in-house format to complex format.
View Source
Travelling Object. Corpus and data format: This section aims to describe existing data formats that could be used in PANACEA.
View Source

Related to Travelling Object

  • Response to Objections Each Party retains the right to respond to any objection raised by a Participating Class Member, including the right to file responsive documents in Court no later than five court days prior to the Final Approval Hearing, or as otherwise ordered or accepted by the Court.

  • Technical Objections to Grievances It is the intent of both parties to this agreement that no grievance shall be defeated merely because of a technical error other than time limitations in processing the grievance through the grievance procedure. To this end an arbitration board shall have the power to allow all necessary amendments to the grievance and the power to waive formal procedural irregularities in the processing of a grievance in order to determine the real matter in dispute and to render a decision according to equitable principles and the justice of the case.

  • Program Objectives Implement a rigorous constructability program following The University of Texas System, Office of Capital Projects Constructability Manual. Identify and document Project cost and schedule savings (targeted costs are 5% of construction costs). Clarification of Project goals, objectives.

  • Religious Objections Any employee who is a member of a bonafide religion, body, or sect which has historically held conscientious objections to joining or financially supporting public employee organizations shall not be required to join or financially support the organization. Such employee shall, in lieu of periodic dues or agency shop fees, pay sums equal to said amounts to a non-religious, non-labor charitable fund exempt from taxation under Section 501(c)(3) of the Internal Revenue Code, which has been selected by the employee from a list of such funds designated by the City and the Association in a separate agreement. Such payments shall be made by payroll deduction as a condition of continued exemption from the requirements of financial support to the Association and as a condition of continued employment.

  • Billing and Payment; Disputed Amounts 9.1 Except as otherwise provided in this Agreement, each Party shall submit to the other Party on a monthly basis in an itemized form, statement(s) of charges incurred by the other Party under this Agreement. 9.2 Except as otherwise provided in this Agreement, payment of amounts billed for Services provided under this Agreement, whether billed on a monthly basis or as otherwise provided in this Agreement, shall be due, in immediately available U.S. funds, on the later of the following dates (the “Due Date”): (a) the due date specified on the billing Party’s statement; or (b) twenty (20) days after the date the statement is received by the billed Party. Payments shall be transmitted by electronic funds transfer. 9.3 If any portion of an amount billed by a Party under this Agreement is subject to a good faith dispute between the Parties, the billed Party shall give notice to the billing Party of the amounts it disputes (“Disputed Amounts”) and include in such notice the specific details and reasons for disputing each item. A Party may also dispute prospectively with a single notice a class of charges that it disputes. Notice of a dispute may be given by a Party at any time, either before or after an amount is paid, and a Party’s payment of an amount shall not constitute a waiver of such Party’s right to subsequently dispute its obligation to pay such amount or to seek a refund of any amount paid. The billed Party shall pay by the Due Date all undisputed amounts. Billing disputes shall be subject to the terms of Section 14, Dispute Resolution. 9.4 Charges due to the billing Party that are not paid by the Due Date, shall be subject to a late payment charge. The late payment charge shall be in an amount specified by the billing Party which shall not exceed a rate of one-and- one-half percent (1.5%) of the overdue amount (including any unpaid previously billed late payment charges) per month. 9.5 Although it is the intent of both Parties to submit timely statements of charges, failure by either Party to present statements to the other Party in a timely manner shall not constitute a breach or default, or a waiver of the right to payment of the incurred charges, by the billing Party under this Agreement, and, except for assertion of a provision of Applicable Law that limits the period in which a suit or other proceeding can be brought before a court or other governmental entity of appropriate jurisdiction to collect amounts due, the billed Party shall not be entitled to dispute the billing Party’s statement(s) based on the billing Party’s failure to submit them in a timely fashion.