- ogsa-wg - lists.ogf.org

OGSA Glossary revision 5 uploaded for July 9th call
by Treadwell, Jem 09 Jul '07

09 Jul '07

Hi, I've uploaded an updated draft (Draft 5) of the OGSA Glossary - you can find it at: https://forge.gridforum.org/sf/go/doc13938?nav=1 This is for discussion on the July 9th telecon (next Monday). Please take a look, and if you're not going to be on the call please let me have any comments as soon as possible. Note that: o Once comments have been addressed this draft will wrap up the OGSA/Reference Model glossary convergence activity. o For now, please just review the terms. I haven't yet fully addressed the changes needed to the front and end sections. o This draft includes several terms from the forthcoming OGSA Data Architecture document, supplied by the OGSA-D WG. The Data section in the OGSA Architecture doc will need to be revised in line with these changes; no firm plan for that at the moment. o On Monday's call we'll discuss next steps for the document - i.e. when and in what form to propose it for publication, and how to sync with the related documents. Thanks! - Jem Jem Treadwell Software Engineer HP ESS Software 856.638.6021 office | 856.638.6190 fax | jem.treadwell(a)hp.com 6000 Irwin Road | Mount Laurel | NJ 08054 www.hp.com/go/software <http://www.hp.com/go/software>

2 1

[Reminder] Glossary (Jem Treadwell) @ 2007-07-09 18:00 - 19:00 ()
by Google Calendar 08 Jul '07

08 Jul '07

ogsa-wg(a)ogf.org, this is a reminder for Title: Glossary (Jem Treadwell) Time: 2007-07-09 18:00 - 19:00 (Central Time) Where: http://ogsa.glance.net/?key=0709 Calendar: Description: When: 6-7pm EDT, 5-6pm CDT, 3-4pm PDT, 7-8am JST, 11pm-midnight UK The dial-in number for Monday; US: +1 718 3541071 (New York) or +1 408 9616509 (San Jose) UK: +44 (0)207 3655269 (London) Japan: +81 (0)3 3570 8225 (Tokyo) PIN: 4371991 See more information: - https://forge.gridforum.org/sf/go/wiki1477 Screen share service: URL: http://ogsa.glance.net/ Usage: https://forge.gridforum.org/sf/go/wiki1584 Note: ** OGF IPR POLICY APPLIES ** http://www.ogf.org/About/abt_policies.php 1) Early discussion Social study notification - https://forge.gridforum.org/sf/go/wiki1717 Note taker assignment Roll call Agenda bashing 2) Full document review (Jem Treadwell) Jem has uploaded an updated draft (Draft 5) of the OGSA Glossary - you can find it at: https://forge.gridforum.org/sf/go/doc13938?nav=1 Please take a look, and if you're not going to be on the call please let me have any comments as soon as possible. Note that: o Once comments have been addressed this draft will wrap up the OGSA/Reference Model glossary convergence activity. o For now, please just review the terms. I haven't yet fully addressed the changes needed to the front and end sections. o This draft includes several terms from the forthcoming OGSA Data Architecture document, supplied by the OGSA-D WG. The Data section in the OGSA Architecture doc will need to be revised in line with these changes; no firm plan for that at the moment. o On Monday's call we'll discuss next steps for the document - i.e. when and in what form to propose it for publication, and how to sync with the related documents. 3) when we publish (Jem Treadwell) How (or if) to publish the glossary separately from Architecture doc Minutes approval - June 11: https://forge.gridforum.org/sf/go/doc14605 Action Item review AI-0611a: Jem/Hiro will add to the agenda of the next Glossary call a discussion on how to publish the Glossary document AI-0611b: Jem will ask Donal F and Dave S to review the definition of 'state' and finalize it AI-0611c: Jem will ask the RM-WG chairs to consider the 'pool' term as part of their glossary AI-0611d: Jem will talk with Dave B on how to proceed with the Data terms and report back on the next call AI-0611e: Hiro will add to the next Roadmap call agenda a discussion on the relation of OGSA and Reference Model; and whether to include a description of that relation in the Roadmap. You can view this event at http://www.google.com/calendar/event?action=VIEW&eid=MGxoMzY3MWhrMTVhMzFhbW… You are receiving this courtesy email at the account ogsa-wg(a)ogf.org because you are an attendee of this event. To stop receiving future notifications for this event, decline this event. Alternatively you can sign up for a Google Calendar account at http://www.google.com/calendar/ and control your notification settings for your entire calendar.

