cultural Adaptability

1
ISO/IEC 11179 Part 6 Registration Processes and
Levels of Compliance
Open Forum onMetadata Registries Santa Fe, NM
Phong NgoSAICJanuary 17, 2000
SDC-0002-021-JE-2024
2
Registration Processes and Levels of Compliance
A Quick Overview
SDC-0002-021-JE-2024
3
So you want to build a Metadata Registry ?
4
WHY Do You Want a Registry ?

• Organize
• Standardize
• SHARE

5
WHY in Standards Prose

• "To give concrete guidance on the formulation and
  maintenance of discrete data element descriptions
  and semantic content ... for the open exchange of
  data throughout the international communities by
  global electronic information interchanges and
  for easy acquisition of desired data. ISO/IEC
  11179-1
• ISO/IEC 11179 emphasizes, among other features,
  the use of nonintelligent identifiers (RE
  ISO/IEC 11179-5 and 11179-6) for data elements
  specified for sharing. To each identifier
  multiple name-context pairs are allowed. This
  strategy not only allows each country, nation,
  organization to choose a name or names for a data
  element, but also provides a vehicle for
  cross-cultural, cross-organizational information
  interchange.

6
WHAT to Register and Share ?

• Metadata of Data ElementsISO/IEC 11179-6
  defines
• the type of information that shall be specified,
• the conditions that shall be met, and
• the procedure(s) that shall be followed for the
  registration of shareable Data Elements.
• Metadata of Other Objects The procedure
  prescribed herein, however, may be extended to
  register other shared objects, such as object
  classes, data element concepts, and permissible
  data element values.

7
So you want to SHARE ?
8
HOW to ShareRules of Engagement

• Nonexclusive registration Every organization
  may be a Registration Authority.
• Data sharing registration Data may be shared
  intra- or inter-organizationally.
• Economically enforced registration Utility
  determines longevity.
• Flexible registration Metadata may be
  registered at different levels of quality.

9
Are You Ready to Go Global ?
Registration Authority Identifier (RAI)
Data Identifier (DI)
Version Identifier (VI)
Same as ISO 6523
International Code Desiginator (ICD)
Organization Identifier
Organization Part Identifier (OPI)
OPI Source (OPIS)
Optional
International Registration Data Identifier (IRDI)
is an internationally unique Identifier.
10
Identify YourselvesLocally and Globally

• Each data element shall be unique within a
  registration authority.
• The combination of registration authority, data
  element identifier and version, shall make an
  internationally unique identification for a data
  element.
• To be assigned an identifier, a data element
  shall satisfy all conditions specified in all
  parts of the standard.

11
Are You Ready to Comply ?
Standardized
Certified
Recorded
Incomplete
Registration Status
12
How Serious Are You ?

• Incomplete Data Element (DE) does not contain
  all Mandatory Attribute values.
• Recorded DEs contents do not meet the quality
  requirements specified in other parts ofISO/IEC
  11179.
• Certified The recorded DE has met the quality
  requirements specified in this and other parts of
  ISO/IEC 11179.
• Standardized (within a registry) The certified
  DE that is established by the Registration
  Authority as a data element preferred for use in
  data interchange and in new or updated
  applications.
• Retired A recorded, certified, or standardized
  data element is no longer used after having been
  marked as "phased out" for a period of time as
  prescribed by the appropriate RA.

13
So You STILL want to become a Registration
Authority?
14
Do You Know the Players?

• Submitting Organization (SO)
• Responsible Organization (RO)
• Registration Authority (RA)
• User Community

15
Roles and Responsibilities
Process applications Assign IRDI values Maintain
a DE Registry Assign appropriate Registration
Status
Submit DE for registration Provide supplemental
info

• SpecifyDataElement(DE)

• Arbitrate
• Semantics
• Name
• Domain

Reconcile Clarify
Advise Notify
Notify SOs of its decisions
RegistrationAuthority
Submitting Organization
ResponsibleOrganization
SDC-0002-021-JE-2024
16
Responsibilities ofSubmitting Organizations (SO)

• Provide the information specified in Annex A in
  the format required by the RA.
• Provide any additional information that may
  reasonably be required by the RA to perform its
  responsibilities.
