ISO/IEC JTC1 SC32 WG2
Development/Maintenance
Last
Update: 2009-01-04
ISO/IEC 20944, Information
technology --
Metadata Registry Interoperability and Bindings (MDRIB)
The ISO/IEC 20944 family of standards is
being developed to provide interoperability among metadata registries
(11179-3), such as reading/writing attributes from/to a metadata
registry. However, the ISO/IEC 20944 series may be used generically, such
as for applications that are unrelated to 11179-3 metadata registries, or
applications that extend 11179-3 metadata registry attributes (attributes
outside of the 11179-3 specification).
The ISO/IEC 20944 standard is comprised of
five parts.
§ Part 1 provides the overview,
framework, common vocabulary, and common provisions for conformance.
§ Part 2 specifies Coding Bindings,
both common provisions and particular bindings
§ Part 3 specifies API Bindings, both
common provisions and particular bindings
§ Part 4 specifies Protocol Bindings,
both common provisions and particular bindings
§ Part 5 specifies common provisions
for Profiles using the 20944 family of standards.
Note: Earlier drafts of the standard were
organized into many more parts. Those
parts have now been consolidated as shown above.
Using/Applying/Implementing
the 20944 Standard
One uses a standard by referencing
the standard. Why does one need to reference standards?
|
|
Users: If you are a user (individual, organization, business, etc.),
you can describe your requirements precisely by stating something like
"Implementations shall conform to ISO/IEC 20944-5/P/MDR and ISO/IEC
20944-3/B/ECMAScript/A" -- a precise way of requiring ISO/IEC 11179-3
and ECMAScript/JavaScript interoperability. The purpose of describing
user's requirements precisely is: implementers (and users) can determine if
individual systems meet the user's requirements. In theory, IF a user
states "my requirements are standards X, Y, and Z" AND an
implementer declares that his/her implementation "conforms to standards
X, Y, and Z", THEN the user's requirements have been satisfied.
Note: In practice, there may be a mismatch because (1) the user has not
completely or precisely defined his/her requirements, and/or (2) the
implementer's "declaration of conformity" might not be true, i.e.,
the implementation does not satisfy all the requirements of the standards. |
|
|
Implementers: For implementers, you will
want to declare that your implementation conforms to the requirements of the
standard -- this is known as a "declaration of conformity".
For example, a declaration of conformity might be: "The Foobar System, version
12.34, conforms to ISO/IEC 20944-5/P/MDR and strictly conforms to ISO/IEC
20944-3/B/ECMAScript/A as an API implementation", which means that
implementer declares that the system (Foobar System version 12.34) satisfies
the requirements of ISO/IEC 20944-5/P/MDR for access to 11179-3 registries
and the system also satisfies, in the role of "API implementation",
the requirements of ISO/IEC 20944-3/B/ECMAScript (the ECMAScript API binding). |
ISO/IEC 20944 Family of
Standards: Listing of Parts
|
||||||||||||||||
|
||||||||||||||||
|
||||||||||||||||
|
||||||||||||||||
|
||||||||||||||||