The structures and some terms used in the public registry are from UML, not ISO 14817. However, in all cases the UML concepts do have a mapping to 14817 equivalents, and a 14817-compliant view could be generated from the underlying metadata in the future. The specific UML tagged values that we have chosen are from the ISO 14817 meta-attributes.

The ISO 14817 process is used wherever possible, although because of the strict non-compliance (e.g. use of ASN.1 is not mandatory), some licence is needed when interpreting the meaning of ISO 14817 roles in the context of this registry trial.

The remainder of this page presents specific guidance for the creation of UML models for submission to the Registry in relation to ISO 14817.

1. Representation of meta-attributes
2. Mandatory meta-attributes
3. Recorded and higher registry status levels
4. ISO 14817 Standard

i. Representation of meta-attributes

All ISO 14817 meta-attributes are supported. Many meta-attributes have a direct representation in the UML model. Any others should be represented by tagged values against the registered item, with name equal to the ISO 14817 meta-attribute name.

The following table defines the correspondance between UML elements and ISO 14817 data concepts for the purposes of meta-attribute specification (We have not yet created a full-scale UML Profile for ISO 14817. Anybody wishing to register ISO 14817 style data definitions should email helpdesk.tts@mottmac.com).

UML element	Use meta-attributes for ISO 14817 Data Concept
Class (default)	Object Class
Class stereotyped <<Message>>	Message
Class stereotyped <<DataFrame>>	Data Frame
Association	Association
Attribute	Data Element
Enumeration	Object Class
Package	Object class

The following table lists all the ISO 14817 meta-attributes that have direct representations or are assigned centrally and therefore should NOT be supplied as tagged values.

ISO 14817 Meta-Attribute	Comment
Data concept identifier	Assigned by registry
Data concept version	Assigned by registry
Descriptive name	Name of UML element
Definition	Annotation / "documentation" for each UML model element.
Descriptive name context	The context in UML supplied by package etc
Data concept type	Can be derived from type of UML element
Abstract	Standard UML property
Roles	Information is in a UML association end
Multiplicity	Standard UML property
Association constraints	Standard UML concepts
Aggregate	Standard UML property
Role key	Information is in a UML association end
Refernced data elements	Information is in model
Data type	Standard UML concept
Registration status	Applied centrally
Date registered	Applied centrally
Last change date	Applied centrally
Last change user	Applied centrally
Registrar organization name	Applied centrally
Registrar phone number	Applied centrally
Remarks	UML comment
Association constraints	Information in UML association / association ends.
Referenced data frames	Equivalent in UML model
Referenced object classes	Information is in model

ii. Mandatory meta-attributes

All submissions require:

• Submitter Organization Name "Definition: A reference to the authority having responsibility for submitting a data concept proposal for registration. Description: This is the organization assigned responsibility for identifying, documenting, and proposing data concepts for registration."
• Submitter Phone Number "Definition: The telephone number [country code, city code, area code, exchange number, telephone number, extension number] of the responsible submitter organization".
• Cascading meta-attributes Note that in contrast to ISO 14817, this trial registry takes the time saving approach of considering meta-attributes specified for packages to apply to all their contained elements, without requiring them to be re-specified individually for every contained element. This applies to the following attributes set by the submitter:
  
  
  • Submitter Organization Name, Submitter Phone Number, Standard.
  
  The cascading approach also applies to the following attributes applied centrally:
  
  
  • Date registered, Last change date, Last change user, Registrar organisation name, Registrar phone number, Steward organisation name, Steward phone number.
  
  The approach to "Registration status" is slightly different - the top level of the registry has one package for each ISO 14817 registration status. All registered items are housed within the appropriate package reflecting their "Registration status".

iii. Recorded and higher registry status levels

"Recorded" and higher levels require a number of mandatory attributes, as defined in ISO 14817.

Click here for more details...

iv. ISO 14817 Standard

The ISO 14817 standard is available for purchase from ISO: ISO 14817 Standard