• Ensure that when a data element has been
  registered, specification of the attribute values
  of the data element are not changed without first
  advising the RA.

17
Responsibilities ofResponsible Organizations (RO)
Specifically, the responsibilities of an RAare

• At the RA's request, advise on the semantics,
  name, and permissible value of data elements
  submitted for registration.
• Notify the RA of any amendments to the data
  elements assigned to the RO.
• Decide, in case of confusion and/or conflict, on
  the attribute values of the assigned data
  elements.

18
Responsibilities of Registration Authorities (RA)

• Receive and process applications for the
  registration of data elements, assign IRDI
  values, and maintain a Data Element Register in
  accordance with the following provisions.
• Consult the appropriate ROs when requests affect
  the mandatory attributes of the data elements
  being registered.
• Handle all aspects of the registration process in
  accordance with good business practice and, in
  particular, take all reasonable precautions to
  safeguard the Register.

19
Responsibilities of Registration Authorities
(RA)(continued)

• Receive applications for registering data
  elements from its SOs.
• Review and facilitate the progress of
  applications through the registration cycle.
• Assign appropriate Registration Status.
• Notify SOs of their decisions according tothe
  requirements of this standard.

20
Your First Assignment as a Registration Authority

• Secure an RA Identifier (RAI).
• Prescribe, amend, and interpret the procedures.
• Determine any additional conditions specifically
  required by its domain of registration.
• Specify the format for each attribute listed in
  Annex A of ISO/IEC 11179-6 and for any additional
  attributes.
• Determine the format and media in which
  applications shall be submitted.
• Are you ready to start?Please let us know after
  a few months.

21
Beyond Registration of Data Elements

• Other Metadata Components
• Associated Compliance Considerations

SDC-0002-021-JE-2024
22
Revised Part 3 of ISO/IEC 11179
As of October 1999
23
Areas of Compliance

• There are no requirements that all components of
  the model be present for a registry to be
  compliant with the model.
• There is a practical need for registering only
  those components of interest.
• Except for those situations constrained by the
  cardinalities of the metamodel, there is no
  required sequence in the registration of the
  components.

24
Potential Areas of Compliance (Proposed)

• Principal Areas
• Data Elements
• Data Element Concepts
• Conceptual and Value Domains
• Other Areas that may be registered as Components
• Object Class
• Property
• Representation

25
Levels of Compliance

• A component is deemed to reach a certain
  Registration Status when its own attributes and
  those of the Required Associated Components meet
  the minimal criteria for that Registration
  Status.
• The same set of Registration Statuses and
  associated criteria that are applicable for Data
  Elements shall be applicable for other
  Components Incomplete, Recorded, Certified,
  Standardized and Retired.

26
Issues/Concerns

• Administrative Topics related to Metadata
  Registration

27
Several Months Later...
So, You Are Still Alive!
28
Discussion Points

• There are not enough attributes to satisfy the
  submitters. (See B.1)
• How can we keep up with these versions ? (See
  B.2)
• We really want to share data with THAT
  organization. But it seems that neither of us
  wants to use the other persons specification of
  data (See B.3)
• Wouldnt it be nice to have only one RA for the
  entire world ? (See C.2) The set of statuses
  provided by the standard seem inadequate. (See
  C.7)

29
There are not enough attributes to satisfy the
submitters (B.1)

• B.1.1 Technical Attributes Depending on the
  classes of object(s) for which an RA is
  responsible, the list of these attributes
  required for a particular RA may be expanded to
  accommodate its needs and those of its members.
  For example
• An engineering-oriented RA may capture and
  maintain additional attributes, such as unit of
  measure, formula, method/procedure used, etc.
• An information systems data modeler may add
  attributes, such as usage, steward, owner,
  quality indicator, etc.
• B.1.2 Administrative Attributes Additional
  administrative attributes, suggested for RA in
  Annex E of the ISO/IEC Directives, include, but
  are not limited to
• Request for update
• Release authorization
• Justification for registration
• Reasons for action taken
• Applicable technical and/or procedure standards.
• RAs may specify other attributes as needed to
  maintain their registers.

30
We really want to share data with THAT
organization. But it seems that neither of us
wants to use the other persons specification of
data. (B.3)

• The number of potential data elements to be
  registered in the framework of ISO/IEC 11179 is
  unlimited and diverse. So is the number of
  potential RAs.
