Modules: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
== Goals of the Logical Language Modules Project == | |||
Build a Library of Logical Language Modular Components and Tools. | |||
These components should aim to: | |||
* A full logical language can be assembled wholly or partly from existing modules. | |||
** Innovators can focus on developing a new module rather than a whole language. | |||
* Enumerate the design space of Logical Languages. | |||
** Provide alternate modules for different design choices. | |||
* Describe modules' strengths, weaknesses, and compatibility. | |||
** Do not apply value judgements or advocate for any particular option. | |||
* Be systematic and well documented. | |||
** A method or a choice without documented justification will be lost. | |||
* Provide software for working with these components. | |||
== Modular Language Architecture == | == Modular Language Architecture == | ||
This section will explore how a language could be broken down into modules. | This section will explore how a language could be broken down into modules. | ||
Line 32: | Line 48: | ||
* Structure, syntax, semantics | * Structure, syntax, semantics | ||
'''''That last one probably needs to be broken down more.''''' -- [[User:DerSaidin|DerSaidin]] ([[User talk:DerSaidin|talk]]) | |||
''''' | |||
<!-- To editors: please pay attention to the exact structure of these entries. --> | <!-- To editors: please pay attention to the exact structure of these entries. --> | ||
Revision as of 06:13, 26 March 2020
Goals of the Logical Language Modules Project
Build a Library of Logical Language Modular Components and Tools.
These components should aim to:
- A full logical language can be assembled wholly or partly from existing modules.
- Innovators can focus on developing a new module rather than a whole language.
- Enumerate the design space of Logical Languages.
- Provide alternate modules for different design choices.
- Describe modules' strengths, weaknesses, and compatibility.
- Do not apply value judgements or advocate for any particular option.
- Be systematic and well documented.
- A method or a choice without documented justification will be lost.
- Provide software for working with these components.
Modular Language Architecture
This section will explore how a language could be broken down into modules.
Module Breakdown
- Phonotactics
- Different rules for how a phonology can be assembled into words.
- Writing System
- Structure, Syntax, and Semantics
- Vocabulary
- Provides set of non-core/non-syntactic/non-structural words with defined meanings
- Not attached to specific phonological forms
- Different vocabulary module instances could incorporate different philosophies
- e.g. world view for constructing composites:
- Have a word for 'tooth', or have a compound like 'mouth-stone'?
Module Hierarchy
- Morphology
- Written
- Writing System
- Verbal
- Phonotactics
- Phonology
- Phonotactics
- Written
- Vocabulary
- Structure, syntax, semantics
That last one probably needs to be broken down more. -- DerSaidin (talk)
Morphology
- Self-segmentation strategies
- Continuation marker
- certain feature or features of a syllable is used to determine if it is a continuation of the previous word
- Sentinel value
- programming concept: special predetermined value as a signal for termination
Syntax
Predicates and their arguments
- Sentence functions
- Predicate–argument
- predicates, together with arguments, form predications; both must be present (at least implicitly)
see(man, cat)
- present in most logical languages
- Predicate–variable
- predicates only accept variable labels as terms; these, in turn, can be bound by quantifier expressions and restricted with subsequent predicate clauses
- Predicate
- no arguments are exposed; predicates are implicitly connected with quantified variables
man₁ = see₁; see₂ = cat₁
- Ad-hoc predicate composition
- Serial predicates
- the embedding of one predicate's structure inside another
- Compound metaphors
- predicate apposition as modification of one predicate's meaning by the other's
- Lojban has a highly developed appositional tanru grammar
Numbers and counting
- Representation
- Numerals as a part of speech
- numbers constitute a separate grammatical class
- Composition
- Usage
- As quantifiers
- numbers attach to terms and scope over the predicate, signifying how many possible values of the term satisfy the predicate
- Lojban: ci da (lit. ‘three something’) = ‘there exist exactly three things that…’[13]. Lojban has an extensive assortment of number grammar particles which allow to construct more elaborate quantifications: for example, su'o (pa) ‘at least one’ for ∃, ro ‘all’ for ∀, or even things like da'a su'e rau ‘all but at most enough’.
References
- ↑ http://toaq.org/#compound_predicates
- ↑ https://mw.lojban.org/papri/X-1#Morphology
- ↑ https://lojban.github.io/cll/4/3/
- ↑ https://lojban.github.io/cll/4/8/
- ↑ https://mw.lojban.org/papri/BPFK_Section:_cmevla
- ↑ https://lojban.github.io/cll/19/10/
- ↑ https://mw.lojban.org/papri/X-1#Sample
- ↑ http://toaq.org/#serial_predicates
- ↑ http://www.jfcarter.net/~jimc/guaspi/acmpaper.html
- ↑ https://mw.lojban.org/papri/User:Gleki/turtau
- ↑ 11.0 11.1 https://lojban.github.io/cll/18/2/
- ↑ http://toaq.org/#numbers
- ↑ https://lojban.github.io/cll/6/6/