Further change tracked revsion to the changes Andrew made in the call. Ignoring white space alterations: * Extra arrow on the action state change diagram for Not Started to Active change. * Revision to the execution action with the 'Execution State' being reflected in the top-level state diagram. * Moving the authorisation issue to the security section. Discussion will continue from section 3.3 on this Thursday's call. Steven -- ---------------------------------------------------------------- Dr Steven Newhouse Tel:+44 (0)2380 598789 Deputy Director, Open Middleware Infrastructure Institute (OMII) Suite 6005, Faraday Building (B21), Highfield Campus, Southampton University, Highfield, Southampton, SO17 1BJ, UK
I probably can't make the call today either so here are some comments wrt v5. Hope they are of use. - 3.1 CreateActivityFromJSDL: There should also be a fault for 'Not a JSDL 1.0 document' to cover the case of a document being well formed but not JSDL 1.0. 3.2 GetActivityStatus The definition of the fault feels like dictating implementation too much. If, say, a list of 100 activities is passed in and only 1 does not exist why shouldn't I be able to return a document with any gathered information including 'unknown activity' for just that activity? So I'd rather have no fault here and extend the definition of the values returned in the output document. The definition of state 'Other' (p7) says that it is an 'unknown' state but this is not correct. 'Unknown' and 'Other' should be separate with 'Other' being an extensibility point. And it should be possible to return additional information in that case. So the structure defined should be ... <OverallStatus state="(enumerated state)" otherstate="(this container specific states)"?) ... and otherstate is only defined when state=Other Andreas Steven Newhouse wrote:
Further change tracked revsion to the changes Andrew made in the call.
Ignoring white space alterations: * Extra arrow on the action state change diagram for Not Started to Active change. * Revision to the execution action with the 'Execution State' being reflected in the top-level state diagram. * Moving the authorisation issue to the security section.
Discussion will continue from section 3.3 on this Thursday's call.
Steven
I probably can't make the call today either so here are some comments wrt v5. Hope they are of use. - 3.1 CreateActivityFromJSDL: There should also be a fault for 'Not a JSDL 1.0 document' to cover the case of a document being well formed but not JSDL 1.0. 3.2 GetActivityStatus The definition of the fault feels like dictating implementation too much. If, say, a list of 100 activities is passed in and only 1 does not exist why shouldn't I be able to return a document with any gathered information including 'unknown activity' for just that activity? So I'd rather have no fault here and extend the definition of the values returned in the output document. The definition of state 'Other' (p7) says that it is an 'unknown' state but this is not correct. 'Unknown' and 'Other' should be separate with 'Other' being an extensibility point. And it should be possible to return additional information in that case. So the structure defined should be ... <OverallStatus state="(enumerated state)" otherstate="(this container specific states)"?) ... and otherstate is only defined when state=Other Andreas Steven Newhouse wrote:
Further change tracked revsion to the changes Andrew made in the call.
Ignoring white space alterations: * Extra arrow on the action state change diagram for Not Started to Active change. * Revision to the execution action with the 'Execution State' being reflected in the top-level state diagram. * Moving the authorisation issue to the security section.
Discussion will continue from section 3.3 on this Thursday's call.
Steven
First off - did I miss the posting about the call today? Some comments inline below: Andreas Savva wrote:
- 3.1 CreateActivityFromJSDL: There should also be a fault for 'Not a JSDL 1.0 document' to cover the case of a document being well formed but not JSDL 1.0.
As there is likly to be more than one version of JSDL. Perhapse a better statment is "Does not conform to known JSDL format". We then need some way to say which JSDL formats a service can handle.
3.2 GetActivityStatus The definition of the fault feels like dictating implementation too much. If, say, a list of 100 activities is passed in and only 1 does not exist why shouldn't I be able to return a document with any gathered information including 'unknown activity' for just that activity? So I'd rather have no fault here and extend the definition of the values returned in the output document.
Agreed.
The definition of state 'Other' (p7) says that it is an 'unknown' state but this is not correct. 'Unknown' and 'Other' should be separate with 'Other' being an extensibility point. And it should be possible to return additional information in that case. So the structure defined should be ... <OverallStatus state="(enumerated state)" otherstate="(this container specific states)"?) ... and otherstate is only defined when state=Other
Could this get horribly complex? Just a worry. steve..
Andreas
Steven Newhouse wrote:
Further change tracked revsion to the changes Andrew made in the call.
Ignoring white space alterations: * Extra arrow on the action state change diagram for Not Started to Active change. * Revision to the execution action with the 'Execution State' being reflected in the top-level state diagram. * Moving the authorisation issue to the security section.
Discussion will continue from section 3.3 on this Thursday's call.
Steven
-- ------------------------------------------------------------------------ Dr A. Stephen McGough http://www.doc.ic.ac.uk/~asm ------------------------------------------------------------------------ Technical Coordinator, London e-Science Centre, Imperial College London, Department of Computing, 180 Queen's Gate, London SW7 2BZ, UK tel: +44 (0)207-594-8409 fax: +44 (0)207-581-8024 ------------------------------------------------------------------------ Assistant Warden, West Wing, Beit Hall, Imperial College, Prince Consort Road, London, SW7 2BB tel: +44 (0)207-594-9910 ------------------------------------------------------------------------
First off - did I miss the posting about the call today?
No... here it is Toll-free dial-in: 1-877-422-0036 Toll/International dial-in: 1-314-655-1412 Tie-line dial-in: 422-0036 Participant passcode: 496684 Time: 10 AM eastern 7 AM Pacific 3 PM UK 4 PM Europe Duration: 1 hour Glance will provided at ogsa.glance.net Agenda: 0. Agenda Bashing 1. Continue document discussion & review 2. AOB -- ---------------------------------------------------------------- Dr Steven Newhouse Tel:+44 (0)2380 598789 Deputy Director, Open Middleware Infrastructure Institute (OMII) Suite 6005, Faraday Building (B21), Highfield Campus, Southampton University, Highfield, Southampton, SO17 1BJ, UK
Toll-free dial-in: 1-877-422-0036 Toll/International dial-in: 1-314-655-1412 Tie-line dial-in: 422-0036 Participant passcode: 496684 Time: 10 AM eastern 7 AM Pacific 3 PM UK 4 PM Europe Duration: 1 hour Glance will provided at ogsa.glance.net Agenda: 0. Agenda Bashing 1. Review text changes from previous call: * Section 3.2: Replacement of a general all encompassing fault with 'NotKnown' status that can be used within the ActivityStatus document to identify activities that are not known. * Section 4: Text for exposing container acitivty. * Section 5: Text for security considerations. 2. Discussion Points * Section 3.2: Use of the CIM state enumerations. * Sections 3.5, 3.5 & 3.6. Having 3 management operations in the BES specification until generic OGSA management structure defined? * Section 3.7: When returning the JSDLDocuments do we place the WS-Name in the JSDLDocument or encapsulate it with the WS-Name in a new element? 3. BES Agenda discussion for the OGSA F2F Monday morning (Aug. 15) 4. AOB Discussion relates to v6 of the document circulated last week. Regards, Steven -- ---------------------------------------------------------------- Dr Steven Newhouse Tel:+44 (0)2380 598789 Deputy Director, Open Middleware Infrastructure Institute (OMII) Suite 6005, Faraday Building (B21), Highfield Campus, Southampton University, Highfield, Southampton, SO17 1BJ, UK
Toll-free dial-in: 1-877-422-0036 Toll/International dial-in: 1-314-655-1412 Tie-line dial-in: 422-0036 Participant passcode: 496684 Time: 10 AM eastern 7 AM Pacific 3 PM UK 4 PM Europe Duration: 1 hour Glance will provided at ogsa.glance.net Agenda: 0. Agenda Bashing 1. BES Agenda discussion for the OGSA F2F Monday 10.30-15.00 (Aug. 15) * Review of current draft & discussion [60 mins] * Discussion about renderings [60 + 60 mins] * Discussion about implementations [30 mins] 2. Review major text changes from previous call: * Section 3.2: Adoption of CIM state names in BES state model. * Section 3.3: ControlActivities - Operation to signal groups of activities. * Section 5: Management. 3. Discussion Points * Section 3.6: When returning the JSDLDocuments do we place the WS-Name in the JSDLDocument or encapsulate it with the WS-Name in a new element? * Events: What do we want to expose for subscription/triggering of events? 4. AOB Discussion relates to v7 of the document (attached). Regards, Steven -- ---------------------------------------------------------------- Dr Steven Newhouse Tel:+44 (0)2380 598789 Deputy Director, Open Middleware Infrastructure Institute (OMII) Suite 6005, Faraday Building (B21), Highfield Campus, Southampton University, Highfield, Southampton, SO17 1BJ, UK
Toll-free dial-in: 1-877-422-0036 Toll/International dial-in: 1-314-655-1412 Tie-line dial-in: 422-0036 Participant passcode: 496684 Time: 10 AM eastern 7 AM Pacific 3 PM UK 4 PM Europe Duration: 1 hour Glance will provided at ogsa.glance.net Agenda: 0. Agenda Bashing 1. Confirm BES Agenda for the OGSA F2F 2. Review major text changes from previous call: * Section 3.3: RequestActivityStateChanges * Section 3.6: GetActivityJSDLDocuments 3. Discussion Points * Section 4 : Subscribing to Generated Events 4. AOB Discussion relates to v8 of the document (attached) reflecting the changes from the previous call. Notes from that call are retained in the text. Regards, Steven -- ---------------------------------------------------------------- Dr Steven Newhouse Tel:+44 (0)2380 598789 Deputy Director, Open Middleware Infrastructure Institute (OMII) Suite 6005, Faraday Building (B21), Highfield Campus, Southampton University, Highfield, Southampton, SO17 1BJ, UK
participants (3)
-
A S McGough -
Andreas Savva -
Steven Newhouse