Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| public:99_annexes:annex-b-terms-and-definitions:c:conformance_profile [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:c:conformance_profile [2026/09/13 17:06] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Conformance Profile ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | A Conformance Profile identifies a defined set of applicable [[public: | ||
| + | |||
| + | A Conformance Profile allows a specification to define alternative or specialized conformance targets while preserving a common [[public: | ||
| + | |||
| + | A Conformance Profile specifies which Requirements apply, any conditions governing their applicability, | ||
| + | |||
| + | A Conformance Profile supports consistent evaluation across subjects that perform different roles, provide different capabilities, | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | // | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | * [[private: | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | A Conformance Profile does not modify the meaning of a Requirement. | ||
| + | |||
| + | A Conformance Profile identifies which Requirements apply to the identified subject. | ||
| + | |||
| + | A subject may conform to one or more Conformance Profiles defined by a specification. | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | A DIDO-TE specification defines separate Conformance Profiles for a Test Node, a Management Node, and a Test Client. Each profile identifies the Requirements applicable to that class of subject. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||