In no particular order:

Chartered Working Group activities

DAIS-WG

The group discussed current progress: the WS-DAI (GFD.74) and WS-DAIR (GFD.76) have gone through an interop process and have written this up in GFD.160. The group is currently awaiting a report stating whether these specifications can proceed to full recommendation status (having made the modifications suggested in GFD.160). Mario Antonioletti has resigned as DAIS chair and should be replaced by Oscar Corcho, assuming working group consensus, in April. Similarly, Steven Lynden has volunteered to become secretary for the DAIS WG and should also take on this role in early April.

The next steps for the group are relatively clear:

• Make the changes to WS-DAI and WS-DAIR to take them to full recommendaiton status.
• Make changes to the WS-DAI-RDF(S) Query spec from the changes made to the WS-DAI spec and put into public comment.
• AIST and UMP, who already have partial implementations of this spec, will do interop.
• Write an experiences document and take the WS-DAI-RDF(S) Query document to full recommendation status.
• Need to work out what the fate of the WS-DAI-RDF(S) Ontology work that has been going on in the group if it's going to progress.
• Need to wait for a second implementation of the WS-DAIX (GFD.75) spec to do interop.

DFDL

Spec produced and now entering public comment. Currently are looking for implementations.

GSM

Worked on rechartering as community group

DMI

• Got the ~DataMinx group involved which gives new push to the group. This resulted in new requirements for functional spec (bulk movement) which will be implemented in new version of the spec.
• Improved communication and integration with JSDL group.
• Mario Antoniolette steps down as group chair, and Stephen Crouch will take over.

GFS

• RNS1.1 is now in public comment
• Will change direction to file catalog standardization;
• Need to find a new co-chair.

DR-RG

Work on metadata case study and reference framework and best practices report (drafts circulated in the group).

SAGA

We had 4 SAGA sessions, all of them with acceptable attendance. We covered a multitude of topics, including current SAGA document status (experience document is getting close to completion, several API extension docs are now in the last call on the mailing list), implementation updates (external groups now start to implement SAGA adaptors, and we synchronized on the infrastructure for code management, distribution, testing, and interop testing), and synchronization with other standards (RPC, CPR, DRMAA, OCCI, BES, JSDL). In particular the experience document was extensively discussed, and it is still somewhat unclear, what exact interop aspects of the complex and elaborate SAGA implementation stack are to be tested and described therein.

JSDL

JSDL-WG did a final review of the Activity Instance Document specification and agreed that after some minor edits the document can be submitted to OGF for public comment as a proposed recommendation. The group also had a a number of requirements presentations from PGI-WG, XtreemOS and a proposal to extend data staging for general data movement. There is ongoing discussion to identify concrete new work items.

OCCI

• OCCI still kicks-ass!
• Adoption is slowly making progress but the overall (social)media is exited.
• While we are about to finish the docs based on the comments made other documents like our Implementors and Integrators Howto was seen as a highlight.
• The OCCI-wg will continue to focus on the IaaS layer but eventually mode into PaaS (maybe by getting DRMAA and OCCI working together).
• Also the Clouddemo which we are trying to get done for next OGF will be a major thing!

GRAAP

Pre OGF 28:

• Experiment document accepted as GFD.167
• 2 F2F meetings
• 1st complete draft of WS-Agreement Negotiation circulated

At OGF 28:

• Compiled WS-Agreement Version 1.0 Errata; two open issue to be resolved before submission
• Discussion of WS-Agreement Negotiation Protocol

After OGF 28:

• finalisation of WS-Agreement Negotiation before OGF 29, final discussion at OGF 29, submit after OGF 29
• finalisation of Advance Reservation micro-spec

NML

Decided on terms for these subtopics during OGF 28:

• Formal concensus on Topology / Domain concept
• Preliminary agreement on Adaptation / Layer concept, though Layer needs further refinements and Adaptation needs some examples for good understanding.
• Consensus on Service concept

