Agenda for the Call on Sep 7 Wed 20:00 EDT/Sep 8 Thu 9:00 JST
Folks, Here is an agenda for the call tomorrow. See you there! * Watch out for the irregular call number. Dial-in Number: 1-702-835-5000 (Las Vegas, Nevada) ### Proposed Agenda 1. Role call, note taker & time keeper, agenda bashing. (5 min) 2. Approval of the proposed contents for section "3.1 Concepts". (5 min) So far no comments on the contents presented last week. Confirm if it is ok to merge this to the draft. 3. Review of the proposed contents for section "3.2 Design Policy". (10 min) The material will be posted later. Check if we can put this into the draft. 4. Schedule for drafting a specification (5 min) The draft writing schedule with a date for each section will be posted later. Check the status for the schedule. Find if any need to be pushed to v2.0. 5. GGF15 sessions (5 min) I made two 90s as session requests. See more details, clicking the below link: http://www.ggf.org/gf/session_request/index.php?event=1&browse&order=5 Check if there are proposals for sessions. 6. Updates (5 min) If any others,... 7. Wrap up, Next meeting(5 min) I cannot make it on Sep 21, alternative is the 19th in U.S. time. Total: 40 min ### Logistics for the call Date & Time: Sep 7 Wed 20:00 EDT/Sep 8 Thu 9:00 JST Dial-in Number: 1-702-835-5000 (Las Vegas, Nevada) Participant Access Code: 7771111 -Keisuke
Hello there, Attached is a proposed schedule and the current status for drafting a spec. Comments will be discussed at the call tomorrow. -Keisuke Keisuke Fukui wrote:
4. Schedule for drafting a specification (5 min) The draft writing schedule with a date for each section will be posted later. Check the status for the schedule. Find if any need to be pushed to v2.0.
Hi,
3. Review of the proposed contents for section "3.2 Design Policy". (10 min) The material will be posted later. Check if we can put this into the draft.
Attached is the draft of section 3.2. I believe it is letter size this time :-) (Sorry for the previous document. I mistook the template.) Your comments are very much welcomed. Note that I use EPRs instead of WS-Names, since latest OGSA Basic Profile still refers WS-Addressing. I think we can move to WS-Naming when the Basic Profile supports it in the future version. Sachiko
Folks, Attached is my modification to the description, addressing to the comments from Tom during the today's call. Please take a look at it and give us your idea. P.S. For better understanding I used the terms as below: - ACS: refers to the ACS specification. - Implementation of the ACS repository: you know this. # We may have the implementation of the ACS compliant IDE, too. - The client of ACS: refers to both the consumer and the producer of ACS. -Keisuke Sachiko Wada wrote:
Hi,
3. Review of the proposed contents for section "3.2 Design Policy". (10 min) The material will be posted later. Check if we can put this into the draft.
Attached is the draft of section 3.2. I believe it is letter size this time :-) (Sorry for the previous document. I mistook the template.) Your comments are very much welcomed.
Note that I use EPRs instead of WS-Names, since latest OGSA Basic Profile still refers WS-Addressing. I think we can move to WS-Naming when the Basic Profile supports it in the future version.
Sachiko
Folks, Though there's not much discussion on this so far, I explored yet another alternative for the case 2), in which the consumers resolve the references. Attached is a modified one in terms of this. Though this is not my final proposal, I'd like share my idea on this. On the other hand, considering this will leave some uncertainties in specification detail, we may end up with eliminating this from the ACS 1.0. -Keisuke Keisuke Fukui wrote:
Folks,
Attached is my modification to the description, addressing to the comments from Tom during the today's call. Please take a look at it and give us your idea.
P.S. For better understanding I used the terms as below: - ACS: refers to the ACS specification. - Implementation of the ACS repository: you know this. # We may have the implementation of the ACS compliant IDE, too. - The client of ACS: refers to both the consumer and the producer of ACS.
-Keisuke
participants (2)
-
Keisuke Fukui -
Sachiko Wada