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

Better handle unexpressed arguments #240

Closed
goodmami opened this issue Jul 24, 2019 · 1 comment
Closed

Better handle unexpressed arguments #240

goodmami opened this issue Jul 24, 2019 · 1 comment
Milestone

Comments

@goodmami
Copy link
Member

Following recent discussions, it seems that relying on underspecified variables to detect unexpressed arguments (and x or e arguments to detect expressed arguments) is not a good method. Instead, expressed arguments are those which are the intrinsic variable of some EP, and the converse is true for unexpressed arguments. Thus, the SemanticStructure.arguments() function could take an expressed=bool parameter which defaults to None and includes both. If True, only include expressed arguments, and if False, only include unexpressed.

Some open questions:

  • what to do with overt unexpressed arguments? e.g., EPs or Nodes with the predicate __unexpr__ (this is a future feature; no grammars currently use this, although it could be inserted in MRS-to-DMRS conversion)
  • can we assume unexpressed arguments are always non-scopal?
  • are MRSs that differ by unexpressed argument types (e.g., ARG1: i8 vs ARG1: p8) compare as equivalent or isomorphic?

Related: #177

@goodmami
Copy link
Member Author

The unexpressed parameter to SemanticStructure.arguments() was completed in fd6f365. The open questions will have to wait for another issue.

@goodmami goodmami added this to the v1.0.0 milestone Jul 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant