October 2005 - acs-wg - lists.ogf.org

Last call for Application Contents Service Specification 1.0
by Keisuke Fukui 07 Mar '06

07 Mar '06

Folks in ogsa-wg, cddlm-wg and acs-wg, We, acs-wg, has come to completion of the ACS Specification 1.0 after discussions and reviews. This is the last call for comments before submission to the GGF Editor for publication. If you have comments, please get them to me by 9 am Japan time on Monday November 7. If there are no significant comments I plan to submit the document on Monday afternoon. Below is the link for the document: https://forge.gridforum.org/projects/acs-wg/document/draft-ggf-acs-spec-1.0… Regards, Keisuke Fukui ACS-WG co-chair

2 2

Agenda for the Call on Oct 26 Wed 20:00 EDT/Oct 27 Thu 9:00 JST
by Keisuke Fukui 28 Oct '05

28 Oct '05

Folks, Here is an agenda for the call tomorrow. See you there! ### Proposed Agenda 1. Role call, note taker & time keeper, agenda bashing. (5 min) 2. Review of the new Chapters for Samples, Schemas, Open Issues and Authors.(10 min) 3. Review of the remained comments through the document. (20 min) 4. Review of the "Issues in Spec" tracker items. (20 min) Please be prepared for discussion in order of the priority as shown in below link: https://forge.gridforum.org/tracker/index.php?group_id=147&atid=805&filter=… 5. Schedule toward the submission of the draft (5 min) - Current progress is shown in the attached excel sheet. - Proposed new schedule (with an additional review meeting): Oct 27 Review of the rest, Issues List, Samples, Authors, Open issues, style check Oct 28 Last call announcement on the acs-wg ML. Oct 31 Submission to the GGF editor [Projection] Mid Nov. Comments from GGF editor received. End Nov. Comments are addressed and returned. Early Dec. 60 day public review starts. Early Feb. review comments are collected. Mid Feb. updated draft is returned to GGF editor. End Feb. approval by GGF. 6. Updates (5 min) - If any others,... - OASIS SDD TC F2F will be held during Nov. 14-16. 7. Wrap up, Next meeting(5 min) - On October 30, the daylight saving time will end in the U.S. - I ask for skip of the meetings on Nov 2nd and 16th. Total: 70 min ### Logistics for the call Date & Time: Oct 26 Wed 20:00 EDT/Oct 27 Thu 9:00 JST Dial-in Number: 1-712-432-2000 (Lake Park, IA) Participant Access Code: 7771111 -Keisuke

2 5

[acs-wg | Document Issues/Change Requests (test) - 1393] Create and test doc tracker
by Sourceforge Tracker Monitor 26 Oct '05

26 Oct '05

Michael Behrens changed 1393 on 2005-10-26 21:47:58 Close Date has changed: - New: '2005-10-26 21:47:58' Old: '-' Status has changed: - New: 'Closed' Old: 'Open' Respond by visiting: https://forge.gridforum.org/tracker/?func=detail&atid=790&aid=1393&group_id… (https://forge.gridforum.org/tracker/?func=detail&atid=790&aid=1393&group_id…) Summary: Create and test doc tracker Project: Application Contents Service WG Tracker: Document Issues/Change Requests (test) Artifact ID: 1393 Category: Content Group: ACS Specification Status: Closed Priority: 1 Last Modified By: Michael Behrens Last Modified: 2005-10-26 21:47:58 Submitted By: Peter Ziu Submit Date: * 2005-04-21 15:30:51 Assigned To: Peter Ziu Close Date: 2005-10-26 21:47:58 Originated By: Keisuke Fukui File(s): <None> Description: Create and test tracker for ACS document development. View the Document Issues/Change Requests (test) : https://forge.gridforum.org/tracker/index.php?func=browse&group_id=147&atid… (https://forge.gridforum.org/tracker/index.php?func=browse&group_id=147&atid…)

1 0

Teleconference minutes - Oct 19
by Sachiko Wada 24 Oct '05

24 Oct '05

