Subject: Stateless Catalog use cases
Resent-Date: Thu, 19 Apr 2001 16:29:59 -0500 (EST)
Resent-From: servicemodel@opengis.org
Date: Thu, 19 Apr 2001 17:38:58 -0400 (EDT)
From: Jeff de La Beaujardiere <delabeau@iniki.gsfc.nasa.gov>
To: Service Model <servicemodel@opengis.org>, catalog.wg@opengis.org
CC: rob@socialchange.net.au

I took an action at today's Catalog/Service Model meeting to
write down my Use Case describing a WMS search and what I
think Rob Atkinson's is [Rob--correct me if I'm wrong].

-Jeff DLB

Stateless Catalog Use Case: Search for WMS Layers

- User types in search terms and initiates search.

- Catalog Client issues query and asks for BRIEF response.

- BRIEF result set includes at least these 5 items:
  - ID of each matching Layer (unique identifier in Catalog instance)
  - Title of matching Layers (for display to human)
  - Name of Layers (unique identifier in WMS)
  - Title of WMS providing each Layer (to identify source for human)
  - GetCapabilities URL of each WMS

- User selects Layer(s) and requests a map or additional information.

- DLB/Atkinson bifurcation:

  - Jeff DLB:
    - Client issues FULL catalog query(ies) for the selected Layer(s)
      using the provided ID(s).
    - Client extracts information from FULL response, including
      GetMap URL of WMS instance.
    - Client does not issue GetCapabilities to WMS directly.
    - Client displays Layer metadata and/or map.

  - Rob Atkinson:
    - Client issues GetCapabilities request directly to WMS(es)
      and finds information using the provided Layer Name(s).
    - Client extracts desired information from Capabilities XML.
    - Client displays Layer metadata and/or map.