Braille Format Sample Clauses

Braille Format. Braille materials provided to patients and visitors shall satisfy the Braille Authority of North America’s standards (“BANA Standards”) for printing and binding Braille materials, currently found at xxx.xxxxxxxxxxxxxxxx.xxx. Each braille document provided pursuant to the Agreement shall include all of the text and other content that is contained in the standard print version of the same document that is made available to the general public. Non-text content that is pure decoration, is used for visual formatting only, or duplicates information provided in the text need not be included in braille format. After documents have been prepared in a braille format, MEEI will provide the electronic rendering of the braille document to patients upon request.
Sample 1
AutoNDA by SimpleDocs
Braille Format 
Sample 1Sample 2Sample 3See All (4)

Related to Braille Format

  • File Format Standard Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in XXX 0000, Section 5, including all the records present in the actual zone used in the public DNS. Sub-format is as follows: Each record must include all fields in one line as: <domain-name> <TTL> <class> <type> <RDATA>. Class and Type must use the standard mnemonics and must be in lower case. TTL must be present as a decimal integer. Use of /X and /DDD inside domain names is allowed. All domain names must be in lower case. Must use exactly one tab as separator of fields inside a record. All domain names must be fully qualified. No $ORIGIN directives. No use of “@” to denote current origin. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. No $INCLUDE directives. No $TTL directives. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. No use of comments. No blank lines. The SOA record should be present at the top and (duplicated at) the end of the zone file. With the exception of the SOA record, all the records in a file must be in alphabetical order. One zone per file. If a TLD divides its DNS data into multiple zones, each goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.

  • meminta nasihat daripada Pihak Xxxxxx dalam semua perkara berkenaan dengan jualan lelongan, termasuk Syarat-syarat Jualan (iii) membuat carian Hakmilik Xxxxx xxxxxx rasmi di Pejabat Tanah xxx/atau xxxx-xxxx Pihak-pihak Berkuasa yang berkenaan xxx (iv) membuat pertanyaan dengan Pihak Berkuasa yang berkenaan samada jualan ini terbuka kepada semua bangsa atau kaum Bumiputra Warganegara Malaysia sahaja atau melayu sahaja xxx juga mengenai persetujuan untuk jualan ini sebelum jualan lelong.Penawar yang berjaya ("Pembeli") dikehendaki dengan segera memohon xxx mendapatkan kebenaran pindahmilik (jika ada) daripada Pihak Pemaju xxx/atau Pihak Tuanpunya xxx/atau Pihak Berkuasa Negeri atau badan-badan berkenaan (v) memeriksa xxx memastikan samada jualan ini dikenakan cukai. HAKMILIK : Hakmilik strata bagi hartanah ini masih belum dikeluarkan HAKMILIK INDUK / NO. LOT : Pajakan Negeri 35263, Lot No.29096 MUKIM/DAERAH/NEGERI : Setapak / Kuala Lumpur / Wilayah Persekutuan Kuala Lumpur PEGANGAN : Pajakan selama 82-tahun berakhir pada 08/08/2085 KELUASAN LANTAI : 81.104 meter persegi ( 873 kaki persegi ) PEMAJU/PENJUAL : Mega Planner Jaya Sdn Bhd (326287-W)(Dalam Likuidasi) TUANPUNYA : Datuk Bandar Kuala Lumpur PEMBELI : Xxxxxxxx Bin Xxxxx @ Xxxx BEBANAN : Diserahhak kepada RHB Bank Berhad [196501000373 (6171-M)] Hartanah tersebut terletak di tingkat 9 pada bangunan apartment 14-tingkat terletak di Melati Impian Apartment, Setapak Fasa 1, Kuala Lumpur. Hartanah tersebut adalah sebuah unit apartment 3 xxxxx dikenali sebaga Xxxxx Pemaju No. 9, Tingkat No.9, Pembangunan dikenali sebagai Melati Impian Apartment Setapak Fasa 1, Kuala Lumpur xxx mempunyai alamat surat-xxxxxxxx xx Xxxx Xx. 0-0, Xxxxxx Impian Apartment, Xxxxx 0/00X, Xxxxx Xxxxxx, 00000 Xxxxx Xxxxxx, Xxxxxxx Xxxxxxxxxxx Xxxxx Xxxxxx. Harta ini dijual “keadaan seperti mana sediada” dengan harga rizab sebanyak RM 300,000.00 (RINGGIT MALAYSIA: TIGA RATUS RIBU SAHAJA) xxx tertakluk kepada syarat-syarat Jualan xxx melalui penyerahan hakkan dari Pemegang Serahak, tertakluk kepada kelulusan di perolehi oleh pihak Pembeli daripada pihak berkuasa, jika ada, termasuk semua terma, syarat xxx perjanjian yang dikenakan xxx mungkin dikenakan oleh Pihak Berkuasa yang berkenaan. Pembeli bertanggungjawab sepenuhnya untuk memperolehi xxx mematuhi syarat-syarat berkenaan daripada Pihak Berkuasa yang berkenaan, jika ada xxx semua xxx xxx perbelanjaan ditanggung xxx dibayar oleh Xxxxx Xxxxxxx.Pembeli atas talian (online) juga tertakluk kepada terma-terma xxx syarat-syarat terkandung dalam xxx.xxxxxxxxxxxxxxxx.xxx Pembeli yang berminat adalah dikehendaki mendeposit kepada Pelelong 10% daripada harga rizab dalam bentuk Bank Draf atau Cashier’s Order di atas nama RHB Bank Berhad sebelum lelongan awam xxx xxxx xxxx xxxxxx hendaklah dibayar dalam tempoh sembilan puluh (90) hari dari tarikh lelongan kepada RHB Bank Berhad melalui Bank Draf / XXXXXX. Butir-butir pembayaran melalui XXXXXX, xxxx berhubung dengan Tetuan Zahrin Emrad & Sujaihah. Untuk maklumat lanjut, xxxx berhubung dengan TETUAN ZAHRIN EMRAD & SUJIAHAH, yang beralamat di Suite 10.3, 10th Floor, Xxx Xxxx Building, Xx.00, Xxxxx Xxxx Xxxxxx, 00000 Xxxxx Xxxxxx. Tel: 00-0000 0000 / Fax: 00-0000 0000. [ Ruj: ZES/ZHR/RHB-FC/16250-17/0614-pae ], peguamcara bagi pihak pemegang xxxxx xxx atau pelelong yang tersebut dibawah.

  • Due Formation The Purchaser is duly formed, validly existing and in good standing in the jurisdiction of its organization. The Purchaser has all requisite power and authority to carry on its business as it is currently being conducted.

  • Name; Formation The name of the Company shall be ARAMARK Sports and Entertainment Services, LLC or such other name as the Member may from time to time hereafter designate. The Company constitutes a continuation of the existence of the Converted Corporation in the form of a Delaware limited liability company. In accordance with Section 18-214(b) of the Act, the Certificate of Conversion (converting the Converted Corporation to the Company) and the Certificate of Formation of the Company have been duly executed by a Member or other person designated by a Member or by any officer, agent or employee of the registered agent of the Company in the State of Delaware (any such person being an authorized person to take such action) and filed in the Office of the Secretary of State of the State of Delaware. As provided in Section 18-214(d) of the Act, the existence of the Company is deemed to have commenced on February 28, 1966, the date the Converted Corporation was originally organized under the laws of the State of Delaware.

  • Company Formation The Company has been formed as a limited liability company under and pursuant to the Act. The Managers shall file the Certificate and all other such instruments or documents and shall do or cause to be done all such filing, recording, or other acts, as may be necessary or appropriate from time to time to comply with the requirements of law for the formation and/or operation of a limited liability company in the State of Delaware. The Managers may also direct that the Company be registered or qualified to do business in other jurisdictions.

  • Contract Formation Subject to FAR Sections 1.601(a) and 43.102, the Government Order must be signed by a duly warranted contracting officer, in writing. The same requirement applies to contract modifications affecting the rights of the parties. All terms and conditions intended to bind the Government must be included within the contract signed by the Government.

  • Cloud storage DSHS Confidential Information requires protections equal to or greater than those specified elsewhere within this exhibit. Cloud storage of Data is problematic as neither DSHS nor the Contractor has control of the environment in which the Data is stored. For this reason: (1) DSHS Data will not be stored in any consumer grade Cloud solution, unless all of the following conditions are met: (a) Contractor has written procedures in place governing use of the Cloud storage and Contractor attests in writing that all such procedures will be uniformly followed. (b) The Data will be Encrypted while within the Contractor network. (c) The Data will remain Encrypted during transmission to the Cloud. (d) The Data will remain Encrypted at all times while residing within the Cloud storage solution. (e) The Contractor will possess a decryption key for the Data, and the decryption key will be possessed only by the Contractor and/or DSHS. (f) The Data will not be downloaded to non-authorized systems, meaning systems that are not on either the DSHS or Contractor networks. (g) The Data will not be decrypted until downloaded onto a computer within the control of an Authorized User and within either the DSHS or Contractor’s network. (2) Data will not be stored on an Enterprise Cloud storage solution unless either: (a) The Cloud storage provider is treated as any other Sub-Contractor, and agrees in writing to all of the requirements within this exhibit; or, (b) The Cloud storage solution used is FedRAMP certified. (3) If the Data includes protected health information covered by the Health Insurance Portability and Accountability Act (HIPAA), the Cloud provider must sign a Business Associate Agreement prior to Data being stored in their Cloud solution.

  • COVID-19 Vaccine Passports Pursuant to Texas Health and Safety Code, Section 161.0085(c), Contractor certifies that it does not require its customers to provide any documentation certifying the customer’s COVID-19 vaccination or post-transmission recovery on entry to, to gain access to, or to receive service from the Contractor’s business. Contractor acknowledges that such a vaccine or recovery requirement would make Contractor ineligible for a state-funded contract.

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • Drainage Systems (1) Clear culvert inlets, outlets, and sediment catching basins. (2) Maintain waterbars, drainage dips, and other water diversion measures. (3) During active use, patrol and maintain functional drainage. (4) Repair damaged culvert ends.

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