Hi team, Here is the minutes of the last teleconf. Please review it and point out where the record is not correct, if any. It is also available at Gridforge: https://forge.gridforum.org/projects/acs-wg/document/minutes-20051019/en/1 Sachiko ======================================================================= ACS Teleconference ----------------------------------------------------------------------- Date and Time: Oct 19 20:10-21:40 EDT 2005 / Oct 20 9:10-10:40 JST, 2005 Participants: Keisuke Fukui (Fujitsu) Peter Ziu (Northrop) Michael Behrens (R2AD) Sachiko Wada (ASCADE) - minutes ------------------------------------------------------------------------ * Review of the proposed contents for section "3.3 Relationship to other activities". Agreed to merge to the current draft. Detail discussion: - 3.3.1 OASIS SDD TC Change the title of table 3-1 to "Relationship summary". (Done on the draft 0.54.) - 3.3.3 CDDLM WG Reset the footnote number for each page. - 3.3.4 OGSA Data WG No comments. - 3.3.5 OASIS WSDM TC Currently WSDM is preferred one, but ACS doesn't need to identify the manageability specification since it is separate from the interoperability for the ACS users. As a note, OGSA-WG is going to create new profile based on WS-Management in addition to the current one. OGSA WSRF Basic Profile doesn't mention to WSDM, either. Add words "such as OGSA profiles" to the following sentence. "the ACS specification leaves the manageability aspect to the standards set byexternal references". (Done on the draft 0.54.) * Review of the proposed draft for the section "7.4 Signature" and the additional elements (or properties) for AA in the draft 0.53. In addition to newly proposed "7.4 Signature" section, AAF section has also changed so as to follow XML Signature standard. Proposed draft was agreed with no major comments. (Merged into the draft 0.54.) * Review of the proposed draft for the chapter 1 and 2 in the draft 0.53. - Chapter 1. Introduction - Chapter 2. Requirements Review the chapter 1 line by line and modified if agreed. Due to time restriction, we could not go through chapter 2. Keisuke will merge the chapter 1 and 2, then everyone makes comments to it by next meeting on the ml. (Merged into the draft 0.54.) * Resource properties Mike agreed to push his propsal with respect to resource properties to future items. ^^^^^^^^^^^^^^^on * Schedule toward the submission of the draft The proposed schedule was agreed. * Next meeting Date: Oct 26 Wed 20:00 EDT/Oct 27 Thu 9:00 JST Calling #: will be announced later

1 0

Agenda for the Call on Oct 19 Wed 20:00 EDT/Oct 20 Thu 9:00 JST
by Keisuke Fukui 21 Oct '05

21 Oct '05

Folks, Here is an agenda for the call tomorrow. See you there! ### Proposed Agenda 1. Role call, note taker & time keeper, agenda bashing. (5 min) 2. Review of the proposed contents for section "3.3 Relationship to other activities". (10 min for each; 15 min) - Review the drafts if available. 3.3.1 OASIS SDD TC - Tom 3.3.4 OGSA Data WG – Mike, Pete 3.3.5 OASIS WSDM TC - Tom - I will post the draft description for 3.3.5 later in separate post. Including the brief comments on manageability in the section 3.3.5, I propose the omission of the "Chapter 6 Manageability" from the draft. Goal: Find if we can merge these into the final draft. 3. Review of the proposed draft for the section "7.4 Signature" and the additional elements (or properties) for AA in the draft 0.53.(10 min) - Proposed draft description for "7.4 Signature" - Proposed additional elements and/or properties for AA. Goal: Find the closure on the issues. 4. Review of the proposed draft for the chapter 1 and 2 in the draft 0.53.(15 min) - Chapter 1. Introduction - Chapter 2. Requirements 5. Schedule toward the submission of the draft (5 min) - Current progress is shown in the attached excel sheet. - Proposed new schedule (with an additional review meeting): Oct 20 Review of the Section 3.3 and 7.4, Chapter 1 and 2. Oct 27 Review of the rest, Issues List, Samples, Authors, Open issues, style check Oct 31 Submission to the GGF editor [Projection] Mid Nov. Comments from GGF editor received. End Nov. Comments are addressed and returned. Early Dec. 60 day public review starts. Early Feb. review comments are collected. Mid Feb. updated draft is returned to GGF editor. End Feb. approval by GGF. 6. Updates (5 min) - If any others,... 7. Wrap up, Next meeting(5 min) - On October 30, the daylight saving time will end in the U.S. Total: 55 min ### Logistics for the call Date & Time: Oct 19 Wed 20:00 EDT/Oct 20 Thu 9:00 JST Dial-in Number: 1-712-432-2000 (Lake Park, IA) Participant Access Code: 7771111 -Keisuke

