42
Use of data or products does not necessarily imply agreement with or endorsement of the purpose behind the gathering of such data.
” Based on the requirement in the implementation plan, it can be expected that GEOSS access control will
primarily be for authentication of users. However,the use of OGC web services within GEOSS implies that OGC GeoRM formerly GeoDRM will play a key role in GEOSS access control as it develops.
9.2.4.3.4 Development Policies
The GEOSS Architecture Implementation Pilot AIP develops and deploys new process and infrastructure components for the GEOSS Common Infrastructure and the broader GEOSS architecture. AIP is a core
task GEO Task AR-09-01b of the GEO Architecture and Data Committee. Results of the AIP are transitioned to GEO Task AR-09-01a and the GEOSS Common Infrastructure GCI. The OGC coordinates
the AIP. Progress of AIP development is listed at http:www.ogcnetwork.netAIpilot
9.2.4.4 Implementation Architecture
Services can be classified into client, business process and access tiers. Client tier services provide the user interface of the system; the services include the GEO web site, GEOSS Web Portal, various community
portals and client applications. The business process tier provides the computational and management functionality of the system; the services include the GEOSS registries, clearinghouse, alert servers,
processing servers, portrayal servers, workflow management servers and other services. The access tier offers various data acquisition and dissemination services; for example GEONETCast, product access
services, sensor web services, model access services and others. The following figure depicts these tiers.
Figure 3 GEOSS Tiers
Collectively all these services form the GEOSS Common Infrastructure GCI. Within the GCI, the web portal, registry and clearinghouse are the principal components for resource discovery. The web portal is the
