[plcs-tog] TOG meeting TODAY

["Rutland, Phil" <ils-dm@a.dii.mod.uk>]

Title: RE: [plcs-tog] TOG meeting TODAY

Tim,

 

Since Tor Arne was unavailable for the TOG meeting I had assumed that the telecon would not go ahead.

 

On the subject of DEX3 (something for the TOG meeting in Amsterdam to debate) I understand that a DEX (in it's simplest terms) contains the definition of information required for a particular exchange. The exchange file is the actual (as realised) exchange.

 

DEX3 contains the information required to define a single Task Specification. The exchange file can contain any number of DEX3s, thus allow one or more Task Specifications to be exchanged.  Since we had initally constrained DEX3 to be a single Task Specification, the proposed Task List DEX (Capability?) was our first stab at addressing the issue of how to exchange a 'related' set of Task Specifications.

 

I hope this helps (or even makes sense!)

 

Phil Rutland

-----Original Message-----
From: Tim Turner [mailto:tjt@lsc.co.uk]
Sent: 14 September 2005 15:40
To: 'Rutland, Phil'; 'tai@sfk.mil.no'
Cc: plcs-tog@lists.oasis-open.org
Subject: RE: [plcs-tog] TOG meeting TODAY

I am confused about your statement Phil,

either Dex3 covers a set of tasks or a single one, which is it?

Is there not a way to keep the tasks and the list together within Dex3 as opposed to separating each item? The current scope may be useful for descrete task exhcanges, but will hinder exchange of a library of tasks.

I would have expected to see Dex3 to cover the larger case, with allowed subsets (conf classes within a Dex) to exchange a single task, an index/list identifying task specifications, a set of tasks, or all 4.

regards,
Tim

-----Original Message-----
From: Rutland, Phil [mailto:ils-dm@a.dii.mod.uk]
Sent: 14 September 2005 07:21
To: 'tai@sfk.mil.no'
Cc: plcs-tog@lists.oasis-open.org
Subject: [plcs-tog] TOG meeting TODAY

Tor Arne,

Sorry to hear about your difficulties. Being a Naval type you should be at
home with all that water!

My view on DEX3 is that we have developed the DEX for a single Task
Specification and that the need for a set of tasks (related or not) is
covered by the exchange file that will contain a single message and one or
more Task Specifications. We are also proposing another DEX (or Capability)
to exchange the relationships between a list of tasks.

Phil Rutland

-----Original Message-----
From: tai@sfk.mil.no [mailto:tai@sfk.mil.no]
Sent: 14 September 2005 11:44
To: plcs-tog@lists.oasis-open.org
Subject: [plcs-tog] TOG meeting TODAY

My family and I are OK, but there have been a landslide a few hundred meters
from my home.
130 + evacuated,
1 dead and 9 in hospital, including several kids who are friends of my boys.
Several houses effected.
Roads closed.
Rescue workers are moved out

152 mm rain in less than 24 hours.
The lake around my house rose 950 mm since 1500 yesterday.

SO IN SHORT:

I do not feel up to leading the TOG-meeting today.
I have secured the material goods, but need to be there for my family.

The focus for the TOG right now:

1.      The scope of DEX 3: should it cover just ONE task or a set of tasks
including task sequence.
2       Set agenda for the TOG/TC meeting in Amsterdam.

I would like inputs on both issues.

Best regards

Tor Arne Irgens

DISCLAIMER: ***SECURITY LABEL: NOT PROTECTIVELY MARKED***   The information in this message is confidential and may be legally privileged. It is intended solely for the addressee.  Access to this message by anyone else is unauthorised.  If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful.  Please immediately contact the sender if you have received this message in error. This e-mail originates from LSC Group. Registered in England & Wales No 2275471 Registered Office: Devonport Royal Dockyard, Devonport, Plymouth, PL1 4SG