"Seegrid will be due for a migration to confluence on the 1st of August. Any update on or after the 1st of August will NOT be migrated"

ADX 2 Procedures


Related pages

Schema documents

  • XmmlSVN:trunk/ADX/2.0/adxProcedures.xsd
  • XmmlSVN:trunk/enumerations/LUTsampling.xsd

Example Instances

Analyte procedure




Each AnalyteProcedure binds an analytical procedure to an analyte, and provides some procedure-specific parameters. These are often useful in assessing the reliability or quality of the result of an analysis.

The AnalyteProcedure has the following properties:

  1. a handle in the form of an id attribute, which may be used to construct a URI which uniquely identifies this analysis for linking in an XML/web context - see LabelsAndHandles
  2. a name which holds the label used by the provider to identify the analyte procedure. - see LabelsAndHandles. The value of the name is often constructed by concatenating the analyte symbol and the procedure code.
  3. the analyte species such as "Au" or "Al2O3", selected from the enumeration in XmmlCVS:XMML/LUTgeochemistry.xsd
  4. a code used by the provider to identify the procedure
  5. the method is a more generic indicator of the analysis procedure such as "AAS", "DCP", "calculated", selected from the enumeration in XmmlSVN:trunk/enumerations/LUTgeochemistry.xsd
  6. if the value of the method is "calculated", then the algorithm or expression is described as the calculation
  7. otherwise, the parameters of the procedure are described as follows:
    1. massAnalysed - Analytical sample weight - with units of measure
    2. aliquotVolume - laboratory extracted aliquot volume for the specimen in requiring analysis - with units of measure
    3. dilutionFactor (default="1.0") - The procedure may involve diluting the specimen by a certain factor in order to bring the result within the detection range of the instrument. A standard dilution may be used as part of some procedures. However, dilution usually happens on a per-specimen/per-analyte basis, so is more often recorded as part of the Analysis element. Note, however, that the dilution factor is always provided for information only, and the numeric value of the result always represents the "true" value, with the correction due to dilution already applied.
    4. lowerDetectionLimit, upperDetectionLimit, secondUpperDetectionLimit - detection limits for the given method for this analyte; some procedures may have a secondary upper detection limit higher than the first, for the given method for this analyte. Results may be reported with values between the primary and secondary upper detection limits that have reduced accuracy.
    5. primaryDigestion - Primary digestion procedure for this analyte/method
    6. secondaryExtraction - Secondary leach, organic extraction or concentration procedure for this analyte/method
    7. deliveryMethod - Specialized method of delivery to analytical equipment: e.g. Hydride.
  8. operator - The party responsible for performing the procedure and/ or specific laboratory location
  9. comment

Analyte suite




An AnalyteSuite is a convenient packaging of a set of AnalyteProcedures.

The AnalyteSuite is composed as follows:

  1. a handle in the form of an id attribute, which may be used to construct a URI which uniquely identifies this analysis for linking in an XML/web context - see LabelsAndHandles
  2. a name which holds the label used by the provider to identify the analyte suite. - see LabelsAndHandles.
  3. the procedureCount giving the number of procedures in this suite
  4. a set of procedureMember - following the usual GML "property" pattern, the procedureMember element may either contain a complete description of an AnalyteProcedure or carry a (href) pointer to an AnalyteProcedure described fully elsewhere. This supports maximum normalisation when appropriate, but allows them to be described in one place if prefered.
  5. comment

Issues and change requests

Readers are invited to add issues to this table - select [Edit] from the menu above. It is not mandatory to enter a solution, but change requests are more likely to be implemented if a concrete solution is proposed.

# By Component(s) Description of issue Proposed solution Resolution
1 ALS Chemex Analytes from LUTgeochemistry List of analytes needs augmentation to capture the requirements of ALS-C, in particular: radioactive species, oxides, some other substances as detailed in spreadsheet provided    
2 ALS Chemex AnalyteProcedure Digestion acid/flux/solvent type should be from controlled list    
3 ALS Chemex AnalyteProcedure More information is required concerning the digestion (fusion? dissolution?) component of the analytical procedure, specifically temperature, acid/flux/solvent type, elapsed time    
4 ALS Chemex AnalyteProcedure Add a slot for describing the confidence limits for a result from this procedure (may be a formula based on result, mass analysed, etc)    
5 ALS Chemex AnalyteProcedure Clarify that the "calculated" analyte procedure allows a description of how the calculation is constructed    
5 CSIRO AnalyteProcedure Re-examine analyte/procedure combination, with a view to describing an analytical procedure separately from the specific analyte, and just bringing these together within the description of a single analysis (measurement).    
Topic revision: r30 - 15 Oct 2010, UnknownUser

Current license: All material on this collaboration platform is licensed under a Creative Commons Attribution 3.0 Australia Licence (CC BY 3.0).