A webapp for the syntax-prosody analyst working in Optimality Theory, with automated Gen, Con and Eval. Download build files from syntax-prosody-ot/build
What do you think about adding a combined syntax <--> prosody mapping constraint to the interface? I am using it in my SS/ES investigation to cut down the complexity of the typology. This is analogous to a "symmetrical faithfulness" type of constraint Eric Bakovic was using in a talk I just heard from him (which i think was based on his AMP2020 paper with Anna Mai), which also had to do with special/general interactions in markedness. In that project, symmetrical FAITH was basically IDENT(Feature), but insofar as IDENT(F) is basically a combination of MAX(F) with DEP(F), and MatchSP is essentially MAX(phi) while MatchPS is essentially DEP(phi), the principle is the same. We can just keep it on the backend or demote it to the "Show more..." section if you think it's too odd to have up top. But I think it's quite useful for simplifying the typology.
What do you think about adding a combined syntax <--> prosody mapping constraint to the interface? I am using it in my SS/ES investigation to cut down the complexity of the typology. This is analogous to a "symmetrical faithfulness" type of constraint Eric Bakovic was using in a talk I just heard from him (which i think was based on his AMP2020 paper with Anna Mai), which also had to do with special/general interactions in markedness. In that project, symmetrical FAITH was basically IDENT(Feature), but insofar as IDENT(F) is basically a combination of MAX(F) with DEP(F), and MatchSP is essentially MAX(phi) while MatchPS is essentially DEP(phi), the principle is the same. We can just keep it on the backend or demote it to the "Show more..." section if you think it's too odd to have up top. But I think it's quite useful for simplifying the typology.