地球科学数据长期保存祥解.ppt

Text in box Testing is one important practical means that contributes to assessing to correctness of a service implementation. As usual, services under test are required to undergo some specific verification and validation procedures. However, the complexity of geo services establishes additional problems; one of them, which we address in this work, is related to dependency issues. Such dependencies often already exist within one specification against which a service is to be assessed. Moreover, specifications themselves often refer to other specifications – either because some pre-existing specifications are used, as in the case of relying on standards, or because the specification on hand is itself modularized into different documents between which, consequently, logical relationships exist. Further problems include interface conformance evaluation, test maturity evaluation, global validity evaluation, and the question of how to craft specifications in a way which eases rigid testing. One use case for conformance testing where this becomes particularly apparent is the Web Coverage Service (WCS) 2.0 Interface Standard issued by the Open Geo?spatial Consortium (OGC). The WCS Core relies on the GML Application Schema for Coverages which contains standardized attribute descriptions; the Core itself, which defines service functionalities mandatory for every implementation claiming to conform with the WCS standard, consists of 42 requirements which are often logically connected. Extension standards add further data structures, functionality, or usage requirements. Currently, three extensions have been adopted as standards and about ten more are in the pipeline of the standards working group. Core and extension documents internally contain requirements classes as modularization units; WCS choose to have, whenever possible, only one requirements class in the Core for reasons of simplicity. Application Profiles, finally, bundle the Core plus a custom set of extensions into