Skip to content

Commit

Permalink
Merge pull request #518 from dginev/does-not-exclude-implementations
Browse files Browse the repository at this point in the history
[wording] no restrictions from supported concept definition
  • Loading branch information
NSoiffer authored Nov 14, 2024
2 parents a388709 + 6533d8a commit 972e052
Showing 1 changed file with 3 additions and 0 deletions.
3 changes: 3 additions & 0 deletions src/intent.html
Original file line number Diff line number Diff line change
Expand Up @@ -316,6 +316,9 @@ <h3 id="intent_using">Using Intent Concepts and Properties</h3>
<p>A concept is considered a <dfn id="intent_supported_concept">supported concept</dfn> (by the AT)
when the normalized name, the fixity property, and the arity
all match an entry in the AT's concept dictionary.
This does not exclude implementations which support additional concepts,
as well as concepts with many arities, fixities or aliases,
as long as they are mapped appropriately.
The speech hint in the matching entry
can be used as a guide for the generation of
specific audio, replacement text or braille renderings, as appropriate.
Expand Down

0 comments on commit 972e052

Please sign in to comment.