This section defines the sourceIds that are valid for passing to getFields and setFields. This This list is complete, but please note that your greenID account may be configured with a subset of these sources; a list of valid data sources for your greenID account is always available via a call to getSources, or by inspecting thesourceList element returned by any call to the API. If If a source does not appear in the sourceList, then you cannot use it.
...
For every data source, greenID maintains a version number, which is returned in each source element in the sourceList element, returned from every call to the API. The The version number is used to track changes to the field structure for the data source. If If the field structure changes, for example by adding a new required field, then the version number will be incremented.
The data sources are subject to change, and the version number is the indicator that customers can use to identify that a change has occurred.
...
The version won't be changed without a good reason. Most Most often, a new version will be produced because the underlying data source has been changed. For For example, if a data source changed to require an additional field, then the field would be added and the version number incremented. These changes will, generally speaking, not be backwards compatible. If If a change is made that maintains backward compatibility, then the old version may continue to be used.
...
| Child pages (Children Display) | ||
|---|---|---|
|