Skip to content

`assume_issue`¶

Assumes that the user has asked a question, making the corresponding issue relevant without asking the user to state it. The DDD should contain a matching resolve goal for that question.

<assume_issue type="wh_question" predicate="departure_time"/>

Attributes and children¶

Attribute	Meaning
`type`	Required by the Tala XML compiler. Supported question types are `goal`, `wh_question`, `kpq`, `alt_question`, and `yn_question`.
`predicate`	Predicate for a predicate-backed question.
`insist`	Optional Boolean. When true, reopens the issue even if it was already resolved.

Without insistence, an issue already resolved in shared commitments does not need to be raised again. With insist="true", existing resolving answers are cleared and the question is raised again.

Question content can include embedded_question for a KPQ. A KPQ wraps the question whose answer is being checked:

<assume_issue type="kpq">
  <embedded_question type="wh_question" predicate="destination"/>
</assume_issue>

Can appear in a goal's plan or postplan, or in an if branch. It has no plan-item children other than question content. Unlike raise, it represents an issue as already asked by the user. Unlike findout, it does not itself ask the user to resolve the question.

DDD JSON form:

{"assume_issue": {"question": {"kpq": {"question": {"wh": {"predicate": "destination"}}}}}}