|
Please wait ......
LTSC PAPI - Conformance
Terms of use
X
Terms of use
These contents have been obtained from the IEEE LTSC web site and edited for presentation. Please refer to the IEEE LTSC web site for additional information on terms of use.
Print
The PAPI Learner Standard describes four types of obligation attributes for data elements: mandatory, optional, conditional, and extended:- Mandatory data elements are always required for the data structure to be valid. An implementation that does not support or include one or more mandatory data elements is a non-conforming implementation.
- Optional data elements are permitted, but not required, for the data structure to be valid. An implementation that does not support one or more optional data elements is a non-conforming implementation.
- Conditional data elements are required, but their requirement is dependent upon certain conditions. An implementation that does not support one or more conditional data elements is a non-conforming implementation.
- Extended data elements are not permitted within strictly conforming implementations. Extended data elements are permitted within conforming implementations to the extent that the implementation individually supports each extended data element. Extensions are motivated by needs of users, vendors, institutions, and industries (1) that are not directly specified by the PAPI Learner Standard, (2) that are specified and agreed to outside the PAPI Learner Standard, and (3) that may serve as trial usage for future editions of the PAPI Learner Standard.
|
| There two flawors of conformance implementations: "Strictly conforming" and "conforming". They are necessary to address the simultaneous needs for interoperability and extensions. |
Strictly Conforming Implementations
A Strictly Conforming implementation:- shall support all mandatory and optional data elements;
- shall not use, test, access, or probe for any extension features or extended data elements;
- shall not exceed limits or smallest permitted maximum values specified by this Standard; and
- shall not interpret or generate data elements that are dependent on any unspecified, undefined, implementation-defined, or locale-specific behavior.
|
| NOTE — The use of extension features or extended data elements is undefined behavior. |
Conforming Implementations
A Conforming implementation:- shall support all mandatory and optional data elements;
- may use, test, access, or probe for extension features or extended data elements, as permitted by the implementation and data interchange participants, as long as the meaning and behavior of strictly conforming implementations is unchanged;
- shall not support or use extension features or extended data elements that change the meaning or behavior of strictly conforming implementations;
- may exceed limits or smallest permitted maximum values specified by this Standard, and to the extent permitted by the implementation; and
- may interpret or generate data elements that are dependent on implementation-defined, locale-specific, or unspecified behavior.
|
NOTE 1 — The use of extension features or extended data elements is undefined behavior.
NOTE 2 — All strictly conforming implementations are also conforming implementations.
NOTE 3 — An implementation does not conform to this Standard if it redefines Standard features via extension methods, and these features change the meaning or behavior of strictly conforming implementations |
Non-Conforming Implementations
A Non Conforming implementation is an implementation that does not conform to this Standard (either strictly conforming or merely conforming). |
|