Navigation¶

• Main Page
  

• Random Page
• Create a new Page
• All Pages
• Categories
  

• Administration
• File Management
  

• Login/Logout
• Language Selection
• Your Profile
• Create Account
  

Quick Search
»
Advanced Search »

WaterML - Next Versions Planning and Research

Goals:

• Move essential information from attributes to elements
• restructure to be focused on series information
• document sensors and observations relationships and terminology
  

• Note on: Exposing full ODM content in Web Services
  

WaterOneFlow method Renaming ¶

Method v1	method v 1.1/2
GetSites	GetSitesObject
GetSitesXML	GetSitesString
GetValues	GetValuesString
GetVaraibleInfo	GetVariableInfoString
GetSiteInfo	GetSiteInfoString
	GetCapabilities	added

Possible Candidates

Methods	GetMethodsObject	GetMethodsString
Sources	GetSourcesObject	GetSourcesString
Vocabularies	GetVocabulariesObject	GetVocabulariesString ||

Changes ¶

To avoid breaking present applications, an additional web service endpoint that returns the 1.1 schema will be created.

Remove any dependence on ID's and use codes, instead. Note: There are no "codes" for many items of datavalue metadata. We make the codes from the ID's. This might be confusing.

Basic ¶

• Change attribute types to be consistent (done)
  • to token for *Code (no returns, tabs, no runs of more than one space)
  • to normalizedString for others (no returns, tabs)
• Add PropertyType, and use instead of note. Extensible, OGC like. (done)
  • siteInfo/siteProperty
  • variable/variableProperty
• value/@qualifiers
  • multiple qualifiers. Make a space delimited set of tokens MNTOKENS
• values(TsValuesSingleVariableType)
  • attribute value/@count
    • Make explicitly optional
    • add annotation to flag attribute as deprecriated
• siteInfo
  • add <siteType>
• variable and series
  • add speciation (done)
    

Minor Breaking ¶

• Expendable Enumerations (done)
  • Basically, a list of terms, plus the ability to add any string. .Net implements as string.
    

Breaking code changes, but not logic changes ¶

• Naming consistency. Standardized CaSe applied. (done)
• <values>(TsValuesSingleVariableType)
  • Move <variable> and <units> inside of <values>
• <timeSeriesResponse>
  • remove <variable>. Moved into <values> Element
  • Make <values> repeatable. USGS Request: There can be multiple instruments for the same observed property.
• <value> (ValueSingleVariable)
  • Use Codes, instead of ID's
    • @methodID to @methodCode
    • @sourceID to @sourceCode
    • @sampleID to @sampleCode
  • Add @qualityControlLevelCode
    

Could require recoding ¶

{not to be done

• <value>
  • value/@datetime as an element <datetime>
    • make it possible to be a DateTime, Year-Month-Day, Month-Day, Year
      • Code needs to be able to handle a variety of date formats, properly.
      • USGS request: They do not want to send out date times.
  • nilable <value>
    • Code needs to handle null values.