Service model Telecon, July 17, 2001
Updated: August 30, 2001 10:47 - Page Maintained by Allan Doyle

[new colors, easier to do in real-time:] Agenda in blue, discussion during telecon in black, action items in red

Present

Allan Doyle
Carl Reed
Jim Stephens
Peter Vretanos
Yonsook Enloe
John Davidson
Ananth Rao
Archie Warnock
Arliss Whiteside
Lou Reich
George Percivall
John Evans
David O'Mahony

Agenda

1. Review of key happenings, actions, etc.

* Allan -- post of revised term definitions revised by Allan, Peter, & John
-- any terms flagged for issues?

* All - any comments to John Davidson on the GSM doc?

We started out talking about John's GSM document. Procedural and content. The consensus still seems to be to use the document as the basis. The issue is what is practical since the document has to go out by Friday. Action - John to update the GSM to v05 and post it asap.

The GSM should talk about how to combine WSDL and Capabilities. Action - Peter to send material to John for inclusion. This should help address the data vs. operations issue. Perhaps we should be able to turn on/off some of the capabilities response with flags in the request. Things like "just the operation content", "just the service content", "both". Suggestion to John to include a section called "future items" or "open issues". Action - send material for these to John. Peter volunteers.

* Use cases - received from Terry Fishers, George P. - still need one from Lou & Doug?

* yonsook - use case review with user types - will happen on 7/27 at ~8:30-10am EDT.

* Peter - any conclusions from analysis of Jeff Lansing's email on WSDL? Jeff is still on vacation. Peter's been using WSDL more, likes it more, still sees some deficiencies. Peter's test - can he generate a request template from a WSDL document - the answer is yes, it's almost there. HTTP POST seems to be there. HTTP GET does not have enough in it yet. Peter will have a running server with a WSDL document.

2. Status report from object modeling telecon about service type hierarchies
-- Allan/Peter/Serge ??
-- any leader for object modeling work yet?

next steps for service type hierarchies/object modeling

Serge will be posting something for Friday. One of the things that should be done is sample mappings of existing interfaces into the type hierarchy. E.g. use a new "Object Server" as the base class, extend it into WFS, WMS, etc. feel that this is premature to put in the GSM for the RFQ but the RFQ should indicate that people should try this as an exercise.

3. WSDL Work Item status

Integration of WSDL and GetCapabilities - Peter
WSDL instantiation of WFS -- Peter
WSDL instantiation of WMS -- Jeff dlb & Ananth - this is underway...
WSDL instantiation of WCS -- John Evans - getting started, work in progress

What works? What's easy & what's hard?
What does WSDL buy us? Are we still happy?

WSDL comments from Peter - we still have to retain the capabilities as a separate operation that will describe the service and the content. The WSDL description should be contained within the capabilities response. While this may seem a bit circular, we can bootstrap it via a capabilities GET URL just as we do now.

Lou points out that we have to begin work on new capabilities - XML Schema version is needed. The other issue is that of the content. How to use Capabilities to describe content. E.g. Map Layers, Feature Collections, Feature Types, etc. We have to separate content from operations.

Good question is how WCS falls into the type hierarchy. Can John Evans help with this?

4. Catalogs

* Jeff dlb & Larry will talk next week about summary/full responses

* Review of Stateless Catalog Profile doc - Written comments due by July 31
Who will provide comments?
Archie Warnock volunteered via email. Lou wants Peter, Compusult to review it. Action - Lou to post SOAP document via Allan. There's also a WSDL rendering of Z39.50.

6. Next steps

Think about what we are doing --

* step 1 -
integration of WFS/WMS/WCS using WSDL?
integrated GetCapabilities

Peter will send out a URL of a WFS that uses WSDL integrated with Capabilities.

* step 2 - integrate data and services ?

* step 3 - how to add ad-hoc services (services other than WMS/WCS/WFS)

* we're taking a look at various elements that will contribute to a service model
- what are we not covering?
- come up with list of uncovered stuff to track as future work/issues
- system metadata
- user metadata
- semantics

Questions -
- SOAP as a potential protocol - what's our stand on this?
- UDDI has to be considered for searching? Lou has looked at UDDI - they don't have the ability to base searches on data content or metadata.
- .NET - any implications here?

Peter's quick take: we have data/content. we have services that operate on the data. How does someone find the data or the service or both?

John - what's the scope of WMT-3 - do we need to spend resources investigating UDDI?

Lou - UDDI has two operations that are not connected too well. 1. you can search yellow or white pages for businesses that offer the kinds of services you might be interested in incorporating. Then there's a cloudy area, you negotiate with the business, build interfaces into their services etc. They have the tmodel that allows you to build the interfaces. In the tmodel they let you summarize that you've implemented a specific version of an interface so that the client code can be written against that spec.

There's still a role for OGC-style discovery.

7. Schedule next telecon
- review Stateless Catalog Profile Comments

Next telecon - Thursday August 2, 1100-1300