Difference between revisions of "Talk:2010-03-19: Demystifying the GEOSS Infrastructure - Virtual Workshop 2"
(What's the difference between the GEOSS Clearinghouse and GEOSS Registries? -- ~~~~) |
|||
| Line 3: | Line 3: | ||
The GEOSS Component and Service Registry provides the key “yellow pages” feature of GEOSS, allowing GEO Members and Participating Organizations to identify and describe GEOSS Components and | The GEOSS Component and Service Registry provides the key “yellow pages” feature of GEOSS, allowing GEO Members and Participating Organizations to identify and describe GEOSS Components and | ||
Services associated with them. | Services associated with them. | ||
| + | |||
| + | The GEOSS Clearinghouse provides search across all component and service descriptions that are in the Component and Service Registry. A small set of searchable fields is extracted from the descriptions and are made available through a standard query interface to support rapid and consistent search across multiple community catalogues. Registered catalog services are, in turn, queried and their contents are either harvested on a recurrent basis or are searched in parallel. Applications may also query the Clearinghouse to discover and access services through links stored in the service descriptions (metadata). | ||
Revision as of 07:47, March 18, 2010
What's the difference between the GEOSS Clearinghouse and GEOSS Registries? -- Erinmr 09:40, 18 March 2010 (EDT)
The GEOSS Component and Service Registry provides the key “yellow pages” feature of GEOSS, allowing GEO Members and Participating Organizations to identify and describe GEOSS Components and Services associated with them.
The GEOSS Clearinghouse provides search across all component and service descriptions that are in the Component and Service Registry. A small set of searchable fields is extracted from the descriptions and are made available through a standard query interface to support rapid and consistent search across multiple community catalogues. Registered catalog services are, in turn, queried and their contents are either harvested on a recurrent basis or are searched in parallel. Applications may also query the Clearinghouse to discover and access services through links stored in the service descriptions (metadata).
