July 2007 - ogsa-wg - lists.ogf.org

Teleconference minutes - 9 July 2007 - Roadmap & Glossary
by Andreas Savva 10 Jul '07

10 Jul '07

Minutes are on gridforge: Roadmap: https://forge.gridforum.org/sf/go/doc14660?nav=1 Glossary: https://forge.gridforum.org/sf/go/doc14659?nav=1 -- Andreas Savva Fujitsu Laboratories Ltd

1 0

Last call for additions to the Roadmap
by Christopher Jordan 09 Jul '07

09 Jul '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Fellow OGSA working group members, We are currently trying to finalize the document list for the OGSA Roadmap document. In order to ensure that we have all the appropriate documents listed in the Roadmap, I am sending this request that document authors and editors review the following list of documents which are currently described in the OGSA Roadmap draft. If there are documents on this list which have changed title or function in the past few months, or there are documents which are not on the list but should be, please send a note either to myself or to the OGSA-WG list, or join one of the Roadmap calls, to discuss any additions or changes which need to be made. The list below only includes document titles and versions. To view the full description and schedule for each of the documents, please consult the latest draft of the Roadmap document, available from: http://forge.ogf.org/sf/go/doc13733?nav=1 (New additions, to be discussed today but not on the list below are the Express Authentication Profile, Resource Modeling, and the EGA Reference Model reconciliation document) Informational Documents _____________________ OGSA Architecture Version 1.5 OGSA Glossary Version 1.5 OGSA ByteIO Use-Cases Version 1.0 OGSA Data Architecture Version 1.0 Naming Issues in Distributed Systems Version 1.0 OGSA EMS Architecture Scenarios Version 1.0 Normative Documents ___________________ OGSA ByteIO Interface Document Version 1.0 OGSA Basic Execution Services Interface Document Version 1.0 Job Submission Description Language Specification Version 1.1 Resource Namespace Service Specification Version 1.0 WS-Naming Specification Version 1.0 Application Content Service Specification Version 1.0 WS-Agreement Specification Version 1.0 Attributes Used in OGSA Authorization Version 1.0 Recommended Profiles _________________________ OGSA WSRF Basic Profile Version 1.0 OGSA Security Profile 1.0 – Secure Channel OGSA Basic Security Profile 1.0 – Anonymous Channel Thanks. Chris Jordan Data Reliability Manager Digital Preservation Initiatives San Diego Supercomputer Center ctjordan(a)sdsc.edu 858.534.8347 http://del.icio.us/tensileacuity "I have lots of problems. But they belong to me." - Sex, Lies, and Videotape -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFGkp7EPCVtcXn6kg8RAmi7AKDbxMOdGYfyvHjnabCm8p27WXJYswCgsmGh pPJt2wucW+7WnhsZ3q9hrmA= =c1B3 -----END PGP SIGNATURE-----

1 0

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

09 Jul '07

Thank you for your comments Allen. In that case I vote for Dave Berry's definition: "A service that provides interfaces to the capabilities and data of one or more data resources within a service-oriented architecture." and the Data Resource is ..... Allen Luniewski <luniew(a)us.ibm.com> wrote: My comments below. 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> wrote on 07/06/2007 12:46:49 PM: > In essence, it is clear with the discussions we have been having > that it is not enough to define a data service as something that > "exposes the capabilities and data of data resource". > > I agree to dave's definition. However, I think we need to define > Data Resource in conjunction with the definition of the Data > Service. I have also compiled all the comments we are exchanging See my note below. We have done this as part of the Data Architecture. I believe that the definitions of data resource and data service are consistent with one another > back and forth in this single mail. > > > Quesiton 1: > If the Data Service is advertising the capabilities and the data, > will the onus be on the data resource to provide QoS. No. The data service is responsible for agreeing to, and providing, QoS. Obviously it will do using whatever capabilities the data resource provides. Moreover, it is quite reasonable to expect that the ability of a data service to provide QoS is constrained by the QoS capabilities of the data resource. But that is an implementation issue and not one that the user of the data service is aware of. > > Say for example: My data service says that a data resource provides > "copy" feature on a certain data. Then who should ensure that copy > feature is available, and upon invoking with right credentials and > parameters that it "copy" is successful? Will that be data resource? > or the me who is invoking the "copy" capaibility? In all cases, the answer is the data service. > > This is important because the definitions we have/are > proposed/proposing do not make these vital things clear. All we are > saying is service exposes capabilities and the data while the data > resource that holds the data and provides various mechanisms to > access the data. > > Question 2: > > What about the possibility of a single data source and different > capabilities on that source provided by different data resources. As posed, this is an issue outside of the context of the data architecture - the operations provided by a data resource are outside of the architecture. To put your question differently, it is quite possible, and reasonable, for their to be many data services that use the same data resource. > > For Example: I am a employee table. I have a "update" capability > from data resource one on view1. I have "add" capability provided by > data resource two on view2. Effectively, I am still the same physical table. This question is outside of the data architecture since you are proposing a direct interaction with the data resource. If I substitute "data service" for "data resource" in your question, then the operations you can perform are dependent on whether you access via view1 or view2. In this example, the effect will to make changes to the same data resource. > > > > Related conversations. > > DONAL: > > guru prasad wrote: > > 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." > > I'm trying to understand why there should be a distinction between > "capabilities" and "data" in this context. Data's interesting for what > you can do with it. :-) > > > 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. > > It's exposing the capabilities, not (necessarily) a description of > them. > > > 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. > > A capability isn't exposed if it isn't (at least in principle) > accessible. > > Donal: > > guru prasad wrote: > > This brings me to this question: What is the difference between and > data > > source and a data resource? > > A data source is an origin endpoint for a data transfer, and is > typically positioned on a data resource. A data resource is some > structured information (==data) that can be used by an activity, > monitored for changes, lifetime-managed, etc. (==resource); i.e. a data > resource is data that is a resource. Obvious really. :-) > > > Is former just the container for data and latter is responsible for > > managing one or more data sources? > > Now you're getting mixed up between the service instances that > implement > the concept space and the concepts themselves. Both "data source" and > "data resource" are concepts, and they map respectively to things like > a > service instance that can stream the results of a database query or a > file. It might be that the two things are implemented in the same > component, but that's not required. Also, a single data resource may > have many different sources associated with it (corresponding to views > of the data, transfer methods, etc.) > > If it helps, remember that I regard the act of data transfer as an > activity. > > Donal. > > Allen Luniewski: > > 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. > > > Dave Berry: > > 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." > Sick sense of humor? Visit Yahoo! TV's Comedy with an Edge to see > what's on, when. --------------------------------- Don't get soaked. Take a quick peak at the forecast with theYahoo! Search weather shortcut.

2 2

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

[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

[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

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