[ESIP-AQ] Fw: Update: Clarification on GEOSS Registration

[McCabe.David at epamail.epa.gov]

ESIP AQ, 

>From Doug Nebert, a decision tree explaining what gets registered where in 
the GCI.  Perhaps this is clear to many or all of you, but I found this 
very helpful.

Have a great weekend!

David

David McCabe, PhD
AAAS Science & Technology Policy Fellow
US EPA, Office of Research and Development (8104R)
1200 Pennsylvania Ave. NW
Washington, DC 20460
202 564 0016
----- Forwarded by David McCabe/DC/USEPA/US on 12/12/2008 01:05 PM -----

From:
Doug Nebert <ddnebert at usgs.gov>
To:
"GEO-ADM at noaa.gov" <GEO-ADM at noaa.gov>
Date:
12/10/2008 02:19 PM
Subject:
Update: Clarification on GEOSS Registration




Here is an updated decision tree to help in registration. This will be
updated and turned into a "wizard" to help users on the CSR registration
site.

Follow the items and see which applies to your project's area of
coverage and interest. The use of "Resource" is meant to represent the
item that you wish to offer to GEOSS:

0. Resource is already described in metadata in a catalogue registered
with GEOSS. Search the GEOSS Clearinghouse through a GEO Web Portal to
see if the resource can be located. GEOSS Clearinghouse instances are
supposed to index all services (including catalogues) registered in the
Component and Service Registry (CSR). If not found, you may wish to
search the registry directly at geossregistries.info. If the catalogued
resource is still not discoverable, then contact the operators of your
catalogue and the CSR regarding the status of the catalog's
participation in GEOSS Registries and Clearinghouse. If you find your
resource in the GEOSS Registries or Clearinghouse, then you are done. If
your resource is not described in a GEOSS registered catalogue, then
continue.

1. Resource is a data set that is available only by file download.
Register it as a "Data set or Database" Component with the file download
as the URL. Done.

2. Resource is a data access system that provides access to one or more
data sets. Register is as an "Exchange and Dissemination System"
Component. In the description, include words to describe the data
contents provided by this system. If so, continue to Step 6

3. Resource is of types: Software, initiative, modeling or data
processing center, training material, web site, or document such as an
online scientific report or publication. If these items are not already
described in a GEOSS-listed catalogue, register each of these resources
as a Component, select the correct type(s), and provide the URL to the
access point described by the metadata. Done.

4. Resource is Information feed/RSS/alert system, or Computational
model. Register these types as Components and, if an API or associated
interface standards exist, continue to Step 6, otherwise, Done.

5. Resource is an Observing System or Sensor Network. Register this as a
Component. In the description, include words to describe the observation
types managed by by this system.

6. Where one or more standard, software-accessible service interfaces
exist that are described by a GEOSS registered standard or "special
arrangement" (ad hoc or community specifications) then register them as
service instances associated with the Component. You should also
associate other standards with the service interface entry, as
appropriate (e.g. metadata, format, data schema, etc) to help developers
understand the context of the offer. If a practice is not listed as a
standard or "special arrangement" you can nominate it as part of the
registration process. Do not create a Service entry for a URL that
references a file or directory unless it is explicitly associated with a
specific standard protocol or practice (e.g. WebDav, OpenDAP,
Web-accessible folder).


Doug.
-- 
Douglas D. Nebert
Senior Advisor for Geospatial Technology, System-of-Systems Architect
FGDC Secretariat     Phone: +1 703 648 4151     Fax: +1 703 648-5755




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rtpnet.org/pipermail/esip-aqcluster/attachments/20081212/d20df049/attachment-0001.htm>