Skip to content

Intent interpretation #543

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.

Sign up for GitHub

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Intent interpretation #543

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
451d6a7
adjust grammar to allow properties on applications
davidcarlisle Oct 11, 2025
e38177f
describe interpretation fo intent expressions
davidcarlisle Oct 11, 2025
5bd97b4
proof read edits
davidcarlisle Oct 12, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
78 changes: 74 additions & 4 deletions src/intent.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,8 +60,8 @@ <h3 id="mixing_intent_grammar">The Grammar for <code class="attribue">intent</co
<pre class="def bnf">
intent := self-property-list | expression
self-property-list := property+ S
expression := S ( term property* | application ) S
term := concept-or-literal | number | reference
expression := S ( term property* ) S
<dfn id="intent_term">term</dfn> := concept-or-literal | number | reference | application
concept-or-literal := NCName
number := '-'? \d+ ( '.' \d+ )?
reference := '$' NCName
Expand Down Expand Up @@ -140,8 +140,7 @@ <h3 id="mixing_intent_grammar">The Grammar for <code class="attribue">intent</co
the core properties as described below.</p>
</dd>

<!-- <dt><dfn id="intent_property_list">self-property-list</dfn></dt>-->
<dt>self-property-list</dt>
<dt><dfn id="intent_property_list">self-property-list</dfn></dt>
<dd>At the top level, an [=intent=] may consist of just a
non-empty list of properties. These apply to the current element
as described in <a href="#intent_using"></a>.</dd>
Expand Down Expand Up @@ -370,6 +369,77 @@ <h3 id="intent_using">Using Intent Concepts and Properties</h3>
produce speech that is appropriate to the community they serve.</p>
</section>

<section>
<h3 id="mixing_intent_interpretation">Interpreting intent expressions</h3>
<p>The exact effect of intent expressions on constructed speech or braille is system dependent however
systems should act in a way consistent with the interpretations decribed in this section.</p>
<section>
<h4 id="mixing_intent_multiple properties">Multiple properties</h4>
<p>If multiple properties appear in a [=self-property-list=] or <a
href="#mixing_intent_grammar"><code>term</code></a> then they are
evaluated left-to right. In general all the properties may have
an effect but in many cases groups of properties all set the same
internal <i>parameter</i> and so their effects are mutually exclusive
and the last one will take effect.</p>
<p>For example, <code>f:prefix:suffix</code> will act as
<code>f:suffix</code> as both properties set the fixity <i>parameter</i>. Similarly
<code>:literal:common</code> will act as <code>:common</code> as
both properties set the default interpretation <i>parameter</i>.
Conversely <code>f:pause-medium:prefix</code> would be the same as
<code>f:prefix:pause-medium</code> as both properties would have
an effect.</p>
</section>
<section>
<h4 id="mixing_intent_argref">Expanding arg references</h4>
<p>When interpreting an intent expression that includes a
[=reference=], the reference may be replaced by the <i>effective
intent</i> of the referenced element. That is, if the referenced
element has an <code>intent</code> attribute with an intent
<i>expression</i> then the reference may be replaced by the expression,
note that any properties following the reference will be at the
end of the combined expression and so take priority over
properties on the referenced element. If the referenced element
has no <code>intent</code>, or if the <code>intent</code> is a
[=self-property-list=] then the effective intent of the element,
along with any properties from the <i>property list</i> will be used as
the replacement form the reference.
The effective intent of an element with no explicit intent
expression is system specific but should be compatible with the
current
default rules for inferring intent (typically <i>common</i> or
<i>literal</i>) The value may either be an inferred intent expression
or may be a [=literal=] corresponding to the speech term that
would be generated for that element.</p>
</section>
<section>
<h4 id="mixing_intent_self_properties">Interpretation of self-properies</h4>
<p>Properties that are part of a [=self-property-list=] (i.e., an
<i>intent</i> value starting with a colon, <code>:</code>) are known as
<dfn>self-properties</dfn>. The effect of any such property is
limited to the element (and its descendants) although the precise
effect depends on the definition of the property. So for
example:</p>
<ul>
<li>
<code>&lt;mrow
intent=":pause-medium">&lt;mi>x&lt;/mi>...&lt;/mrow></code>
would inicate there should be a pause in speech before the
<code>mrow</code> is procesed (it would not cause a pause before
all descentant elements.
</li>
<li><code>&lt;mrow
intent=":literal">&lt;mi>x&lt;/mi>...&lt;/mrow></code>
would set the <i>parameter</i> corresponding to the default intent inference
rules to <code>literal</code> this would cause the intent for this
<code>mrow</code> including all its descendants to use the
<code>literal</code> rules for inferring intent unless they have
an explicit intent or use another [=self-property=] such as
<code>:common</code> to over-ride this.</li>
</ul>
</section>


</section>
<section>
<h3 id="mixing_intent_errors">Intent Error Handling</h3>
<p>An intent processor may report errors in intent expressions in
Expand Down