Document Tree Sample Clauses

Document Tree. ‌ A Flowable is a document element that is placed on a page. It is usually a part of a document tree. Flowables at one level in a document tree are rendered one below the other. Here is schematic representation of an example document tree: |- Section | |- Paragraph | \- Paragraph \- Section |- Paragraph |- List | | | | | | | | | | | |- ListItem | | | |- Paragraph (item label; a number or bullet symbol) \- StaticGroupedFlowables (item body) \- Paragraph \- ListItem \- Paragraph | | | | | \- StaticGroupedFlowables \- List |- ListItem | \- ... \- ... \- Paragraph This represents a document consisting of two sections. The first section contains two para- graphs. The second section contains a paragraph followed by a list and another paragraph. All of the elements in this tree are instances of Flowable subclasses. Section and List are subclasses of GroupedFlowables; they group a number of flowables. In the case of List, these are always of the ListItem type. Each list item contains an item number (ordered list) or a bullet symbol (unordered list) and an item body. For simple lists, the item body is typically a single Paragraph. The second list item contains a nested List. A Paragraph does not have any Flowable children. It is however the root node of a tree of inline elements. This is an example paragraph in which several text styles are combined: Paragraph |- SingleStyledText('Text with ') |- MixedStyledText(style='emphasis') | |- SingleStyledText('multiple ') | \- MixedStyledText(style='strong') | |- SingleStyledText('nested ') | \- SingleStyledText('styles', style='small caps') \- SingleStyledText('.') The visual representation of the words in this paragraph is determined by the applied style sheet. Read more about how this works in the next section. Besides SingleStyledText and MixedStyledText elements (subclasses of StyledText), paragraphs can also contain InlineFlowables. Currently, the only inline flowable is InlineImage. The common superclass for flowable and inline elements is Styled, which indicates that these elements can be styled using the style sheets.
Sample 1Sample 2
AutoNDA by SimpleDocs
Document Tree. The Contractor shall develop and maintain a document list, such as a document tree, quarterly (January 15th, April 15th, July 15th, and October 15th of each year) that shows traceability among the Contractor’s DRIS documentation. Further, this list will provide a description of the linkage between documents, either through reference or through subdocument structures. As an example, the Program Management Plan will likely incorporate by reference several other sub plans, such as the Staffing Plan, and Subcontractor Plan, which will each have its own independent revision cycle. The Government would like to see these linkages clearly spelled out. The tree will include the document name, author, update date, and relationship to other documents.
Sample 1

Related to Document Tree

  • Document Management The Contractor must retain sufficient documentation to substantiate claims for payment under the Contract and all other records, electronic files, papers, and documents that were made in relation to this Contract. The Contractor must retain all documents related to the Contract for five (5) years after expiration of the Contract or, if longer, the period required by the General Records Schedules maintained by the Florida Department of State available at the Department of State’s Records Management website.

  • Document routing The Contractor shall use the information in the Routing Data Table below only to fill in applicable fields in WAWF when creating payment requests and receiving reports in the system. Routing Data Table* Field Name in WAWF Data to be entered in WAWF Pay Official DoDAAC "To be cited in each individual task order" Issue By XxXXXX "To be cited in each individual task order" Admin DoDAAC "To be cited in each individual task order" Inspect By XxXXXX "To be cited in each individual task order" Ship To Code "To be cited in each individual task order" Ship From Code "To be cited in each individual task order" Mark For Code "To be cited in each individual task order" Service Approver (DoDAAC) "To be cited in each individual task order" Service Acceptor (DoDAAC) "To be cited in each individual task order" Accept at Other DoDAAC "To be cited in each individual task order" LPO DoDAAC "To be cited in each individual task order" DCAA Auditor DoDAAC "To be cited in each individual task order" Other DoDAAC(s) "To be cited in each individual task order" (*Contracting Officer: Insert applicable DoDAAC information or “See schedule” if multiple ship to/acceptance locations apply, or “Not applicable.”)

  • DOCUMENT PREPARATION The Transfer/Deed shall, save for the Land Transfer Tax Affidavit, be prepared in registrable form at the expense of Seller, and any Charge/Mortgage to be given back by the Buyer to Seller at the expense of the Buyer. If requested by Buyer, Seller covenants that the Transfer/Deed to be delivered on completion shall contain the statements contemplated by Section 50(22) of the Planning Act, R.S.O.1990.

  • Paper Document Controls In order to comply with the following paper document controls, the Contractor agrees to:

  • AGREEMENT TITLE This Agreement will be known as the Health and Allied Services, Managers and Administrative Workers (Victorian Public Sector) (Single Interest Employers) Enterprise Agreement 2021-2025.

  • Paper documents Any paper records must be protected by storing the records in a Secure Area which is only accessible to authorized personnel. When not in use, such records must be stored in a Secure Area.

  • Agreement Documents 1. This Agreement consists of the following documents:

  • LIGHT DUTY ASSIGNMENTS 1. In the event a clerk requests a light duty assignment, in writing, management must contact the President, Lehigh Valley Area Local to discuss such request.

  • Corporate Documents The Administrative Agent shall have received:

  • Related Agreements Any agreement related to this Plan shall be in writing and shall provide that: (i) such agreement may be terminated at any time, without payment of any penalty, by a vote of a majority of the Independent Trustees or by a vote of the holders of a “majority” (as defined in the 0000 Xxx) of the Fund's outstanding Class C voting shares; (ii) such termination shall be on not more than sixty days’ written notice to any other party to the agreement; (iii) such agreement shall automatically terminate in the event of its “assignment” (as defined in the 1940 Act); (iv) such agreement shall go into effect when approved by a vote of the Board and its Independent Trustees cast in person at a meeting called for the purpose of voting on such agreement; and (v) such agreement shall, unless terminated as herein provided, continue in effect from year to year only so long as such continuance is specifically approved at least annually by a vote of the Board and its Independent Trustees cast in person at a meeting called for the purpose of voting on such continuance.

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