1996 - Jay K. Trautman
1997 - Jonathan Sweedler
1998 - Robert T. Kennedy
1999 - David E. Clemmer
2000 - Kimberly A. Prather
2001 - Sylvia Daunert
2002 - (no award given)

• 2003 - Stephan J. Stranick
2004 - David C. Muddiman
2005 - Jason B. Shear
2006 - Neil Kelleher
2007 - Garth J. Simpson
2008 - Laurie E. Locascio
2009 - John R. Engen

ChAMP is designed to be flexible - the parts can used and reused in many different ways by developers.  That is a good thing because it allows development to be defined by the application area.  However, developers may have a had time knowing where to start, so what follows is a set of best practices (and guidelines) for implementation of ChAMP or any similar project.

Best Practices

  • Look at how ChAMP is organized.  Think about your project in a similar way.
  • Define the scope of your application. Articulate specifically what areas it will not cover.
  • After defining metadata needed for your application evaluate which items can be represented by ontologies that already exist (not just CAO)
  • Wherever possible, make the name singular.  This may seem strange relative to common usage but makes better sense when multiple terms get separated in, for instance, RDF
  • Do not include numeric digits or special characters in metadata names
  • Use camel case (e.g. camelCase) for metadata names that would logically have spaces
  • For each metadata item
    • define its data type (use of the XML data types is recommended)
    • decide whether it should be represented by a controlled vocabulary, enum list, or set of terms
    • determine if the metadata item should occur multiple times or only once for the thing it is describing
  • For those metadata that should be controlled vocabulary based, use published vocabularies from national organizations in the domain OR if none exists consider working with a discipline group to create and publish an open vocabulary
  • In cases where a large amount of metadata is needed, consider separating the items into categories to help manage them and think at a higher level about the types of metadata that are important to project.  This makes it easier to see gaps in metadata coverage.


  •  Look at the examples on this website.  They show concrete implementations of ChAMP in both XML and JSON-LD

The third example metadata standard, in JSON-LD format, is not about an analytical method at all.  Standard reference materials are vital resources in chemical analysis to show accuracy of new and revised analytical methods and verify the accuracy of chemical analysis over time.  Agencies that produce standard methods perform rigorous chemical analysis (using two or more analytical techniques) to report certified values for analytes.  Thus, ChAMP can be used to capture metadata about the material itself and also the methods of analysis used to determine analytes in the material.

[Other links: ChAMP JSON-LD ContextChAMP Journal Article JSON-LD ExampleChAMP Standard Method JSON-LD Example]

JSON-LD Context

refmaterial context

Example File - NIST SRM 3668

refmaterial jsonld

In a number of instances a new method is developed from an existing one.  In these situations it is sometimes difficult to appreciate why a method is better/different especially when it is a smaller change.  This category of metadata was developed in order to capture more detail about a method(s) from the perspective of the chemistry or processing of samples, i.e. the use of different material, glassware or small components of an analytical system.  For instance, the addition of a new chemical to a reagent may add stability that improves the reliability of a method, or the use of a different analytical column affords a faster or lower interference detection. If you have a better name for this category than materials send your suggestion to This email address is being protected from spambots. You need JavaScript enabled to view it..

  • chemical: a synthesized or purchased amount of a chemical substance that is an important part of the analysis (string) [04-29-15]
  • solution: a prescribed solution that is part of the processing or reaction with the analyte in an analysis (string) [04-29-15]
  • glassware: containers, utensils, and apparati that are made of glass and are important in the chemical analysis process (string) [04-29-15]
  • component: a general category for other pieces/parts that are used specifically in a procedure, e.g. analytical column (string) [04-29-15]

For a second example of the use of ChAMP in creation of a standard (in JSON-LD format), we chose standard methods for obvious reasons. Standard methods of chemical analysis are published by many entities and for many application areas and while you can find many of these methods on the Internet searching for the most sensitive, or the one that best fits your application need is not always easy.  Extraction and annotation of metadata using ChAMP, as outlined below, is a great way to allow scientists to find what they need fast.

[Other links: ChAMP JSON-LD ContextChAMP Journal Article JSON-LD ExampleChAMP Reference Material JSON-LD Example]

JSON-LD Context

stdmethod context

Example File - EPA Method 7196A

stdmethod jsonld