Skip to content

Commit

Permalink
Update act-rules-format/act-rules-format.bs
Browse files Browse the repository at this point in the history
  • Loading branch information
WilcoFiers authored Dec 5, 2024
1 parent e6b0052 commit bdeee59
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion act-rules-format/act-rules-format.bs
Original file line number Diff line number Diff line change
Expand Up @@ -634,7 +634,7 @@ Glossary {#glossary}
ACT Rules <em class="rfc2119">must</em> have a glossary section. The glossary <em class="rfc2119">must</em> contain the [=outcome=] definition, as well as any definitions used in [applicability](#applicability) and [expectations](#expectations) sections in the rule. Since changes to the definition change the rule, those definitions cannot be maintained independently of the rule. If a shared glossary is used for rules, any definition changes <em class="rfc2119">must</em> result in a new [rule version](#rule-versions) of all rules that use that definition.

<div class="note">
<p>**Note:** Rules can use multiple glossaries, some in the rule, and some outside. These can also be glossaries in other documents such as WCAG 2.2 or HTML 5. Where an external glossary term can change without a change to the rule, some indication of the glossary term's version is necessary. For example the HTML 5 standard is regularly updated, so a date can be added to the link to indicate the version that was used in authoring the rule.</p>
<p>**Note:** Rules can use multiple glossaries, some in the rule, and some outside. These can also be glossaries in other documents such as WCAG 2.2 or HTML 5. Where an external glossary term can change without a change to the rule, some indication of the glossary term's version is necessary. For example the HTML 5 standard is regularly updated, so a date can be added to the link to indicate the version that was used in authoring the rule.</p>
</div>

Issues List (optional) {#issues-list}
Expand Down

0 comments on commit bdeee59

Please sign in to comment.