Skip to content

Commit

Permalink
Cleaned up cross references in Annex C
Browse files Browse the repository at this point in the history
  • Loading branch information
cmheazel committed Feb 25, 2025
1 parent 665d818 commit 350a2e4
Show file tree
Hide file tree
Showing 7 changed files with 2,248 additions and 2,717 deletions.
4 changes: 2 additions & 2 deletions sources/document.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -3,12 +3,12 @@
:docsubtype: logical-model
:status: Draft
:committee: technical
:docnumber: 08-131r3
:docnumber: 08-131r4
:edition: 1.1.0
:received-date: 2025-02-25
:issued-date: 2025-xx-xx
:published-date: 2025-xx-xx
:copyright-year: 2024
:copyright-year: 2025
:fullname: Carl Reed
:role: editor
:fullname_2: John Herring
Expand Down
1,079 changes: 345 additions & 734 deletions sources/document.err.html

Large diffs are not rendered by default.

1,008 changes: 518 additions & 490 deletions sources/document.html

Large diffs are not rendered by default.

Binary file modified sources/document.pdf
Binary file not shown.
1,906 changes: 937 additions & 969 deletions sources/document.presentation.xml

Large diffs are not rendered by default.

899 changes: 413 additions & 486 deletions sources/document.xml

Large diffs are not rendered by default.

69 changes: 33 additions & 36 deletions sources/sections/ac-definitions.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -8,55 +8,52 @@
order. It may be easier to understand the more significant terms in the following
less formal definitions arranged in a bottom-up order:

. a {{standardization target type}} is a type of entity about which a standard
is written. An instance of a {{standardization target type}} is a
{{standardization target}}. A standard may address multiple targets in separate
<<conformance-class,_conformance classes_>>.
. a <<StandardizationTargetType-definition,_standardization target type_>> is a type of entity about which a standard
is written. An instance of a <<StandardizationTargetType-definition,_standardization target type_>> is a
<<StandardizationTarget-definition,_standardization target_>>. A standard may address multiple targets in separate
<<ConformanceClass-definition,_conformance classes_>>.

. a {{requirement}} is a statement of a condition to be satisfied by a single
{{standardization target type}}, and it must be stated in "normative" language.
. a <<Requirement-definition,_requirement_>> is a statement of a condition to be satisfied by a single
<<StandardizationTargetType-definition,_standardization target type_>>, and it must be stated in "normative" language.

. a {{conformance test}} checks if a set of
{{requirement,requirements}} are met (*pass*) or not met (*fail*) by a
{{standardization target}}. The relationship between {{conformance test,
conformance tests}} and {{requirement,requirements}} is many-to-many.
. a <<ConformanceTest-definition,_conformance test_>> checks if a set of
<<Requirement-definition,_requirements_>> are met (*pass*) or not met (*fail*) by a
<<StandardizationTarget-definition,_standardization target_>>. The relationship between <<ConformanceTest-definition,_conformance tests_>> and <<Requirement-definition,_requirements_>> is many-to-many.

. all {{conformance test, conformance tests}} are graded as *pass* or *fail*
against each instance of the {{standardization target}}.
. all <<ConformanceTest-definition,_conformance tests_>> are graded as *pass* or *fail*
against each instance of the <<StandardizationTargetType-definition,_standardization target type_>>.

. a {{requirement}} is associated to one {{conformance test}}.
. a <<Requirement-definition,_requirement_>> is associated to one <<ConformanceTest-definition,_conformance test_>>.

. a {{recommendation}} is a suggestion and is not associated to any
{{conformance test}}.
. a <<Recommendation-definition,_recommendation_>> is a suggestion and is not associated to any
<<ConformanceTest-definition,_conformance test_>>.

. a {{requirements class}} is a set of one or more {{requirement,requirements}}
all with the same {{standardization target type}}.
. a <<RequirementsClass-definition,_requirements class_>> is a set of one or more <<Requirement-definition,_requirements_>>
all with the same <<StandardizationTargetType-definition,_standardization target type_>>.

. a {{conformance test class,conformance (test) class}} is a collection of
{{conformance test,conformance tests}} that are associated to and only to the
requirements in a corresponding {{requirements class}}.
. a <<ConformanceClass-definition,_conformance (test) class_>> is a collection of
<<ConformanceTest-definition,_conformance tests_>> that are associated to and only to the
requirements in a corresponding <<RequirementsClass-definition,_requirements class_>>.

. a {{conformance test module,conformance (test) module}} is also collection of
{{conformance test classes,conformance test classes}} that group
{{conformance test, conformance tests}} on a single
{{standardization target type}}.
. a <<ConformanceTestModule-definition,_conformance (test) module_>> is also collection of
<<ConformanceClass-definition,_conformance test classes_>> that group
<<ConformanceTest-definition,_conformance tests_>> on a single
<<StandardizationTargetType-definition,_standardization target type_>>.

. a *conformant implementation* is a {{standardization target type}} that has
successfully passed all tests in a specified {{conformance test
class,conformance (test) class}} and received a {{certificate of conformance}}
. a *conformant implementation* is a <<StandardizationTargetType-definition,_standardization target type_>> that has
successfully passed all tests in a specified <<ConformanceClass-definition,_conformance (test) class_>> and received a <<CertificateOfConformance-definition,_certificate of conformance_>>.

. the {{core requirements class}} of a standard is the minimal set of
{{requirement,requirements}} which must be supported by all *conformant
implementations*. If a standard addresses multiple {{standardization target
type,standardization target types}}, it may have a *core* for each *target
. the <<CoreRequirementsClass-definition,_Core requirements class_>> of a standard is the minimal set of
<<Requirement-definition,_requirements_>> which must be supported by all *conformant
implementations*. If a standard addresses multiple <<StandardizationTargetType-definition,_standardization target types_>>, it may have a *core* for each *target
type*.

. an *extension* of a {{requirements class}} is an additional {{requirements class}}
(the extension) that adds additional {{requirement,requirements}} to the first
{{requirements class}} (the *base requirements class* being extended). The
extension is said to be dependent on the *base*. Any {{conformance test class}}
. an *extension* of a <<RequirementsClass-definition,_requirements class_>> is an additional <<RequirementsClass-definition,_requirements class_>>
(the extension) that adds additional <<Requirement-definition,_requirements_>> to the first
<<RequirementsClass-definition,_requirements class_>> (the *base requirements class* being extended). The
extension is said to be dependent on the *base*. Any <<ConformanceClass-definition,_conformance (test) class_>>
must identify all its dependencies during the execution of conformance tests
against a candidate {{standardization target}}.
against a candidate <<StandardizationTarget-definition,_standardization target_>>.

[[annex-C-2]]
=== UML Model
Expand Down

0 comments on commit 350a2e4

Please sign in to comment.