1 0

[Reminder] Roadmap (Chris Jordan) @ 2007-07-09 17:00 - 18:00 ()
by Google Calendar 08 Jul '07

08 Jul '07

ogsa-wg(a)ogf.org, this is a reminder for Title: Roadmap (Chris Jordan) Time: 2007-07-09 17:00 - 18:00 (Central Time) Where: http://ogsa.glance.net/?key=0709 Calendar: Description: When: 7-8pm EDT, 6-7pm CDT, 4-5pm PDT, 8-9am JST, midnight-1am UK The dial-in number for Monday; US: +1 718 3541071 (New York) or +1 408 9616509 (San Jose) UK: +44 (0)207 3655269 (London) Japan: +81 (0)3 3570 8225 (Tokyo) PIN: 4371991 See more information: - https://forge.gridforum.org/sf/go/wiki1477 Screen share service: URL: http://ogsa.glance.net/ Usage: https://forge.gridforum.org/sf/go/wiki1584 Note: ** OGF IPR POLICY APPLIES ** http://www.ogf.org/About/abt_policies.php 1) Early discussion Social study notification - https://forge.gridforum.org/sf/go/wiki1717 Note taker assignment Roll call Agenda bashing 2) roadmap document review (Chris) roadmap v1.1 draft - https://forge.gridforum.org/sf/go/doc13733 Issue Tracker - http://forge.ogf.org/short/ogsa-wg/roadmap11 3) glossary publication process discussion (Jem, if time permits) How (or if) to publish the glossary separately from Architecture doc Minutes approval June 25: https://forge.gridforum.org/sf/go/doc14632 Action Item review * AI-0618b: The figure in Appendix A needs some rework. In particular delete WS-BaseNotification 1.3 from the WSRF box and format the text boxes (WSRF, WSN) so that they are both in 'foundation' or outside * AI-0618c: Chris J will add and assign a tracker artifact to check the status of all documents AI-0625a: Hiro will check number and status of the info model documents and send the information to Chris J (via tracker) AI-0625b: Chris J will send a mail to the list asking people if there are other documents that need to be added - Include a list of documents that are currently in the Roadmap for easy reference You can view this event at http://www.google.com/calendar/event?action=VIEW&eid=NWxsMm5vaWE1Mzdwc3R2Zm… You are receiving this courtesy email at the account ogsa-wg(a)ogf.org because you are an attendee of this event. To stop receiving future notifications for this event, decline this event. Alternatively you can sign up for a Google Calendar account at http://www.google.com/calendar/ and control your notification settings for your entire calendar.

1 0

[Invitation] Glossary (Jem Treadwell) @ 2007-07-09 6pm - 7pm ()
by Hiro Kishimoto 08 Jul '07

08 Jul '07

