Enhance Sentence Editor

[RyanFleck]

I was checking again through the precise structure of the user-constructed sentences in RM, and I'd like to refine these as follows:

• [Article]*
• [past participle]
• [attribute noun]
• [preposition]*
• [article]*
• [subject noun]
• [auxiliary verb]*
• [boolean phrase]*
• [adjectival or arithmetic expression].

* Five of these fields are constrained to drop-down lists shown below, while the rest are editable fields with the default prompt text being the grammatical identifiers shown above.

• Article: the, a, an
• Preposition: in, on, with, of
• Auxiliary Verb: is, was, has been, will be
• Boolean phrase: deemed, equal to, not equal to, less than, greater than, less than or equal to, greater than or equal to

On balance I think the boolean field works best here in words instead of symbols. I would also suggest there should be a 240-character limit on each constructed sentence, i.e. the sum of characters taking all the fields together. This would be both to force moderation in verbosity, and it would constrain malicious entries.

[jpotvin]

We need this to given greater priority than an enhancement. It's more a correction to my insufficient thought about the required grammatical structure of the sentence. Since this is our #1 channel for rules-as-data input, this can't be delayed.

[jpotvin]

Updated. Same structure, but terminology to conform with MRS (Minimal Recursion Semantics)

• [Determiner]*
• [Verb, past participle]
• [Noun (attribute)]
• [Preposition]*
• [Determiner]*
• [Noun (subject)]
• [Verb (auxiliary)]*
• [Boolean expression]*
• [Adjective OR arithmetic expression]