Table 11.1 — Table of contents
Table 11.1 — Table of contents | Table 11.3 — Minimum requirements for EDCS API conformance |
Table 11.2 — Table of tables |
This clause specifies conformance of:
Conformance enhances the likelihood of successful interoperability among applications.
Profile conformance provides for the specification of well-known subsets of this International Standard. The default profile requires support for the EDCS codes and EDCS labels for all EDCS dictionary entries. Additionally, the default profile requires support for the EDCS abstract elements and associated EDCS representation types as specified in Table 9.5.
An information coding specification, application, and/or exchange format may conform to:
Let L be an EDCS label defined either in this International Standard or by registration. An information coding specification, application, and/or exchange format conforming to an EDCS label L shall:
Let C be an EDCS code defined either in this International Standard or by registration. An information coding specification, application, and/or exchange format conforming to an EDCS code C shall:
Let R be the representation of an EDCS attribute value type T for EDCS attribute A defined in either this International Standard or by registration. An information coding specification, application, and/or exchange format conforming to the representation of EDCS attribute A shall meet the following requirements:
This International Standard language specifies the conformance of programming language bindings that realize the EDCS API. Conformance requirements include the degree of flexibility allowed when performing conversions of EDCS attribute values given with respect to different units of measure and unit scales. This International Standard does not directly address the hardware, software and/or performance requirements of implementations of the EDCS API, nor does it dictate the functionality of applications that may use the EDCS API.
An EDCS API language binding conforming information coding application shall:
Programming language bindings are allowed to prepend and/or postpend additional information to an EDCS label and/or abbreviate components of an EDCS label to make the symbolic constant corresponding to an EDCS label unique and identifiable as part of the language binding while following the strictures of the programming language to which a label is bound (see 9.4).
If a programming language binding standard exists for the programming language in question, the provisions of that standard shall be followed.
All programming language bindings shall apply the following provisions:
This International Standard specifies the conformance of exchange formats that incorporate EDCS labels, EDCS codes, and/or the representations of EDCS attribute values, as well as conformance requirements for generators and readers of these exchange formats. Conformance requirements include the degree of flexibility allowed for generators and readers of such formats. This International Standard does not directly address the hardware, software, and/or performance requirements of generators and/or readers, nor does it dictate the functionality of generators and/or readers that may incorporate EDCS labels, EDCS codes, and/or the representations of EDCS attribute values.
The concept of an EDCS profile is defined in 10.14. Two EDCS profiles are defined in this International Standard. These are the EDCS default profile (see 11.3.3) and the EDCS unit profile (see 11.3.4). Other profiles may be developed and registered as EDCS profiles. Conformance is specified in the context of an EDCS profile for:
Let P be one of: the EDCS default profile, the EDCS unit profile, or a registered EDCS profile. An EDCS exchange format conforming to profile P shall:
Let P be one of: the EDCS default profile, the EDCS unit profile, or a registered EDCS profile. An application that generates an exchange format based on the EDCS that conforms to profile P shall:
Let P be one of: the EDCS default profile, the EDCS unit profile, or a registered EDCS profile. An EDCS reader conforming to profile P shall:
There are no additional minimum requirements for conformance to an EDCS label, an EDCS code, and/or the representation of an EDCS attribute value. The minimum requirements for the representation of EDCS attribute values are given in 11.2.1.4. Application requirements may be met by using any:
All implementations of language bindings to the EDCS application program interface shall support the minimum level of functionality defined in Table 11.3.
Table 11.3 — Minimum requirements for EDCS API conformance
Function |
Binding support |
ConvertQuantityValue | Full support as required by the individual service request. |
GetHighestCodesUsed | Full support as required by the individual service request. |
The EDCS default profile includes:
The EDCS default profile contains no EDCS profile constraints.
An implementation conforming to the EDCS default profile shall support all EDCS attribute value types and their corresponding EDCS representation types as specified in Table 9.5.
The EDCS unit profile includes:
The EDCS unit profile contains no EDCS profile constraints.
An implementation conforming to the EDCS unit profile shall support EDCS codes, EDCS labels, or both and their corresponding EDCS representation types as specified in Table 9.5.
A registered EDCS profile shall include at least one concept from an EDCS dictionary and its corresponding EDCS code and EDCS label, as well as the EDCS representation types for EDCS codes and EDCS labels as specified in Table 9.5.
A registered EDCS profile may contain any number of EDCS profile constraints including zero.
http://www.iso.ch/iso/en/ittf/PubliclyAvailableStandards/ISO_IEC_18025_Ed1.html