ogsa-wg(a)ogf.org, you are invited to Title: Glossary (Jem Treadwell) Time: 2007-07-09 6pm - 7pm (Central Time) Where: http://ogsa.glance.net/?key=0709 Calendar: Description: When: 6-7pm EDT, 5-6pm CDT, 3-4pm PDT, 7-8am JST, 11pm-midnight UK The dial-in number for Monday; US: +1 718 3541071 (New York) or +1 408 9616509 (San Jose) UK: +44 (0)207 3655269 (London) Japan: +81 (0)3 3570 8225 (Tokyo) PIN: 4371991 See more information: - https://forge.gridforum.org/sf/go/wiki1477 Screen share service: URL: http://ogsa.glance.net/ Usage: https://forge.gridforum.org/sf/go/wiki1584 Note: ** OGF IPR POLICY APPLIES ** http://www.ogf.org/About/abt_policies.php 1) Early discussion Social study notification - https://forge.gridforum.org/sf/go/wiki1717 Note taker assignment Roll call Agenda bashing 2) Full document review (Jem Treadwell) Jem has uploaded an updated draft (Draft 5) of the OGSA Glossary - you can find it at: https://forge.gridforum.org/sf/go/doc13938?nav=1 Please take a look, and if you're not going to be on the call please let me have any comments as soon as possible. Note that: o Once comments have been addressed this draft will wrap up the OGSA/Reference Model glossary convergence activity. o For now, please just review the terms. I haven't yet fully addressed the changes needed to the front and end sections. o This draft includes several terms from the forthcoming OGSA Data Architecture document, supplied by the OGSA-D WG. The Data section in the OGSA Architecture doc will need to be revised in line with these changes; no firm plan for that at the moment. o On Monday's call we'll discuss next steps for the document - i.e. when and in what form to propose it for publication, and how to sync with the related documents. 3) when we publish (Jem Treadwell) How (or if) to publish the glossary separately from Architecture doc Minutes approval - June 11: https://forge.gridforum.org/sf/go/doc14605 Action Item review AI-0611a: Jem/Hiro will add to the agenda of the next Glossary call a discussion on how to publish the Glossary document AI-0611b: Jem will ask Donal F and Dave S to review the definition of 'state' and finalize it AI-0611c: Jem will ask the RM-WG chairs to consider the 'pool' term as part of their glossary AI-0611d: Jem will talk with Dave B on how to proceed with the Data terms and report back on the next call AI-0611e: Hiro will add to the next Roadmap call agenda a discussion on the relation of OGSA and Reference Model; and whether to include a description of that relation in the Roadmap. You can view this event at http://www.google.com/calendar/event?action=VIEW&eid=MGxoMzY3MWhrMTVhMzFhbW… You are receiving this courtesy email at the account ogsa-wg(a)ogf.org because you are an attendee of this event. To stop receiving future notifications for this event, decline this event. Alternatively you can sign up for a Google Calendar account at http://www.google.com/calendar/ and control your notification settings for your entire calendar.

1 0

[Invitation] Roadmap (Chris Jordan) @ 2007-07-09 5pm - 6pm ()
by Hiro Kishimoto 08 Jul '07

08 Jul '07

ogsa-wg(a)ogf.org, you are invited to Title: Roadmap (Chris Jordan) Time: 2007-07-09 5pm - 6pm (Central Time) Where: http://ogsa.glance.net/?key=0709 Calendar: Description: When: 7-8pm EDT, 6-7pm CDT, 4-5pm PDT, 8-9am JST, midnight-1am UK The dial-in number for Monday; US: +1 718 3541071 (New York) or +1 408 9616509 (San Jose) UK: +44 (0)207 3655269 (London) Japan: +81 (0)3 3570 8225 (Tokyo) PIN: 4371991 See more information: - https://forge.gridforum.org/sf/go/wiki1477 Screen share service: URL: http://ogsa.glance.net/ Usage: https://forge.gridforum.org/sf/go/wiki1584 Note: ** OGF IPR POLICY APPLIES ** http://www.ogf.org/About/abt_policies.php 1) Early discussion Social study notification - https://forge.gridforum.org/sf/go/wiki1717 Note taker assignment Roll call Agenda bashing 2) roadmap document review (Chris) roadmap v1.1 draft - https://forge.gridforum.org/sf/go/doc13733 Issue Tracker - http://forge.ogf.org/short/ogsa-wg/roadmap11 3) glossary publication process discussion (Jem, if time permits) How (or if) to publish the glossary separately from Architecture doc Minutes approval June 25: https://forge.gridforum.org/sf/go/doc14632 Action Item review * AI-0618b: The figure in Appendix A needs some rework. In particular delete WS-BaseNotification 1.3 from the WSRF box and format the text boxes (WSRF, WSN) so that they are both in 'foundation' or outside * AI-0618c: Chris J will add and assign a tracker artifact to check the status of all documents AI-0625a: Hiro will check number and status of the info model documents and send the information to Chris J (via tracker) AI-0625b: Chris J will send a mail to the list asking people if there are other documents that need to be added - Include a list of documents that are currently in the Roadmap for easy reference You can view this event at http://www.google.com/calendar/event?action=VIEW&eid=NWxsMm5vaWE1Mzdwc3R2Zm… You are receiving this courtesy email at the account ogsa-wg(a)ogf.org because you are an attendee of this event. To stop receiving future notifications for this event, decline this event. Alternatively you can sign up for a Google Calendar account at http://www.google.com/calendar/ and control your notification settings for your entire calendar.

