OGSA

After you've mastered the intracacies of international widget trade, you've decided that you want more. You want to diversify, yet build upon your core copentency in the international world of widgets. With your experience, you know how to talk the widget talk and walk the widget walk with widget producers in any country. In fact, you have gotten this international communiation down to an art, so much so that it almost bores you. You've noticed that the majority of these communications follow a certain arc, require certain services, and bore you to tears. So, in an effort to quell your ennui, you've decided to codify all these ``best practices'' of international widget trade, or as you call it IWT, into a set of common rules, rules that those engaging in IWT can follow to speed production.

Similarly, those working with WSDL in the Grid world soon realized that the majority of interprocess communication took a certain arc, followed certain rules, and required certain communication primitives and services be present. So, they set about codifying these into a set of ``best practicies'' that those in the Grid world could use to speed the production and adoption of Grid related technologies. This common set of rules is called OGSA.

OGSA consists of two sets of rules. The first set of rules defines a common service model, a set of properties which an OGSA service must possess. The second set of rules defines a set of common services which have proven their use in the field. Lets review each in turn.

• OGSA Service Model
• OGSA Common Services