- All participants should register and annotate a web service in the demo registry at https://demo.edunify.pesc.org.
- Add/review requirements to the requiments pageson the Differential Requirements Page.
The group met for about 50 minutes and agreed that the initial tasks are to perform a review of the current state of the art with a survey of the literature on web service directories with a focus on distributed, federated directories as decided at the meeting in DC. The group reviewed the bibliography page and initial citations and agreed to review these papers and links and each add one or two relevant references by the next meeting. The group also reviewed the example use case (Register a Web Service) in detail to serve as an example for the initial draft of the other use cases. The group then assigned a lead author for each of the five remaining use cases defined to date. The lead authors will create an initial draft by the next meeting.
Friday, January 22
The group met and reviewed the first draft of each of the use cases prepared by members of the group. We discussed each case breifly, highlighting what work or refinement remains for each use case. All members of the group will review, update, and comment on all of these initial drafts by the next meeting. We also made some specific assignments.
- Update Use Case 1: Provide an initial draft of the service metadata that will be maintained as part of the core registry record (Steve Wheat)
- Update Use Case 3: Add specific structures and examples of user rating and scoring data that could be maintained as part of the index services provided by EdUnify or others mining directory data (Richard Moon)
- Update Use Case 4: Provide an initial definition and examples of service monitoring requests, responses, and data maintained as part of the index services. (Thomas Jackson)
- Add a use case with a robot or spider application as the actor (Steve Wheat)
The primary topic of the next meeting will be candidate designs contained in the literature on the bibliography page. The group will report on some candidate designs in the EdUnify Business Work Group meeting next Wednesday, January 27 and review and discuss these designs further on Friday, January 29. The group is still in the early stages of considering these designs and their implications, but it will start posting materials pertaining to the review of these designs next week.
Friday, January 29
The group met and discussed aspects of the technical design. Arnie Miles from Georgetown University provided an outline to guide the discussion. The discussion contemplated a registry approach and an index approach. We also discussed various topologies for implementing these approaches. The discussion then focused on the precise method for registering or publishing web service metadata for inclusion in a registry or index. This question is the first step toward a registry or an index. The group discussed the Active Web Service Registries article posted by Jan Huus on the bibliography page and decided to explore the implications of this method or something similar for publishing web service metadata. One of the primary advantages of this method is its simplicity. This method would be very easy for organizations to adopt and implement. The group needs to discuss this aspect of the design further, but we decided to begin a page to record details and implications of this design for further discussion. After the meeting Steve Wheat posted the EdUnify Candidate Technical Design page for this purpose. By next week the technical work group participants will read the candidate design page and add comments and enhancements.
Feburary through March 2010
The group had several undocumented calls in which we reviewed the BioCatalogue as a potential starting point for demonstration and detailed requirements gathering. The group decided to implement BioCatalogue for demonstration purposes and began discussing more detailed security requirements.
and started work on the Differential Requirements Page , specifying requirements in the area of security and verification and service registration.