Volunteers appointed for the following concepts:

• Link / Path / Segment concepts
• Identifiers concept
• Cross-connects and channels concepts

(Node / Port was done already at OGF 26; integration of these concepts in the schema and syntax representation of the schema is still to be done after these steps)

GIN

GIN Update Session on Monday

• Administrative issues: Call for additional Co-Chair & Roadmap
• More efforts would be useful driven by additional co-chairs
• Interoperability workshop @ PARA2010
• GIN Questionnaire about interoperability issues/challenges

GIN Demonstration Session on Monday

• Continuation of HPC-BP Demonstration (BES & JSDL)
• D-Mon demo of information system interoperability (GLUE2)
• EUFORIA fusion community demonstration (EGEE & DEISA)

GIN Interoperability Panel on Thursday

• Panel members of industry, end-user (i.e. fusion), e-infrastructures
• Discussions of convergence issues of Clouds/Grids/Middleware’s
• Piecing together a framework to drive greater efficiency

PGI

Three PGI Working Sessions on Tuesday

• Process definition in order to have a clear path forward in PGI
• Roadmap: Definition of requirements & building more consensus
• First strawman documents collected by OGF29
• Strawman document selected at OGF30
• (Presentations on linking work with JSDL groups / OGC groups)

PGI Workshop directly after OGF28

• Friday & Saturday, Room A016 , starting from 9:00 a.m.
• Open Workshop for all interested individuals

PGI Workshop in Amsterdam end of April

• 28. & 29. April, EGI.eu office
• Open Workshop for all interested individuals

DRMAA

The DRMAA WG sessions acted as extremely productive opportunity for bringing DRMAA Version 2 close to finalization. Beside tons of minor clarifications, we fixed the new advance reservation and parallel job support in DRMAAv2. SAGA people participated all the time, so the new DRMAAv2 API smoothly maps to their higher-level functionalities.

Another new development were the initial discussions about a OCCI binding of the DRMAA interface. This would bring OCCI an additional task model, and DRMAA a long-demanded RPC mapping.

GLUE

• Presentations on various efforts to render the Glue 2.0 into LDAP and XML.
• Discussion on producing the rendering documents.

New Group Activities (BoFs)

Access to Remote Instrumentation in Grid Environment BoF

(acronym: ARI - the name of the group could still change a bit)

• The BoF was successful
• During the session we have been continuing with drafting a charter, we should have soon the charter finalised

This working group is  spawned by RISGE-RG that will  focus its effort on providing a Shared Information Model (SIM) and defining concrete interfaces for accessing remote instrument . There is a need in the community for accessing remote instruments by using standard interfaces that are well defined and specified by standard approaches/procedures.  The main purpose of this  working group will be to standardize approaches in remote access interfaces to instruments though our SIM. Target devices including all kind of instruments including distributed sensor networks. As such, it concerns mostly the services for steering and monitoring instrument resources, granting security and authorization (policy), accessing combined or multiple devices, performing a calibration phase, and also services for acquiring data from instruments and operating on files and streams.

The effort of this working group will be focused initially use cases collected by RISGE-RG, also taking into account the standards and use cases in the  field of sensors (OGC –  SWE), and the CIMA interface and implementation. During its work, the group will consider the outcome of other groups  such as SAGA, OGSA ByteIO, GLUE. data from instruments and operating on files and streams. Collaboration with OGC is foreseen.

DCI Federation Protocol BoF

The DCI Federation Protocol BoF featured a presentation on the original use case from the German-based DGSI project, describing the two federation mechanisms of workload delegation and resource leasing. There was general consensus that this topic should be embraced in a OGF working group, and eleven participants volunteered for working on it. Open issues include additional use cases such as storage, licenses, and long-term archival, technology issues such as WSRF, and the setup of a joint testbed. A formal charter will be written as a next step, targeting WG foundation at OGF29.