INFOD Current Actions ===================== This is a list of current actions. Each action has a serial number, once it is closed it is moved to a companion document of closed actions. ============================================================================== ============================================================================== 5 Go over list of questions, clarifications addressed for chapter 1 in http://www-unix.gridforum.org/mail_archive/infod-wg/2005/05/msg00001.html (ch 2 questions have an open item for them) Page 4, para 4: "a publication specifies..." the first part is fine but then you say it "makes available". I don't think a publication should *do* anything. - Date: 1 Jul 2005 - Owner: Dieter - Target date: 4 Aug 2005 6 Go over list of questions, clarifications addressed for chapter 2 in http://www-unix.gridforum.org/mail_archive/infod-wg/2005/05/msg00001.html (ch 1 questions have an open item for them) - Date: 1 Jul 2005 - Owner: Dieter - Target 4 Aug 2005 9 Update SensorNet scenario with operations as per Chicago F2F June 05 Include scenario to determine when consumer, consumption needed and decide whether definition of equivalent of association for consumption is needed - Date: 1 Jul 2005 - Owner: Arjun - Target date: 15 Nov 2005 10 Update R-GMA scenario with operations as per Chicago F2F June 05 - Date: 1 Jul 2005 - Owner: Steve F - Target date: 15 Nov 2005 20 Ensure that existing glossary includes the following terms, and that they are defined in specs. - From http://www-unix.gridforum.org/mail_archive/infod-wg/2005/01/msg00006.html - Terms for INFOD to clarify, define: - Publisher, Consumer, Subscriber, Broker , Propagator (INFOD has no producer) - Continuous query Pushing, Polling and Pull Action Event correlation of content and creation Type System Language Registry History and latest queries Mediation Primary and Secondary producers Topics Profiles Demand Driven Publishing Targeted Publishing Definition On Demand Publishing Definition On Demand Propagation Definition - vocabulary, identity, The event taxonomoy should be explained in the glossary - Date: 1 Jul 2005 - Owner: Vijay - target date: 10 Sep 2005 21 Update the charter, to reflect new schedule The text has been simplified - Date: 1 Jul 2005 - Owners: Susan - target date: 27 Oct 2005 22 Produce a plan for at least two implementations - Date: 1 Jul 2005 - Owner: - target date: GGF16 This may be hard to do - Arjun 23 Provide response to document proposed by Vijay on infod suggested service modifications: - publication regenerate - some services can regenerate some cannot and need to cache - aspects of analyst role - lifetime management - and new point - Clarification: A publication can be viewed as a reaction to a query however the format of the published material may need to be considered or specified separately See https://forge.gridforum.org/projects/infod-wg/document/Info-D_Suggested_Service_Modifications/ for Vijay paper and see http://www-unix.gridforum.org/mail_archive/infod-wg/2004/07/msg00001.html for issue description - Date: 1 Jul 2005 - Owner: Cecile - Target date: 15 Sep 2005 24 Document in specs summary of issues raised in Vijay's original append - and resolutions - and validate still accurate with existing infod specs: - declarative vs descriptive interfaces - type of data/temporal/meta events defined in infod - consumption See http://www-unix.gridforum.org/mail_archive/infod-wg/2004/08/msg00004.html and summarize resolutions as per: - http://www-unix.gridforum.org/mail_archive/infod-wg/2004/08/msg00005.html http://www-unix.gridforum.org/mail_archive/infod-wg/2004/08/msg00006.html http://www-unix.gridforum.org/mail_archive/infod-wg/2004/08/msg00007.html Is this still relevant. Cecile will ask Vijay to read it. - Date: 1 Jul 2005 - Owner: Cecile, Vijay - Target date: 15 Sep 2005 26 We will need to update spec to use WS-RF resource properties and operators. But our query semantics might be different than those of WSRF; so we'll have to be careful about how we structure the registry to allow it. Topics about Resource Management (naming, versioning and change management of resources) is not part of the INFOD scope yet some specific components are expected by the INFOD model, in particular: time of a change, a reference to an identity to record responsibility for the change, time when a version becomes valid, time when a version expires, a schedule when this version is valid, etc. Document current positioning wrt to wsrf (a few papers were summarizing this already) it might mean that we end up trying to build on top of or align with WS-BaseNotification, because it is part of the OGSA Basic Profile Document current positioning wrt to wsn (ref: http://www-unix.gridforum.org/mail_archive/infod-wg/2005/05/msg00003.html) WS-ResourceLifetime is a specification that allows us to destroy resources. Does this have any sort of versioning? Not obviously - this could be used for planned updates? There is no scheduling component to this specification - it is about handling instances, not any evolutionary aspects of a service. We will still have to have our own creation mechanisms. Now just needs writing up However we now think that WSRF should be optional - but still needs writing up. Needs comments on section 3 - Date: 1 Jul 2005 - Owners: Abdeslem, Cecile - target date: 29 Sep 2005 28 Produce interaction diagram to guide readers in understanding general usage - Date: 21 Jul 2005 - Owner: Chris - target date: 27 Oct 2005 Do it for the cars use case 29 Write up consumer service requirement - is this addressed by POBOX? - Date: 21 Jul 2005 - Owner: Steve F. - Target date: 15 Nov 2005 31 Define late binding and determine where late binding is supported Expanding recipient list from logical EPR? - Date: 21 Jul 2005 - Owner: Shailendra - Target date: 11 Aug 2005 32 Define non-events - are they deadline related? - Date: 21 Jul 2005 - Owner: Cecile and Dieter - Target date: 20 Oct 2005 Dieter will produce a note - but it won't go anywhere 35 Break the spec into multiple logical documents defining different levels of INFOD OGSA profiles mandate base WSN. To be compliant we need to refactor around base notifications now and provide INFOD services as an extension to WS-BaseNotify?    http://www-unix.gridforum.org/mail_archive/infod-wg/2004/08/msg00010.html http://www-unix.gridforum.org/mail_archive/infod-wg/2004/12/msg00000.html Questions to address include: How does WS-Eventing fit in? What's the difference between a disseminator and a WSN broker? publication and WSN topic? Vocabulary and WSN filter? Can WSN send message directly to a consumer by name? Publications are defined by topics in WSN, how does that differ from INFOD mechanisms for controlling publications through vocabularies? One proposal was to split: o Information Dissemination from publishers to consumers, allowing subscribers to subscribe on behalf of 3rd party consumers o Information Dissemination with one or more disseminators, but without propagation requirements between disseminators (disseminators do not talk to each other yet provide decoupling of publishers/subscribers/consumers interaction) o Information Dissemination with one or more disseminators and with possible propagation between disseminators (delivery of the "intelligent cloud" Another proposal from F2F was to look at the list of Requirements, and pick a few that are doable short term, and use it to drive the factoring from simple to more complex scenarios - and use that work to see how the 2 relate to each other (ie common short term items from both) Amount of information points to two documents (not three as initially thought). First document with base functionality. Rest in second document. Moving GetMData description to base document. - Date: 1 Jul 2005 - Owner: Cecile, Susan, Abdeslem - Target date: post GGF15 36 Look at WSN to see how they have cleaned up soap/web-services header contents description - Date: 25 Aug 2005 - Owner: Arjun - Target date: 27 Oct 2005 40 Discusss with Dieter the vocaulary issuse of 20 and 21 and 28 - Date 8 Sep 2005 - Owner: Vijay - Target: 29 Sep 2005 41 Fix section 2 of the specification and make it consistent with section 3.8.1 - Date 3 Oct 2005 - Owner: Dieter - Target: 20 Oct 2005 42 Remove body from the the message header section and add comments for every attribute - Date 3 Oct 2005 - Owner: Shailendra - Target: 20 Oct 2005 43 Describe the two approaches: (1) Re-pacakaging a message at each hop in a new header (2) Removing the header and adding a new appropriate message header after transformation - Date 3 Oct 2005 - Owner: Shailendra - Target: 20 Oct 2005 44 Put mandatory properties together in the message structure - Date 3 Oct 2005 - Owner: Shailendra - Target: 20 Oct 2005 45 Describe the behavior of DestinationEPRs and MessageIds in an INFOD system - Date 3 Oct 2005 - Owner: Shailendra - Target: 20 Oct 2005 46 Justify message structure and map to the patterns. This should resolve issue 2 - Date 3 Oct 2005 - Owner: Shailendra and Vijay - Target: 31 Oct 2005 48 Define sequence number,operationalCharacteristics more clearly - Date 3 Oct 2005 - Owner: Shailendra - Target: 31 Oct 2005 49 Reconsider the manifest name and to give it a name that is consistent with its content - Date 3 Oct 2005 - Owner: Shailendra - Target: 31 Oct 2005 50 Explain the need for incorporating information in the INFOD messages to deal with the integration of SOAP and asynchronous messaging - Date 3 Oct 2005 - Owner: Shailendra and Vijay - Target: 31 Oct 2005 51 Add a subscriber id to the create subscription interface - Date 3 Oct 2005 - Owner: Abdeslem - Target: 31 Oct 2005 52 Explore the use of the subscription interface with the registry manager to notify publishers and consumers of changes to the contents of the registry manager (e.g., changes to subscriptions, changes to publishers, changes to consumers) - in other words explore the registry manager acting as a publisher This should resolve issue 7 - Date 3 Oct 2005 - Owner: Vijay - Target: 31 Oct 2005 53 Explore the message layout for create subscription, etc ... - Date 3 Oct 2005 - Owner: Vijay and Shailendra - Target: 31 Oct 2005 55 Create/revise use case in accordance with new template: ChS (Chemsecure) - Date 3 Oct 2005 - Owner: Ronny - Target: 15 Nov 2005 56 Create/revise use case in accordance with new template: Media - Date 3 Oct 2005 - Owner: Stephen D - Target: 15 Nov 2005 57 Create/revise use case in accordance with new template: Cars - Date 3 Oct 2005 - Owner: Dieter - Target: 15 Nov 2005 58 Create/revise use case in accordance with new template: Sensor - Date 3 Oct 2005 - Owner: Arjun - Target: 15 Nov 2005 59 Create/revise use case in accordance with new template: 3rd party delivery - Date 3 Oct 2005 - Owner: Susan - Target: 15 Nov 2005 60 Assemble the use case and pattern document Include mention of the desirability of a bank balance notification use case and an e-mail filter use case - Date 3 Oct 2005 - Owner: Susan - Target: 15 Dec 2005 61