This document specifies the core components for the Simple API for Grid Applications (SAGA Core API), a high level, application-oriented API for grid application development. The scope of this API is derived from the requirements specified in GFD.71 (�A Requirements Analysis for a Simple API for Grid Applications�). It will in the future be extended by additional API extensions.

In 2010/2011, a number of errata have been applied to this document. A complete changelog can be found in the appendix. Note that the API specified in this document version is thus labelled as version 1.1, and as such obsoletes the previous API version 1.0. Most changes should be backward compatible with the original specification (for details see changelog).

This document defines the HPC Basic Profile, consisting of a set of non-proprietary specifications, along with clarifications, refinements, interpretations and amplifications of those specifications which promote interoperability.

This document specifies the semantics and structure of the Job Submission Description Lan-guage (JSDL). JSDL is used to describe the requirements of computational jobs for submission to resources, particularly in Grid environments, though not restricted to the latter. The document includes the normative XML Schema for the JSDL, along with examples of JSDL documents based on this schema.

This document specifies the semantics and structure of the HPC Profile Application. The HPC Profile Application is an extension to JSDL 1.0 [JSDL10] that is used to describe an executable running as an operating system process. The document includes the normative XML Schema for the HPC Profile Application, along with examples of documents based on this schema.

This document presents a specification for a Basic Execution Service (BES): a service to which clients can send requests to initiate, monitor, and manage computational activities. The specification defines an extensible state model for activities; an extensible information model for a BES and the activities that it creates; and two port-types; BES-Management and BES-Factory. BES-Management defines operations for managing the BES itself. BES-Factory defines operations for initiating, monitoring, and managing sets of activities, and for accessing information about the BES. An optional unspecified BES-Activity port-type indicates an extension point for operations relating to the monitoring and management of individual activities.