Common ways in which the dataset may be obtained or received, and related ins tructions and fee information Technical means and media by which a dataset is obtained from the distributor Information about the distributor Information about the distributor of and options for obtaining the dataset *** count (distributionFormat + distributorFormat) > 0 Description of the form of the data to be distributed *** count (distributionFormat + distributorFormat) > 0 Identification of, and means of communication with, person(s) and organisations associated with the dataset *** count of (individualName + organisationName + positionName) > 0 Location of the responsible individual or organisation Information about online sources from which the dataset, specification, or comm unity profile name and extended metadata elements can be obtained. Telephone numbers for contacting the responsible individual or organisation Information required enabling contact with the responsible person and/or organisation Standardized resource reference Vertical domain of dataset Time period covered by the content of the dataset Geographic area of the entire dataset referenced to WGS 84 Information about spatial, vertical, and temporal extent *** count(description + geographicElement + temporalElement + verticalElement) >0 High-level geospatial data thematic classification to assist in the grouping a nd search of available geospatial datasets Keywords, their type and reference source Encapsulates the dataset aggregation information Basic information about data Restrictions on the access and use of a dataset or metadata Restrictions and legal prerequisites for accessing and using the dataset. *** otherConstraints: documented if accessConstraints or useConstraints = "otherRestrictions" /> Quantitative_conformance_measure from Quality Procedures. Renamed to remove implied use limitation OCL -- result is type specified by valueDomain result.tupleType = valueDomain *** "levelDescription" is mandatory if "level" notEqual 'dataset' or 'series' *** "report" or "lineage" role is mandatory if scope.DQ_Scope.level = 'dataset' This schema was directly generated from the ISO TC 211 Harmonized UML model via Version 0.10 of the Rational Rose Script 'XMLout4XMLSchema.ebs' and via 'UMLSchema_to_XMLSchema.xslt' for the DGIWG contribution to the ISO 19139 Project Team at DateTime 05-26-2004 18:19:52 Information about the metadata *** Conditional statements: *** language: documented if not defined by the encoding standard *** characterSet: documented if ISO 10646-1 not used and not defined by the encoding standard