Mike, Thank you for your reply.

Transport: What is "SwA"? If it is WebServices, I think it can be effective in some situations.

SwA is "Soap with Attachment", which is a W3C Recommendation. http://www.w3.org/TR/soap12-af/ SOAP Message Transmission Optimization Mechanism (MTOM), which is also a W3C Recommendation, describes attachment related features along with some implementation details. http://www.w3.org/TR/soap12-mtom/ MTOM is the latest spec and W3C says SwA has been superceded by MTOM. I have not checked the MTOM spec yet. See also the Attachment Profile of WS-I. http://www.ws-i.org/Profiles/AttachmentsProfile-1.0-2004-08-24.html

Messaging(1): I like type-1 better and I think an exception path would be needed in both cases. Message(2): Like this one! Helps explain timing issues.

I agree, Perhaps the exception message is notfied as well. If you have other patterns of async messaging, please let us know.

GetContents: Term "key" will need clarificaction (is it meant to be AAID?). Perhaps ws-naming can be used for the AAID?

AAID identifies AA like EPR, so I don't think it will be the key to retrieve contents of the AA. I'm not sure what exactly AAID is, but I suppose AAID contains static information such as version and name of the application, while AA EPR is used to point the location of the AA entry (that is a WS-Resource), thus AA EPR may be dynamically changed. I agree that we need clarification of what AAID is and what the key to GetContents should be.

Transfer: I presume the key is sent with the Transfer request too. Perhaps we can dicuss policy issues with regard to transfers (security related I think) at the GGF

I agree. Security policy is especailly important in case of closs-site collaboration, i.e. Transter operation. Thanks. Sachiko At Wed, 22 Jun 2005 23:06:41 -0400, Michael Behrens wrote:

Looks great! I have a few comments below:

Transport: What is "SwA"? If it is WebServices, I think it can be effective in some situations. Messaging(1): I like type-1 better and I think an exception path would be needed in both cases. Message(2): Like this one! Helps explain timing issues. GetContents: Term "key" will need clarificaction (is it meant to be AAID?). Perhaps ws-naming can be used for the AAID? Transfer: I presume the key is sent with the Transfer request too. Perhaps we can dicuss policy issues with regard to transfers (security related I think) at the GGF

Sachiko Wada wrote:

...

Hi Keisuke and all,

I made some diagrams for the repository interface Keisuke posted today. I hope this will be some help.

Most of the diagrams are simple visualization of the new interface except for the asynchronous patterns (slide 2, 3) which are my rough ideas.

I also put my comments and questions with smiley mark. I'd like to hear your opinion at today's telconf.

Sachiko

At Wed, 22 Jun 2005 17:38:09 +0900, fukui wrote:

...

[1 <text/plain; ISO-8859-1 (7bit)>] Folks,

Attached is a proposed repository interface description for ACS, which is pland as among the GGF14 ACS-WG#2 agenda at the last call.

At tomorrow's call we will just verify the contents include valid technical points for the session, and will not examin the line by line. So please verify that we can discuss this at the GGF14 as a part of the agenda.

My apologies to my late posting for this.

-Keisuke [2 ACS-ARI_en.doc <application/msword (base64)>]

------- Sachiko Wada ASCADE, Inc. Tel. 03-5332-3636

-- Michael Behrens R2AD, LLC (571) 594-3008 (cell) *new* (703) 714-0442 (land)