sdc-0002-021-je-2027 january 18, 2000 bruce bargmeyer chair, sc 32 – data management and...
TRANSCRIPT
SDC-0002-021-JE-2027
January 18, 2000
Bruce BargmeyerChair, SC 32 – Data Management and Interchange U.S. Environmental Protection Agency Telephone: (202) [email protected] URL: http://www.nist.gov/itl/div897/staff/bargmeyer
SC 32/WG 2
Open Forum on Metadata Registries
SDC-0002-021-JE-2027
ISOISO 11179, Parts 1-611179, Parts 1-6
Part 1: Framework for the Specification and Standardization of Data Elements
Part 2: Classification for Data Elements Part 3: Basic Attributes of Data Elements Part 4: Rules and Guidelines for the
Formulation of Data Definitions Part 5: Naming and Identification Principles
for Data Elements Part 6: Registration of Data Elements
Plus New Work Items
SDC-0002-021-JE-2027
Part 4: Data DefinitionsPart 4: Data Definitions
Verification Method Code:The code that represents the process used to verify the latitude and longitude coordinates.
Mailing Address Post Office Box:The number of the post office box where mail for the addressee is delivered.
International Postal Code:The code that represents a postal zone specific to a country.
SDC-0002-021-JE-2027
Data Element ConceptData Element ConceptAfghanistan
Belgium
China
Denmark
Egypt
France
Germany
…………
Data ElementsData ElementsAFG
BEL
CHN
DNK
EGY
FRA
DEU
…………
ISO 3166English Name
ISO 31663-Numeric Code
004
056
156
208
818
250
276
…………
ISO 31663-Alpha Code
Afghanistan
Belgium
China
Denmark
Egypt
France
Germany
…………
Name:Context:Definition:Unique ID: 4572Value Domain:Maintenance Org.:Steward:Classification:Registration Authority:Others
Name:Context:Definition:Unique ID: 3820Value Domain:Maintenance Org.:Steward:Classification:Registration Authority:Others
Name:Context: Definition:Unique ID: 1047Value Domain:Maintenance Org.:Steward:Classification:Registration Authority:Others
Name: Country IdentifiersContext:Definition:Unique ID: 5769Conceptual Domain:Maintenance Org.:Steward:Classification:Registration Authority:Others
SDC-0002-021-JE-2027
Data_Element_Concept_Relationship
<<Required>> type_description
Non_enumerated_Domain
<<Required>> description
Value_Domain_Relationship
<<Required>> type_description
Enumerated_Domain
Permissible_Value
<<Required>> item<<Required>> begin_date<<Conditional>> end_date
2..n
1..*
+member_of2..n
+specifing1..*
allowed_value
Value_Meaning
<<Required>> identifier<<Optional>> description<<Required>> begin_date<<Conditional>> end_date
2..n
0..*
+contained_in2..n
+containing
0..*
permissib le_value
1..*
0..*
+represented_by
1..*
+representing0..*
permissib le_value_meaning
Conceptual_Domain
<<Optional>> administered_component_information : Administered_Component<<Optional>> dimensionality
0..*0..*
+containing
0..*
comceptual_domain_relationship
+contained_in0..*
1..*
0..*
+containing
1..*
+contained_in
0..*
value_meaning_set
Value_Domain
<<Optional>> administered_component : Administered_Component<<Optional>> name<<Required>> datatype : Datatype<<Optional>> maximum_character_quantity<<Optional>> minimum_character_quantity<<Optional>> format<<Optional>> unit_of_quantity : Unit_of_Quantity
0..*
0..1
+contained_in
0..*
value_domain_relationship
+containing
0..1 0..*
1..1
+representing0..*
+specified_by
1..1
specification
Example
<<Required>> item
Data_Element_Concept
<<Required>> administered_component : Administered_Component<<Optional>> object_class : Object_Class<<Optional>> object_class_qualifier<<Optional>> property : Property<<Optional>> property_qualifier
0..1
0..* +containing0..1
data_element_concept_relationship
+contained_in0..*
1..10..*+specifing
1..1+having
0..*
data_element_concept_conceptual_domain_relationship
Data_Element
<<Required>> administered_component : Administered_Component<<Required>> representation_class : Representation_Class<<Optional>> representation_class_qualifier
0..* 1..1
+represented_with
0..*+providing_representation_for
1..1
representation
1..*
1..*
+represented_by
1..*
+representing1..*
exemplication
0..*
1..1
+providing_representation_to
0..*
+represented_by
1..1
expression
Rule
<<Optional>> administered_component : Administered_Component<<Required>> description
Source_Data_Element
0..*
1..*
+containing
0..*
+contained_in
1..*
derivation_input
0..1
1..1
+is_input_to0..1
+resulting_from
1..1
derivation_output
1..1
0..*
+is_formula_for1..1
+used_by0..*
derivation
Proposal for Comments11179-3 RevisionDD Mann
PAGE 111179-3 METAMODELMain Model
NOTE:
This model represents the logical structure of a registry for data elements and related components that are in a "recorded" or higher registration status.
For UML v1.3 documentation see:ftp://ftp.omg.org/pub/docs/ad/99-06-08.pdf
1999-12-13
AFG
BEL
CHN
DNK
EGY
FRA
DEU
…………
004
056
156
208
818
250
276
…………
Afghanistan
Belgium
China
Denmark
Egypt
France
Germany
…………
SDC-0002-021-JE-2027
Part 5Names
IDs
Part 4Definitions
Part 2 Classifications
SDC-0002-021-JE-2027
Biological terms
New speciesNew classification
Systematic NameVernacular Name
Taxonomic Serial NumberISO
ANSIIndustryGov’t
Impacts of Data Change
SDC-0002-021-JE-2027
Chemicals
New chemical
Systematic NameSynonym
CAS NumberISO
ANSIIndustryGov’t
Impacts of Data Change
SDC-0002-021-JE-2027
Impacts of Data Change
ISO
ANSIIndustryGov’t
Country
Country changesCZ Czechoslovakia*
CZ Czech Republic**LO Slovakia**
* FIPS PUB 10-3** FIPS PUB 10-4
Change
SDC-0002-021-JE-2027
As changes in the world occur, metadatachanges will be recorded and effectively
communicated between registries.
Standard Data
Change
ISO
ANSIIndustry
Gov’t
DefenseData Dictionary
System
Catalog ofData Sources
HealthCare
FinancingAdministration
IntelligentTransportation
System
Sta
nd
ard
Dat
a
EDREDR
Health AffairsHISB
SDC-0002-021-JE-2027
Profiles of ISO/IEC 11179Profiles of ISO/IEC 11179
xx
xx
SDC-0002-021-JE-2027
Individual Parts of 11179 Profiles Extensions
ImplementationsImplementations