Is the telecon still on for tomorrow AM? I've read the document - I like the use-cases. I would suggest more emphasis on service migration - perhaps a use case could be added to illustrate how migration would affect the mapping service and client caching? Naming is an important component of service virtualization or abstraction - look forward to the call - or followup emails. Andrew Grimshaw wrote:
All,
Recall that back at the January face-to-face Frank and Dave took an action to write up their take on the requirements for (low-level) naming. Attached is their draft.
A few comments of mine based on my read and discussions of the document with Dave.
1) This is not intended as a replacement for the existing work.
2) It is requirements - not specifications. Rather, it is a call for specifications that address the requirements.
3) Several of the requirements are met by the existing WS-Naming draft specification, though some are not.
4) Two of the proposed "specifications", 5.2 and 5.4 are covered by the existing WS-Name specification. A variant of 5.3 is covered in the WS-Name spec. The variant specified a technique that could be used to ensure that identifying information would be sent with the headers - specifically embed names in the reference parameters. Personally I fell that 5.3 is a fine replacement for that if desired. 5.1 is not covered at all, and I must confess that it seems so obvious that I had implicitly assumed it true. Dave says it is not - so having a spec that says it must be true seems ok to me.
5) I think that with a small amount of work on this document and the WS-Name spec we can make them dovetail quite nicely.
GGF is a scant two weeks away. I'd like to schedule a teleconference with the following agenda on Friday April 28th, at 10 AM eastern. (Dial in information as soon as I find a dial in number we can use.) If you plan on attending, PLEASE read both the existing draft WS-Name spec and this document before the call.
Proposed Agenda:
Max time Subject
5 minutes Agenda bashing
30 minutes Discuss draft requirements document including vis a vis existing draft WS-Name document
30 minutes Discuss approval of DRAFT WS-Names document to send to GFSG for GFSG approval. Note we will prepare a version that does not include the language that overlaps 5.3.
25 minutes Attempt to come to closure on working group consensus regarding WS-Directory, RNS, or
failing that, at least what the issues are.
Andrew Grimshaw
Professor of Computer Science
University of Virginia
434-982-2204
grimshaw@cs.virginia.edu
-- Michael Behrens R2AD, LLC (571) 594-3008 (cell) (703) 714-0442 (land)