To briefly summarize the relationship between web services and schemas: web services are used by the National Geothermal Data System project to deploy data that has been mapped to an interchange format structured by a schema provided by NGDS content models (for more information about NGDS content models, see the NGDS Content Model Tutorial).

As indicated above, users will conform to different naming conventions depending on the schema to which the data they are deploying as a web service is mapped; the schema to which the data is mapped depends on the kind of data being deployed. For example, data describing a water chemistry analysis would be mapped to an AqueousChemistry schema; when deployed, AqueousChemistry naming conventions would be used.

AASG Geothermal Data naming conventions are enumerated by schema in Table 1; see below for a description of each field in the table:

Table 1: AASG Geothermal Data naming conventions, listed by schema; entries highlighted in red represent schemas that have not yet been deployed; entries highlighted in gray represent schemas that are deprecated but remain in use; a pair of asterisks (**) indicates a pair of "wildcard" characters that should be replaced with the appropriate state abbreviation (such as AZ for Arizona)

The fields in Table 1 are as follows:

• Schema: The NGDS schema used to structure the data deployed by the user
• Current Version: The most up-to-date version of the NGDS schema listed in the Schema column; multiple versions of a given schema indicate that a transition to a newer version of that schema is in progress
• Service Name: Conventions for NGDS Service Names; here, a pair of asterisks (**) indicates a pair of "wildcard" characters that should be replaced with the appropriate state abbrevation. For example:
  • An Arizona web service structured by the RockChemistry schema would use the Service Name AZRockChemistry
  • A California web service structured by ThermalSpring schema would use the Service Name CAThermalSprings
• Layer Name: Conventions for NGDS Layer Names. For example:
  • A layer containing data describing water quality in a web service structured by the AqueousChemistry schema would be called WaterQuality
  • A layer containing data describing a rock isotope analysis in a web service structured using the RockChemistry schema would be called IsotopeSeries

Note that these naming conventions should be adhered to exactly with regard to capitalization, spacing, punctuation, plurality, and state abbreviation.

For a list of hyperlinks that dereference to representations of the schemas described in Table 1, see Table 3.

To continue this tutorial, click the links below.