1 0

[Updated Invitation] Roadmap (Chris Jordan) @ 2007-07-09 5pm - 6pm ()
by Hiro Kishimoto 08 Jul '07

08 Jul '07

Details for the following event have changed: Title: Roadmap (Chris Jordan) Time: 2007-07-09 5pm - 6pm (Central Time) Where: http://ogsa.glance.net/?key=0709 Calendar: Description: When: 7-8pm EDT, 6-7pm CDT, 4-5pm PDT, 8-9am JST, midnight-1am UK The dial-in number for Monday; US: +1 718 3541071 (New York) or +1 408 9616509 (San Jose) UK: +44 (0)207 3655269 (London) Japan: +81 (0)3 3570 8225 (Tokyo) PIN: 4371991 See more information: - https://forge.gridforum.org/sf/go/wiki1477 Screen share service: URL: http://ogsa.glance.net/ Usage: https://forge.gridforum.org/sf/go/wiki1584 Note: ** OGF IPR POLICY APPLIES ** http://www.ogf.org/About/abt_policies.php 1) Early discussion Social study notification - https://forge.gridforum.org/sf/go/wiki1717 Note taker assignment Roll call Agenda bashing 2) roadmap document review (Chris) roadmap v1.1 draft - https://forge.gridforum.org/sf/go/doc13733 Issue Tracker - http://forge.ogf.org/short/ogsa-wg/roadmap11 3) glossary publication process discussion (Jem, if time permits) How (or if) to publish the glossary separately from Architecture doc Minutes approval June 25: https://forge.gridforum.org/sf/go/doc14632 Action Item review * AI-0618b: The figure in Appendix A needs some rework. In particular delete WS-BaseNotification 1.3 from the WSRF box and format the text boxes (WSRF, WSN) so that they are both in 'foundation' or outside * AI-0618c: Chris J will add and assign a tracker artifact to check the status of all documents AI-0625a: Hiro will check number and status of the info model documents and send the information to Chris J (via tracker) AI-0625b: Chris J will send a mail to the list asking people if there are other documents that need to be added - Include a list of documents that are currently in the Roadmap for easy reference You can view this event at http://www.google.com/calendar/event?action=VIEW&eid=NWxsMm5vaWE1Mzdwc3R2Zm… You are receiving this courtesy email at the account ogsa-wg(a)ogf.org because you are an attendee of this event. To stop receiving future notifications for this event, decline this event. Alternatively you can sign up for a Google Calendar account at http://www.google.com/calendar/ and control your notification settings for your entire calendar.

1 0

Re: [ogsa-wg] [OGSA-D-WG] Definition of "data service"
by Dave Berry 06 Jul '07

06 Jul '07

