1. Mark Morgan 13-16 February, 2006 (GGF16 in Athens)
WS-Directory
Mark Morgan
13-16 February, 2006 (GGF16 in Athens)

2. GGF Intellectual Property Policy
All statements related to the activities of the GGF and addressed to the GGF are subject to all provisions of Appendix B of GFD-C.1, which grants to the GGF and its participants certain licenses and rights in such statements. Such statements include verbal statements in GGF meetings, as well as written and electronic communications made at any time or place, which are addressed to any GGF working group or portion thereof,
Where the GFSG knows of rights, or claimed rights, the GGF secretariat shall attempt to obtain from the claimant of such rights, a written assurance that upon approval by the GFSG of the relevant GGF document(s), any party will be able to obtain the right to implement, use and distribute the technology or works when implementing, using or distributing technology based upon the specific specification(s) under openly specified, reasonable, non-discriminatory terms. The working group or research group proposing the use of the technology with respect to which the proprietary rights are claimed may assist the GGF secretariat in this effort. The results of this procedure shall not affect advancement of document, except that the GFSG may defer approval where a delay may facilitate the obtaining of such assurances. The results will, however, be recorded by the GGF Secretariat, and made available. The GFSG may also direct that a summary of the results be included in any GFD published containing the specification.

3. Introduction to WS-Directory
Objective
To define a minimal Web Service interface for arranging and naming web service endpoints in a hierarchical, human-readable fashion
Emphasis on simple and quick

4. Definition of a WS-Directory
A WS-Directory is a web service resource (a web service which can be addressed by a WS-Addressing EndpointReferenceType which possibly implies associated state at the server) which contains a set of two-tuples defined as:
<name, entry-document>
An entry-document is an XML document which MUST contain an EndpointReferenceType (indicating the web service resource as defined above) indicating the resource named by this tuple, and which MAY contain additional, unspecified XML elements.
“WS-Directory entries MAY be WS-Directory resources themselves, thus recursively defining a hierarchy.”

5. Conceptual Interface WSDirectory
add(entryName: String, entry: EntryDocument): boolean
remove(entryPattern: String): int
lookup(entryPattern: String): WSDirectoryEntryMap
EntryDocument
<entry-document>
<endpoint>
wsa:EndpointReferenceType
</endpoint>
{xsd:any} *
</entry-document>

6. Example EntryDocument
<wsdir:entry-document>
<wsdir:entry-name>MySpecialFile.txt</wsdir:entry-name>
<wsdir:entry-reference>
<wsa:Address>
<wsa:ReferenceProperties>
<uva-guid>E521E66C-559E-4b0b EB747D864C</uva-guid>
</wsa:ReferenceProperties>
<ws-naming:abstract-name>uva-an: C-412e-842B-1F8865F51776</ws-naming:abstract-name>
</wsdir:entry-reference>
<foo:supported-port-types>
<foo:port-type>wsrp:GetResourceProperty</foo:port-type>
<foo:port-type>wsn:NotificationProducer</foo:port-type>
<foo:port-type>wsrl:ImmediateTermination</foo:port-type>
<foo:port-type>byteio:RandomByteIO</foo:port-type>
</foo:supported-port-types>
</wsdir:entry-document>

7. Iterators are a larger concept than just naming
Why no iterators?
Iterators are a larger concept than just naming
We believe a working group for result iteration is needed to address this

8. Some kinds of metadata are needed
What about metadata?
Some kinds of metadata are needed
Num entries
Timestamps
Etc.
WS-Directory is NOT a spec. right now, it’s a suggestion
Not fully fleshed out
“profiles” on top of WS-Directory likely to be a good idea (for example, for file systems)
Point is to recommend a basic, base class of interface that many working groups can use.