• It is envisioned that organizations wishing to
  share information among themselves may want to
  establish an RA for that purpose. An RA and its
  members may subsequently want to share subsets of
  data elements with other RAs and their members.
  If two or more RAs believe that they should
  standardize certain data elements across their
  areas of interest, they may accomplish this
  requirement in a couple of ways Either they
  will negotiate to complement one another's
  registers with their already standardized data
  elements, or they will establish another RA to
  register data elements that they want to share,
  but are not available or agreed upon. Under the
  latter circumstance, the current RAs will become
  SOs and the newly founded RA will become the RA
  for shareable data elements. Conceptually, this
  hierarchy may be repeated.
• This part of ISO/IEC 11179 allows as much
  flexibility as needed for data sharing purposes.
  The viability of individual RAs depends on other
  economic and practical benefits to their
  subscribing communities.

31
C.1 Should a data element contain more than the
five (5) Registration Statuses currently
specified in 6.3?

• The five (5) Registration Statuses specified in
  this part of ISO/IEC 11179 are intended to
  provide criteria for assigning defined levels of
  compliance of each Data Element submitted for
  registration.
• Some organizations have adopted the practice of
  combining the above statuses with statuses of
  administrative nature, e.g., Received, Processed,
  Being Promoted. Attribute Administrative Status,
  as specified in this part of ISO/IEC 11179, shall
  be used for this administrative purpose.

32
C.2 Why don't we have a single international RA
for all data elements?

• It would be conceptually more attractive to have
  a single RA for all data elements. Redundancy
  would be minimized, and data sharing would be
  easier thanks to a single point of reference.
• Actually, this part of ISO/IEC 11179 has evolved
  from a single global RA to a predetermined
  hierarchy similar to that prescribed in the
  previous Annex H of JTC 1 Directives. Although
  these approaches may be suitable for the
  registration of a finite number of objects, e.g.,
  Registration of Graphical Items (RE ISO/IEC
  9973), they are, however, neither viable nor
  practical for the registration of data elements.
  
• There will be a very large number of data
  elements to be registered, and no single
  organization will have resources and expertise to
  review and register data elements of varied
  subject matters.

33
C.5 How can an RA obtain an RAI?

• In general, virtually every organization has
  already been assigned an organization code that
  is internationally unique therefore, by default,
  they already have an RAI
• Obtain an ICD to use as RAI directly from the
  British Standards Institute OR
• Institutions like Dun Bradstreet or SWIFT have
  been assigned International Code Designators
  (ICD) through the maintenance agency of ISO/IEC
  6523
• Subsequently, the above institutions assign
  Organization Identifiers (RE Identification of
  Organization) to their subscribing members
• Their members, subsequently, assign Organization
  Part Identifiers (RE Identification of
  Organization Part) to their internal
  organizational units

34
C.7 There is some concern with making
Registration Status and Administrative Status two
separate pieces of information.

• Registration Status (6.3) is reserved for use as
  a quality indicator for the metadata of a data
  element being maintained in a data register.
• Administrative Status (6.4) is a designation of
  the position in the processing life-cycle of an
  RA for handling registration requests. The
  values of this attribute are assigned by an RA
  with the permissible values, such as Received,
  Draft, Rejected, Submitted for Certification,
  etc., to facilitate the management of its
  Register. It is the responsibility of the RA to
  refine, publish, and implement this
  administrative feature.

35
Other Discussion Points

• What if we just want to register only Data Value
  Domains (code sets)?
• What if we just want to deal with classification
  of only Data Concepts?
• Several organizations are implementing ISO/IEC
  11179. How can we interchange metadata (and
  data) among registries?

36
But We Are NOT Alone

• Reference Implementation
• U.S. EPAs Environmental Data Registry (EDR)
  www.epa.gov/edr/
• Australian Institute of Health and Welfares
  National Health Information Knowledgebase (NHIK)
  www.aihw.gov.au/services/health/nhik.html
• In Progress
• HCFA Registry
• Census Bureau Data Registry
• DoD Health Affairs
• DoD Environmental Security
• DOT
• Metadata Registry Coalition
• Contact Glenn Sperle (GSperle_at_hcfa.gov)