I suppose there is an ambiguity arising throught the phrase "expose the capabilities", as we don't have a definition of "expose". Perhaps we could find better words to express the intended meaning. I wondered about "make available the capabilities and data", but this might be confused with provisioning. (I notice that the OGSA definition of "virtualization" has dropped the phrase "make available"). How about: "A service that provides interfaces to the capabilities and data of one or more data resources within a service-oriented architecture." Dave. > >guru prasad wrote: > > The definition just tells me that Data Service just exposes the > > capabilities and/or data of data resource(s). But, it does not tell me > > if I can access this service to invoke those capabilities or the data of > > a data resource. > Donal Fellows replied: > It's exposing the capabilities, not (necessarily) a description of them. > A capability isn't exposed if it isn't (at least in principle) accessible.

2 1

Re: [ogsa-wg] [OGSA-D-WG] Definition of "data service"
by guru prasad 05 Jul '07

05 Jul '07

I have the following opinion about the proposed definition for a data service: "A service that exposes the capabilities or data of one or more data resources within a service-oriented architecture." The definition just tells me that Data Service just exposes the capabilities and/or data of data resource(s). But, it does not tell me if I can access this service to invoke those capabilities or the data of a data resource. If this is true, then, 'service' is too strong a term. It should be 'data resource descriptor'. Else, 'service that exposese the capabilities or data' has to be rephrased. Because it is not only exposing but also allowing the user to access those capabilities. I also agree to what bob natale had to say. The definition of data resource should evolve and be included with the definition of data service. Allen Luniewski <luniew(a)us.ibm.com> wrote: >From the Data Architecture glossary: Data sink: A data resource that receives the data copied by a data transfer mechanism from a source. Data Source: A data resource that contains the data to be copied to a sink via a data transfer mechanism. Informally, Data Architecture, and DMI for that matter, use these terms to denote the end points of a data transfer operation. A data resource is defined as: An entity (and its associated framework) that provides a data access mechanism or can act as a source or sink. (This is what currently on Grid Forge but source/sink really mean data source/sink). So, a data resource is the "thing" that both holds data and provides mechanisms for accessing its contents. Think of a data resource as something like a relational database or a file system as we have had for decades while the Data Architecture defines interfaces (services) that "front" a data resource, making it a participant in the service oriented architecture being defined by OGSA. Allen Luniewski IBM Cross Brand Services IBM Silicon Valley Laboratory 555 Bailey Ave. San Jose, CA 95141 408-463-2255 408-930-1844 (mobile) guru prasad <guru_bn(a)yahoo.com> Sent by: ogsa-wg-bounces(a)ogf.org 07/05/2007 10:54 AM To Mario Antonioletti <mario(a)epcc.ed.ac.uk>, Dave Berry <daveb(a)nesc.ac.uk> cc ogsa-d-wg(a)ogf.org, ogsa-wg <ogsa-wg(a)ogf.org> Subject Re: [ogsa-wg] [OGSA-D-WG] Definition of "data service" This brings me to this question: What is the difference between and data source and a data resource? Is former just the container for data and latter is responsible for managing one or more data sources? Mario Antonioletti <mario(a)epcc.ed.ac.uk> wrote: Hi, > Currently we're looking at something like the following: > > A service that exposes the capabilities or data of one or more > data resources within a service-oriented architecture. I think it should be "the capabilities and data" as opposed to "or". Similarly for the definition below. However, I think the one above is more succinct and thus gets my vote. > or > > A service that exposes the capabilities of one or more data > resources within a service-oriented architecture. These capabilities > might include data access, data transfer or data management. Mario +-----------------------------------------------------------------------+ |Mario Antonioletti:EPCC,JCMB,The King's Buildings,Edinburgh EH9 3JZ. | |Tel:0131 650 5141|mario@epcc.ed.ac.uk|http://www.epcc.ed.ac.uk/~mario/ | +-----------------------------------------------------------------------+ -- ogsa-wg mailing list ogsa-wg(a)ogf.org http://www.ogf.org/mailman/listinfo/ogsa-wg --------------------------------- Park yourself in front of a world of choices in alternative vehicles. Visit the Yahoo! Auto Green Center.-- ogsa-wg mailing list ogsa-wg(a)ogf.org http://www.ogf.org/mailman/listinfo/ogsa-wg --------------------------------- Ready for the edge of your seat? Check out tonight's top picks on Yahoo! TV.