1 3

[ogsa-d-wg] OGSA-D-WG description for ACS specification:
by Michael Behrens 20 Oct '05

20 Oct '05

This is being posted to the ACS and OGSA-D group for inter-group communication purposes. ACS needs to be aware of data services as they will impact the ACS specification at some point in time. The ACS specification has a non-normative section for describing relationships with other groups/activities. This is the proposed paragraph for your review - what do you think? "The OGSA Data Working Group defines the data services which provide for distribution of data on the grid. ACS can utilize protocols being specified such as Byte-IO, GridFTP, and possibly Replication. ACS provides an extension point for protocols which allow implementations to specify which protocols are supported. The ACS team has reviewed their briefings and draft documents with interest. Interaction with the OGSA Data Working group is expected to increase during the development of the next version of this specification." -- Michael Behrens R2AD, LLC (571) 594-3008 (cell) *new* (703) 714-0442 (land)

3 6

New description for section 7.4
by Keisuke Fukui 19 Oct '05

19 Oct '05

FYI, As discussed in the last meeting, I am sending the missing description for section 7.4 Signature. Please take a look at it to review this in the meeting tomorrow. Thanks in advance. -Keisuke

1 0

Teleconference minutes - Oct 12
by Sachiko Wada 17 Oct '05

17 Oct '05

Hi team, Here is the minutes of the last teleconf. Please review it and point out where the record is not correct, if any. It is also available at Gridforge: https://forge.gridforum.org/projects/acs-wg/document/minutes-20051012/en/1 Sachiko ======================================================================= ACS Teleconference ----------------------------------------------------------------------- Date and Time: Oct 12 20:10-21:50 EDT 2005 / Oct 13 9:10-10:50 JST, 2005 Participants: Keisuke Fukui (Fujitsu) Peter Ziu (Northrop) - regrets Michael Behrens (R2AD) Sachiko Wada (ASCADE) - minutes ------------------------------------------------------------------------ * Review of the proposed contents for section "3.3 Relationship to other activities". 3.3.1 OASIS SDD TC - Tom 3.3.4 OGSA Data WG - Mike, Pete 3.3.5 OASIS WSDM TC - Tom Action: Keisuke, to ask Tom to post the drafts in this week. (Done Oct 12) Action: Mike, to write draft for section 3.3.4 and send it to the ML. (Done Oct 13) * Schedule toward the submission of the draft Proposed schedule is approved. Oct 13 Review of the Chapter 7 then Chapter 1 and 2. Oct 20 Review of the rest, Open issues, style check Oct 27 Submission to the GGF editor [Projection] Mid Nov. Comments from GGF editor received. End Nov. Comments are addressed and returned. Early Dec. 60 day public review starts. Early Feb. review comments are collected. Mid Feb. updated draft is returned to GGF editor. End Feb. approval by GGF. Carry on items to version 2.0 will be described in chapter 11 "Open Issues". Action: Keisuke, to compile issues raised at GGF15 sessions. (Done Oct 12) * Review of the proposed draft for the chapter 7 AAF in the draft 0.51. - Relationship to SDD. For the version 1.0, we don't have any dependencies to SDD. Convergence with SDD will be addressed in the open issues chapter. - Version format. Mike's question: Why do we use xsd:string type to describe version instead of using separate types such as major, minor, etc. Answer: The spec should accept various version numbering semantics enforced by any development environment (tools) to be used with ACS. - Uniqueness of AAID Sachiko's question: If different producers try to create AA instances that have same AAID, is it failed? Answer: Yes. AAID must be unique in a repository. The combination of the name and version element in the AAID should be kept unique in the repository between producers. - AccessConstraint. This element specifies security policy for information contained in Application Archive, thus mainly it should be about access control. The generic security policy should be described and kept by system implementation rather than by each AA. This element should be optional. - CheckSum for each content. The term "digest value" may be more appropriate. We need check other standards like XML Signature. - Differential AAD. Mike's question: Can binary differentials be included in AA? Answer: The differential here is in a granularity of Application Content. Differential updates finer than it, for example using a binary patch, is not specified in ACS, though they can be practiced in a implementation specific way with prior agreement between producers and consumers. - Version management. We currently have only simple attributes that indicate parent and immediate children. For future discussion, Mike suggested adding attributes to describe richer dependency information between AAs. - Physical format. Mike suggested having auto installable format in order to help automated provisioning. One may execute GetContents automatically to obtain content on which it depends. Agreed to discuss about this as an open issues. Action: Keisuke, to merge section 1.3 Notational Conventions and 1.4 Namespace (posted on Sep 26 by Sachiko) to the draft. (Done Oct 14) Action: Sachiko, to add XML schema diagrams. Action: Keisuke, to compress and simplify the description, especially the Differential AAD section. Action: Mike, to post his proposal for AAD to the ml. (Done Oct 12) * Updates Keisuke attended CDDLM teleconf on Oct 12 and discussed possible interaction between ACS and CDDLM. The conclusion is either of three sequences Stuart proposed will work and there is no preference from ACS view. * Next meeting Date: Oct 19 Wed 20:00 EDT/Oct 20 Thu 9:00 JST Calling #: will be announced later

