Hi guys,

For those who just started reading the mail exchanges and had issues finding the links that Dave sent. Here are the working links..

http://code.google.com/p/dtsproject/source/browse/trunk/dts-jaxb/src/main/resources/archive/dmi-messagesProposals.xml
http://code.google.com/p/dtsproject/source/browse/trunk/dts-jaxb/src/main/resources/archive/dmi-messagesProposals.xsd
http://code.google.com/p/dtsproject/source/browse/trunk/dts-jaxb/src/main/resources/archive/MINX-DataTransferRequest-Example.xml

Sorry, I had to move stuff around today and unclutter that directory so I could only keep the schema we're using on the project in the resources directory. I also uploaded new schemas which now reuse the types/elements defined in OGSA-DMI and JSDL.

Cheers,
Gerson

On Thu, Jul 16, 2009 at 7:04 PM, Meredith, DJ (David) <david.meredith@stfc.ac.uk> wrote:
Hi folks,

Further to Mario's email, a couple of useful links for Friday's meeting:

1) The proposal for a wrapped message request is at the following link
(for transferring multiple files and directories in one atomic request
by wrapping multiple src-sink DEPRs):
http://code.google.com/p/dtsproject/source/browse/trunk/dts-jaxb/src/mai
n/resources/dmi-messagesProposals.xsd

An example at:
http://code.google.com/p/dtsproject/source/browse/trunk/dts-jaxb/src/mai
n/resources/dmi-messagesProposals.xml



2) For reference, the second link points to the current DataMINX schema
which adopts more of a JSDL/HPC file staging approach (using multiple
src and target URIs rather than DEPRs).
http://code.google.com/p/dtsproject/source/browse/trunk/dts-jaxb/src/mai
n/resources/minx-dts.xsd

An example at:
http://code.google.com/p/dtsproject/source/browse/trunk/dts-jaxb/src/mai
n/resources/MINX-DataTransferRequest-Example.xml


To recap, in DataMinx we need to:
a) Define a transfer consisting of multiple [src-sink] declarations in a
single request document where the data may reside on different hosts.
b) Define all messages in a WS-I document-literal-wrapped format (since
we are using a RESTtful style WS and our messages are routed via JMS
queues to appropriate worker nodes who will perform the transfer). Not
sure how this would fit with the WSRF factory-instance approach?

dave.



-----Original Message-----
From: ogsa-dmi-wg-bounces@ogf.org [mailto:ogsa-dmi-wg-bounces@ogf.org]
On Behalf Of Mario Antonioletti
Sent: 15 July 2009 16:24
To: OGSA-DMI
Subject: [ogsa-dmi-wg] Rescheduled Call for this Friday.


Hi,
   First of all my apologies but I completely forgot that we were
scheduled to have a call last Monday - it somehow fell off my outlook
calendar, still no excuse.

We will now have the call this Friday at 11am UK time (GMT+1) which
makes it 8pm in Australia. Details as below:

Agenda
======

- Agenda bashing
- Progress update
  - MAA determine if proposed changes can be passed off as errata.
  - AL determine if existing spec can transfer multiple directories
    living on the same host.
  - SM WSRF OGSA-DMI rendering.
  - Other stuff ...
- Planning

Please let me know if anything else should be added to the list.

Call details
============
               Participant access code: 23057332 then #

              Primary dial-in number: 0870 2407821
                or if dialling internationally +44 2078193600
              Or local access alternatives:
               USA West Coast 4089616553
               USA East Coast 7183541169
               Germany (0)6950070811
               Finland (0)969379595
               Australia 0282239343

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/
|
+-----------------------------------------------------------------------
+
--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.

--
 ogsa-dmi-wg mailing list
 ogsa-dmi-wg@ogf.org
 http://www.ogf.org/mailman/listinfo/ogsa-dmi-wg
--
Scanned by iCritical.