Geochemical Schema, based on the Database Model Schema version 1.1.1 GeochemistryData element is simply a utility container for geochemistry elements that may exist independently of (in association with) each other. It acts as a root element only. A survey is the most important element in the schema. Everything else is organised around it. In gml3, a Feature/FeatureCollection has metaDataProperty implicitly. For Survey, the metaInfo is used to substitute the abstrct metaDataProperty and CGKNMetaData is used to substitute the abstract MetaData. major change than in gml2. Only one siteMembers that holds an array of homogeneous Sites. A survey associates to many Sites by siteMembers property. restricts from gml3 FeatureArrayPropertyType By definition, at least one site must be visited at each Site_Cluster--classificationNodeList. It is not necessary for any samples to be collected at a particular site. A survey is conducted by an organisation. An organisational unit is an administrative concept. The organisational unit is defined on a scale that makes sense relative to the data being stored. A project is an administrative concept. It is impossible to define in a rigid way, because it is continuously evolving. What constitutes a project may vary from one organisation to another. It may be rigidly tied to funding, time period, or staff. The ProjectType is intended to capture enough information to allow recording of the most important information. A project is led by one or more principal investigators. A principal investigator is an individual, who is indirectly related to a survey via the ProjectType. The list of attributes is kept fairly brief, to minimise maintenance problems. Contains information on publications which use data from a survey. This type is highly denormalised, in order to avoid the great complexities of literature references. It provides enough information to allow the user to obtain a copy of the publication. A survey can collect many different types of samples. The type for a sample. A sample corresponds exactly to what is collected in the field. If material from a single source is separated in the field, then it should count as multiple samples. A sample may be broken into SubSamples after it has been removed from the collection site. After a sample has been collected, it may be split into multiple components (e.g. till samples are routinely seived into different size fractions). Each subsample is, in some way, distinct from the other subsamples. A subsample is not a split into identical parts. By definition, each sample must be connected to at least one subsample. If the subsample is identical to the sample, then it is classed as "undivided". Base type for PreparedSampleType and LaboratorySampleType. The subSampleList is restricted. This type defines the type for a subsample. A subsample may be split into two or more identical parts, all of which are submitted for analysis. This is a very useful QA/QC technique. By definition, every subsample must be connected to at least one split subsample. This type defines the type for a split subsample. Every sample that is chemically analysed, contains many analytical results. type for Analyses result Analysis needs a Analytical Method. Analysis may need a Control Reference. The type for AnalyticalSampleBundle. An AnalyticalSampleBundle consists of a group of samples which have a common analytical history. The nature of this history is specified by AnalyticalSampleBundleTypeID. Each data bundle is assigned a unique ID. for metadata property type, extends from gml3 MetaDataPropertyType This is the CGKN metadata profile. Every survey should have one, and only one, CGKNMetaData. It extends from gml3 AbstractMetaDataType. CGKN metadata is related to CGKNMetadataContactInfo. The CGKNMetadataContactInfo contains contact details as required by the CGKN metadata profile ClassificationNodeList for classified objects such as Site, Sample and SubSample. enumeration for province codes. enumeration for progress values.