Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PhonologicalRule #417

Open
3 tasks
dwhieb opened this issue Aug 31, 2020 · 1 comment
Open
3 tasks

PhonologicalRule #417

dwhieb opened this issue Aug 31, 2020 · 1 comment
Labels
schemas Changes to schemas

Comments

@dwhieb
Copy link
Member

dwhieb commented Aug 31, 2020

Create a new PhonologicalRule schema. Each Phonological Rule should have the following properties:

For now, we can leave the formula as a simple string. Later, we may implement input, output, and environment fields. This would be a fairly complex task though. We'd need to support:

  • features (probably with a Phonological Features object, whose property values are Booleans)
  • alpha/beta notation (probably by also allowing a or b as values of properties in the Phonological Features object)
  • disjunction (with curly brackets)
  • sequences (Cx; maybe just C/V followed immediately by a number)
  • epenthesis / deletion (probably by allowing empty strings as input/output)
  • boundaries (syllable σ or s; morpheme +; word #)
  • natural classes (maybe): consonant C; vowel V; glide/semivowel W; sibilant S; rhotic R; lateral L; nasal N; maybe others
  • both the input and output will probably need to be arrays, where each item in the array is either a phoneme (string), natural class (string), feature set (object), or boundary (string)

Take a look at this repo for implementation ideas: https://github.com/TriMill/sca

@dwhieb dwhieb added the schemas Changes to schemas label Aug 31, 2020
@dwhieb dwhieb added this to the v1.1.0 milestone Aug 31, 2020
@dwhieb dwhieb changed the title Lexeme.phonologicalClass LexemeForm.phonologicalClass Nov 16, 2020
@dwhieb dwhieb added the blocked Issue blocked label Nov 17, 2020
@dwhieb dwhieb self-assigned this Nov 17, 2020
@dwhieb dwhieb removed the blocked Issue blocked label Nov 17, 2020
@dwhieb dwhieb changed the title LexemeForm.phonologicalClass LexemeForm.phonologicalRules Feb 17, 2021
@dwhieb
Copy link
Member Author

dwhieb commented Feb 17, 2021

I think this issue is best split in two:

  • phonologicalClass(es): A simple string indicating the phonological class a morpheme belongs to. Useful for indicating which phonological rules apply to a given morpheme without having to actually specify the details of the rule for every morpheme. The value should be the key of a PhonologicalRule object.
  • PhonologicalRule: A schema object representing a phonological rule. This doesn't necessarily have to have a parent schema; it can live on its own. Each phonological rule should have a name / key, which can be used by the phonologicalClass attribute.

@dwhieb dwhieb changed the title LexemeForm.phonologicalRules PhonologicalRule Feb 17, 2021
@dwhieb dwhieb unassigned dwhieb and vadekh Feb 17, 2021
@dwhieb dwhieb removed this from the v1.1.0 milestone Jan 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
schemas Changes to schemas
Projects
None yet
Development

No branches or pull requests

2 participants