 |
About This Document 0.1 |
|
| phonics | orthography | morphology | syntax & morpho-syntactics | lexicon | culture | artifacts |
The Idrani Standard Metalinguistic Specification v 0.4.1 is the only official description of the Idrani language as created by Trent M. Pehrson. All information in this document is the sole property of Trent M. Pehrson unless otherwise specified. For information on terms of use use and copyright policies, click on the link labeled 'terms of use' in the navigation bar at the top of this page. |
|
Introduction to the Standard Metalinguistic Specification (SMS) Document The Idrani Standard Metalinguistic Specification (ISMS) is a standardized document patterned after the concept of an Application Programming Interface document or API common in the field of computer programming. Like the API, the standard metalinguistic specification (SMS) is a pattern designed to describe components of language in a standard way so that consistency will lend itself to ready understanding. Like the API, the SMS has common elements on each page and also has consistent description methodologies and HTML formatting to aid in clarity and consistency. Below are the proposed methodologies for creating a SMS. Standard Metalinguistic Specification Version 0.1 Navigation and Information
Sections May Include: Metalinguistic Sections May
Include: Each Metalinguistic Section
Must Contain the Following Constituents Before Its Content: Major Navigation Bar: 40h x 800w HTML only navigation bar. Navigation bar contains links to navigation and information sections only, not to metalinguistic sections. Terms of Use and Copyright Disclaimer Table: 800w table with one column only containing a brief blurb on copyright and terms of use including mentioning of the link to terms of use in the major navigation bar and offering a link in text (e.g. The [NAME OF LANGUAGE] Standard Metalinguistic Specification is the only official description of the [NAME OF LANGUAGE] language as created by [LANGUAGE AUTHOR]. All information in this document is the sole property of [LANGUAGE AUTHOR] unless otherwise specified. For information on terms of use use and copyright policies, click on the link labeled 'terms of use' in the navigation bar at the top of this page or click here.). Hierarchical Page Content Navigation: This is a hierarchy of the sections of the page using <ul> and <li> tags and links to provide a map to the information on the page. Overview Table: 800w table with two rows and one column. The first row serves as the title bar and must have a background color identical to the background color of the page header. The text of the title bar is "[METALINGUISTIC SECTION] Overview" The Overview table describes in summary the section as well as giving information related to the background of the development of the language in regard to the section. Content Tables: Each content table is an 800w table with the first row spanning all columns. The first row of each content table must have a background color identical to the background color of the page header but in a shade lighter than the header and must bear the title of the content. The second row of the table must span all columns and have a white background. It must contain navigation links to all table in the section above it in the hierarchy, in hierarchical order from left to right and each link must be separated by a pipe. Subsequent rows must contain either links to subordinate tables in the section with accompanying descriptions or leaf node information about the language. The final row in a content table is optional and must span all columns and have a white background. It will bear the title"Usage" and contains links to usage tables with title text that describes each usage example. Content tables should be arranged first hierarchically and then by alphabetical order of the table titles. Usage Tables: Each usage table is an 800w table with the first row spanning all columns. The first row of each usage table must have a background color identical to the background color of the page header but in a shade lighter than the content tables and must bear the title of the usage. The second row of the table must span all columns and have a white background. It must contain navigation links to all tables in the section above it in the hierarchy, in hierarchical order from left to right and each link must be separated by a pipe. Subsequent rows must contain usage examples with accompanying descriptions. The final row in a content table is optional and must span all columns and have a white background. It will bear the title"Notes" and contains links to note tables with title text that describes the note. Usage tables should be arranged first by alphabetical order of the table titles beneath all content tables. Note Tables: Each note table is an 800w table with the first row spanning all columns. The first row of each note table must have a background color identical to the background color of the page header but in a shade lighter than the usage tables and must bear the title of the note. The second row of the table must span all columns and have a white background. It must contain navigation links to all tables in the section above it in the hierarchy, in hierarchical order from left to right and each link must be separated by a pipe. Subsequent rows must contain notes. Citations Table: The citations table is an 800w table. Rows in the citations table must alternate in background color between white and a complimentary color to the header color in a very light shade. Citations must have links back to an anchor at their references in the page. If a reference refers to an on-line resource, a link to that resource must be provided. Bottom Navigation: Bottom navigation will contain text only links separated by pipes. The first row of links will contain links to all the navigation sections. The second row will contain links to the metalinguistic sections. Bottom Copyright Information A text only copyright blurb will appear at the bottom of the page.
|
|
|