3 2

Definition of "data service"
by Dave Berry 05 Jul '07

05 Jul '07

We invite comments on the definition of "data service" for the OGSA Data Architecture (and hence the OGSA Glossary). Currently we're looking at something like the following: A service that exposes the capabilities or data of one or more data resources within a service-oriented architecture. or A service that exposes the capabilities of one or more data resources within a service-oriented architecture. These capabilities might include data access, data transfer or data management. We think either of these would be a significant improvement on our previous definition. The emphasis in these new proposals is on linking data resources into an SOA, which fits nicely with the OGSA definition of a service: A software component participating in a service-oriented architecture that provides functionality and/or participates in realizing one or more capabilities. Our previous definition mentioned specific types of interfaces, which we think is too specific and not resistant to change: A service that is primarily intended to provide access to data stored in one or more data resources. A data service will provide one or more of the data access, data source or data sink interfaces defined in the OGSA Data Architecture. Comments welcome, especially before Monday's OGSA-WG call. Dave Berry Deputy Director, Research & E-infrastructure Development National e-Science Centre 15 South College Street, Edinburgh, EH8 9AA +44 131 651 4039 www.nesc.ac.uk <http://www.nesc.ac.uk/>

5 4

express profile documents
by Blair Dillaway 05 Jul '07

05 Jul '07

Hi Duane , Here are some additional comments on the express profile specs dated June 28, 2007. Overall I think these are considerably improved over the initial drafts. Secure-Addressing: - Line 69: "Extend the requirements of the WS-I ..." doesn't sound right. Perhaps "Address additional grid interoperability requirements not covered in WS-i..." - Line 86 "client to engage in secure communication." How about "client to engage in secure communication and effectively use an OGSA web service". This at least acknowledges concerns raised by David Chadwick about providing the tokens needed to authZ actions at the service. - Line 173: It should be WS-SecurityPolicy 1.2, not 1.5. - Line282: Add to end of the paragraph - "The INITIATOR may need the RECIPIENT's token to supply a verifiable key used for message-level encryption of an initial request message. - Section 4.3: If we're specifying a 'secure endpoint reference' then we should say something about how these EPR documents are distributed. There are several possible attacks from modifying these documents in transit (man-in-the-middle attacks, failing to sign and/or encrypt the message correctly). One option is to provide for signing of these documents by the service, in which case we should spec how they are signed. This is the most scalable approach. One could also assume distribution via trusted server over TLS/SSL, but that's likely unacceptable in a lot of environments. Secure-Transport - Line 248, 252: You reference the ciphersuites in WS-SecurityPolicy. This is a fine list of strong suites, but unfortunately doesn't include a cross-reference to the TLS/SSL standard ciphersuite identifiers. You provide an example translation on Line 384. A simple mapping table would likely help out people reading this spec who are familiar with the TSL/SSL suite names. - Line 312: Providing to EPR document signing would help address the issue you raise regarding EPRs coming from untrusted sources. Secure-Soap - Line 285: It says ".. this Profile requires encrypted communication". Based on prior discussions, I had thought it was agreed integrity protection was a MUST but confidentiality was optional? - Section 7: I still have a problem with the wording here. Stating in C0701 that "UsernameToken credentials SHOULD NOT be used for message authentication..", and then having Section 7.2 explain how to indicate they should be used for message level client authentication, seems contradictory. C0701 also says username tokens "are not cryptographically verifiable.". Of course, if one uses password digest (with nonce & timestamp) one can get cryptographically strong verification the sender knew the password and the token wasn't pasted in from some other message. Was your intent in C0701 to warn people that username tokens should be used with caution since they: 1) don't provide a basis for ensuring overall message integrity; 2) the binding between the token and message is weak? Perhaps just remove C0701 since it's the only numbered security consideration in the document and the requirements in Section 4.2 already ensure it can't be used unless you're using secure transport. Regards, Blair Dillaway

1 0