1 0

Archive Descriptors or Resource Propoperties or Both
by Michael Behrens 17 Oct '05

17 Oct '05

For the draft spec 0.51, I propose these additional optional elements. Perhaps they could be both in the AAD and exposed as resource properties: <aaf:Requires>xsd:string</aaf:Requires>* The AAID which this one content requires. This can be used to automatically obtain all dependencies. <aaf:Conflicts>xsd:string</aaf:Conflicts>* The AAID which this one conflicts with. <aaf:Replaces>xsd:string</aaf:Replaces> The AAID which this one replaces. <aaf:ReleaseNotes>xsd:string</aaf:ReleaseNotes> (like a readme.txt content)* <aaf:ContentType >xsd:string</aaf:ContentType > The type of content or the purpose of the content: Patch, Base, Differential, Data. Data means non-executable static data. <aaf:GroupName>xsd:string</aaf:GroupName> This is the group of the AA. This way, a hierarchy can be rendered/determined as needed. <aaf:PatchVersion>asd:string</aaf:PatchVersion>? Indicates the patch number or release if this content is a patch Add to AAID? <aaf:icon> <small> </small>? <large> </large> </aaf:icon>? This would be a binary PNG 32x32 or 64x64 for use with IDEs, etc. ALSO: Installation Package - Mention that an application content (AC) might be stored as an auto-installable format, such as an .msi, or installable/executable jar, or possibly even an .sdd? This would make provisioning/installation (silent installs) easier perhaps. Just an idea for future discussion. I presume we could use SDD equivilants for these and the other ADD elements - if so, perhaps that needs to go into the SDD section that Tom is working. Multiple Pulls with dependency could be managed using the dependency tree - perhaps using SDD elements? -- Michael Behrens R2AD, LLC (571) 594-3008 (cell) *new* (703) 714-0442 (land)

2 1

[Fwd: BOUNCE acs-wg@ggf.org: Non-member submission from [Allen Luniewski <luniew@almaden.ibm.com>]]
by Keisuke Fukui 16 Oct '05

16 Oct '05

Forwarding a bounced e-mail.

1 0