INFOD Closed Actions ==================== 1 Add reference to appropriate appendix, or description for vocabulary, identity management, etc. in Page 5, para 2: we need references or brief explanation of vocabulary, identity management and principal as they all have a meaning which is peculiar to their context. This is now in the specification - Date: 1 Jul 2005 - Owner: Dieter - target date: 31 Jul 2005 - Closed 8 Sep 2005 2 Add Arjun to list of writers of specs... - Date: 1 Jul 2005 - Owner: Cecile - Closed 1 Sep 2005 3 After much discussion about using WSDM to stop/start our services, we decide that we agree that starting/stopping our service is out of scope. - Date: 1 Jul 2005 - Owner: Dieter - Closed 1 Sep 2005 4 Figure 1 is confusing. Steve to come up with better diagram. http://www-unix.gridforum.org/mail_archive/infod-wg/2005/05/msg00003.html - Date: 1 Jul 2005 - Owner: Steve - Closed 1 Sep 2005 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. CONSIDERED TO BE NO LONGER RELEVANT - Date: 1 Jul 2005 - Owner: Dieter - Closed: 20 Oct 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) CONSIDERED TO BE NO LONGER RELEVANT - Date: 1 Jul 2005 - Owner: Dieter - Target 4 Aug 2005 - Closed: 20 Oct 2005 7 Go over list of questions, issues raised in May 05 F2F: http://www-unix.gridforum.org/mail_archive/infod-wg/2005/06/msg00001.html - Date: 1 Jul 2005 - Owner: Chris - Target date: 21 Jul 2005 8 Map the original infod registry object components back to operation parms newly defined to ensure no loss of function from Chicago June 05 F2f discussion Now in specification - Date: 1 Jul 2005 - Owner: Dieter, Cecile - target date: 31 Jul 2005 - Closed 8 Sep 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 DONE - it will be reviewed further as part of action 58 - Date: 1 Jul 2005 - Owner: Arjun - Target date: 15 Nov 2005 - Closed 10 Nov 2005 11 Write homeland security use-case Are we still doing this ?! It was decided that this was no longer useful and was covered by the SensorNet Use Case - Date: 1 Jul 2005 - Owner: Abdeslem - Closed 14 Jul 2005 12 Consider bank balance notification use case It was decided to add a short note in the use case document mentioning the desitability of such a Use Case - Date: 1 Jul 2005 - Owner: Dieter - Closed: 13 Oct 2005 13 Consider e-mail filter use case Sounds like a POBox application It was decided to add a short note in the use case document mentioning the desitability of such a Use Case - Date: 1 Jul 2005 - Owner: Cecile, Shailendra - Target date: 15 Sep 2005 - Closed: 13 Oct 2005 14 Write ERP use case Are we still doing this ?! It was decided that this was no longer useful - Date: 1 Jul 2005 - Owner: Dieter - Target date: - Closed 14 Jul 2005 16 Connect with Medical Screening Use Case: Here is the reference: One researcher doing 'classification technology' is Ed Chang, he calls the technology PBIR (Perception-based Image Retrieval). There are other widely used technologies such as 'Recommendation Engines' known from Business Intelligence. http://www-unix.gridforum.org/mail_archive/infod-wg/2004/09/msg00002.html Are we still doing this ? We decided not to - Date: 1 Jul 2005 - Owner: - target date: - Closed 14 Jul 2005 15 Create new SensorNet scenario to determine when consumer, consumption needed and decide whether definition of equivalent of association for consumption is needed This will be incoporated into action 9 - Date: 1 Jul 2005 - Owners: Dieter, Arjun - Target date: ?? - Closed 14 Jul 2005 17 Include Bank and Sensor scenario to do from infod Mailing list http://www-unix.gridforum.org/mail_archive/infod-wg/2004/07/msg00001.html Are we still doing this ? It was decided not to do this. So the action is DROPPED - Date: 1 Jul 2005 - Owner: Steve F - target date: - Closed 4 Aug 2005 18 Incorporate Chicago 05 F2F updates This is coverered by actions 5 and 6 - Date: 1 Jul 2005 - Owner: Cecile - Target date: end of 31 Jul 2005 - Closed 14 Jul 2005 19 John Davey's suggestion. June 05. Cecile to simplify specs as per suggestions. This is coverered by actions 5 and 6 - Date: 1 Jul 2005 - Owner: Cecile - Target date: end of Jul - Closed 14 Jul 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 - Closed: 20 Oct 2005 21 Update the charter, to reflect new schedule The text has been simplified. It now addresses only up to GGF16. - Date: 1 Jul 2005 - Owners: Susan - target date: 27 Oct 2005 - Closed: 12 Jan 2006 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 NO LONGER RELEVANT - Date: 1 Jul 2005 - Owner: Cecile - Target date: 15 Sep 2005 - Closed: 20 Oct 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. Reading has been done. This is now addressed in the spec. - Date: 1 Jul 2005 - Owner: Cecile, Vijay - Target date: 3 Nov 2005 - Closed 17 Nov 2005 25 Define relationship between Infod AND DAIS - document current positioning - resolve lifetime issues of INFOD objects vs DAIS sessions - 3rd party delivery support - This should probably go into a use case This will be addressed by the use case required by action 59 on 3rd party delivery. - Date: 1 Jul 2005 - Owners: Susan - target date: 31 Aug 2005 - Closed: 13 Oct 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 Remove section 3.9 and don't expose yet as WS resources - Date: 1 Jul 2005 - Owners: Abdeslem, Cecile - Target date: 27 Oct 2005 - Closed: 10 Nov 2005 27 Understand action 17! In his absence it was decided to transfer 17 to Steve F! - Date: 14 Jul 2005 - Owners: Steve F - Target date: 21 Jul 2005 - Closed 21 Jul 2005 28 Produce interaction diagram to guide readers in understanding general usage The diagram is done. There was some discussion about what should happen to this rather large diagram. It would be nice to include in the cars use case though it is rather large. If it is simplified it may lose its value. Steve will take a look. Will split it into 3 parts. The 3 diagrams will go into the use case doc - Date: 21 Jul 2005 - Owner: Chris - target date: 19 Jan 2006 - closed: 19 Jan 2006 30 Add pattern of many publishers publishing using the same PublicationType via association We may just explain this in the spec. This is now in the spec: action COMPLETE - Date: 21 Jul 2005 - Owner: Cecile - Target date: - Closed: 4 Aug 2005 32 Define non-events - are they deadline related? Dieter has produced the following text. It does not appear to fit into any of our current documents: INFOD uses the terms states, events, and messages. Messages report about events; events are the consequence of state changes. State changes require a temporal data model; i.e., the ability to compare a state with previous states. By definition an event has happened when an expression or constraint becomes true after a state transition. This model represents an extension of the normalization model of temporal databases. Temporal database technology also looks at the duration of an expression remaining true in the presence of state changes. If the length for a condition to remain true should be limited, one expects two state changes (events), one when entering a state where the condition becomes true and one entering a state where the condition is not true anymore. If the second state change (event) does not happen within a given time limit, it is important to create awareness of this fact by creating an alternative events. The alternative event is often perceived as a non-event; it got created because the expected event did not happen in time; or using another view: a deadline has been missed. - Date: 21 Jul 2005 - Owner: Cecile and Dieter - Target date: 20 Oct 2005 - Closed 20 Oct 2005 33 Review what's in the specification on vocabularies and give feedback Which version - when should this be done? Now - Date: 21 Jul 2005 - Owner: Steve F - Target date:11 Aug 2005 - Closed 8 Sep 2005 34 Review what's in the specification about disseminators and give feedback. See issues 13 and 17 Which version - when should this be done? Not yet. This is no longer considered a useful action - Date: 21 Jul 2005 - Owner: Abdeslem and Susan - Target date: - Closed: 13 Oct 2005 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 - Closed: 20 Oct 2005 36 Look at WSN to see how they have cleaned up soap/web-services header contents description. Arjun thinks that we should follow this approach. See action 89. - Date: 25 Aug 2005 - Owner: Arjun - Target date: 3 Jan 2006 - Closed: 12 Jan 2006 37 See how to divide Reg Manager interface into 2 documents. Do we need WSDL Inheritance? It was decided to avoid the latest WSDL. "Copy and paste" inheritance can be done as a profile. - Date: 25 Aug 2005 - Owner: Steven - Target date: - Closed: 13 Oct 2005 38 Consider issue 2 Covered by action 46 - Date 8 Sep 2005 - Owner: ALL - Target: 22 Sep 2005 - Closed: 13 Oct 2005 39 Consider issue 7 Covered by action 52 - Date 8 Sep 2005 - Owner: ALL - Target: 29 Sep 2005 - Closed: 13 Oct 2005 40 Discusss with Dieter the vocabulary issuse of 20 and 21 and 28 - Date 8 Sep 2005 - Owner: Vijay - Target: 10 Nov 2005 - Closed 17 Nov 2005 41 Fix section 2 of the specification and make it consistent with section 3.8.1 - Date 3 Oct 2005 - Owner: Dieter - Target: 10 Nov 2005 - Closed 17 Nov 2005 42 Remove body from the the message header section and add comments for every attribute - Date 3 Oct 2005 - Owner: Shailendra, Cecile - Target: 20 Oct 2005 - Closed 17 Nov 2005 44 Put mandatory properties together in the message structure - Date 3 Oct 2005 - Owner: Shailendra, Cecile - Target: 20 Oct 2005 - Closed 17 Nov 2005 45 Describe the behavior of DestinationEPRs and MessageIds in an INFOD system The following should be incorporated by Cecile into the spec which is currently locked: MessageIds are universaly unique ids and are created at the time of publish. Messages can be correlated using the correlation id. The uniqueness of MessageIds is very useful in P2P protocols and message recovery after instance failure. - Date 3 Oct 2005 - Owner: Shailendra, Cecile - Target: 20 Oct 2005 - Closed 8 Dec 2005 46 Justify message structure and map to the patterns. This should resolve issue 2 In addition to properties supported by most messaging systems such as JMS and CORBA that treat messages as lightweight entities consisting of a header and a body, INFOD provides additional features to enable message tracking and additional routing capabilities. For example, the message ids allow the messages to be uniquely attributed to the publishers and uniquely identify its dissemination path. The header contains fields used for message routing and identification; the body contains the application data being sent. The semantics of the header elements are as follows: - Id \226 Uniquely identifies a message and attributes it to a verifiable publisher. - Length \226 The length of the message, including manifest and payload. - Type \226 Uniquely identifies a message type, for xml message types this refers to xsd format of the message. - Correlation Id \226 Uniquely identifies a group of messages. For multiple nested groupings multiple correlation ids may be associated with the message. - Priority \226 A sender provided priority associated with the message. - Retry \226 The number of times the disseminator will retry to deliver this message. The sender specifies this parameter for enactment by the disseminator. - SenderEPR \226 End point reference to enable any routing node to be able to interact with the sender. - DestinationEPR \226 The end destination EPR where the message routing needs to be terminated. - OriginalId \226 A message may have resulted by split, merge or join of different messages, the original id points to the originating message. - SequenceNo \226 For ordered delivery of message in a correlation (as specified by CorrelationId) the sequence number specifies the order of consumption of message. This number does not mean that sequence will be observed at each stage of routing, but is required to be enforced at the point of consumption. - Signature \226 The encryption key for the message. - EncryptionAlgorithm \226 The name of the encryption algorithm. - Characterset \226 The character set for the message. - Form \226 single or multi-byte character set - OpChar \226 operational characteristics. - userProperty \226 A set of user defined name value pairs. - Flags \226 A set of property attributes for message routing. Patterns for dissemination Following are the important properties of various message deliveries - Ordered sequence of message delivery  Create a correlationId to identify a sequence.  Associate an incremental sequenceNo with each message.  End the sequence by creating new correlations. - Transactional message delivery  Create a correlationid  Set routing flags for transactional and guaranteed delivery.  Set retry to allow recovery while routing  Create nested correlationid at each stage of propagation in the dissemination network.  Set acknowledgement flag on at each step of routing. - Broadcast of messages  SetDestinationEPR to NULL  Retry will be ignored by disseminator.  Priority may be ignored by disseminator. - Date 3 Oct 2005 - Owner: Shailendra and Vijay - Target: 28 Dec 2005 - Closed: 12 Jan 2006 47 Give feedback on Shailendra and Vijay's work. This is no longer considered useful - Date 3 Oct 2005 - Owner: Arjun - Target: 31 Oct 2005 - Closed: 13 Oct 2005 49 Reconsider the manifest name and to give it a name that is consistent with its content. Webster dictionary defines Manifest as ?To be the evidence off?, The content of the manifest reveals routing information of a message. Steve F is unhappy with this and so takes the action over The agreed word is "Trail". The change needs to go into the Spec then it will be DONE Changes consist of 'Manifest' will be changed to 'Trail' in 3.9.1, typo in message: 'body' should be actually 'trail' and finally trail should be defined as an array. - Date 3 Oct 2005 - Owner: Cecile - Target: 10 Nov 2005 - Closed: 12 Jan 2006 51 Add a subscriber id to the create subscription interface - Date 3 Oct 2005 - Owner: Dieter - Target: 10 Nov 2005 - Closed: 8 Dec 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: Shailendra - Target: 3 Jan 2006 53 Explore the message layout for create subscription, etc ... - Date 3 Oct 2005 - Owner: Vijay and Shailendra - Target: 31 Oct 2005 - Closed: 17 Nov 2005 ??? 54 Revise and place Use Case template on GGF WebSite - Date 3 Oct 2005 - Owner: Steve F - Target: 10 Oct 2005 - Closed: 13 Oct 2005 55 Create/revise use case in accordance with new template: ChS (Chemsecure) This is now included in action 58 - Date 3 Oct 2005 - Owner: Ronny - Target: 29 Nov 2005 - Closed 15 Dec 2005 56 Create/revise use case in accordance with new template: Media Remove non-base specification items from each use case Eliminate colo(u)r in pictures Use Poseiden UML tool to describe the use case Ensure the use cases element names, parameters and operations match the specification Ensure the figures and table numbers include the section number - Date 3 Oct 2005 - Owner: Stephen D - Target: 20 Dec 2005 - Closed: 22 Dec 2005 57 Create/revise use case in accordance with new template: Cars - Date 3 Oct 2005 - Owner: Dieter - Target: 15 Nov 2005 - Closed: 3 Nov 2005 58 Create/revise use case in accordance with new template: Sensor Consider ChemSecure case - action 55 Ensure consistency with NextGrid use case Remove non-base specification items from each use case Eliminate colo(u)r in pictures Use Poseiden UML tool to describe the use case Ensure the use cases element names, parameters and operations match the specification Ensure the figures and table numbers include the section number DONE - Date 3 Oct 2005 - Owner: Arjun/Ronny - Target: 19 Jan 2006 - Closed: 19 Jan 2006 59 Create/revise use case in accordance with new template: 3rd party delivery Ensure consistency with NextGrid use case Remove non-base specification items from each use case Eliminate colo(u)r in pictures Use Poseiden UML tool to describe the use case Ensure the use cases element names, parameters and operations match the specification Ensure the figures and table numbers include the section number DONE - Date 3 Oct 2005 - Owner: Dieter - Target: 19 Jan 2006 - Closed: 19 Jan 2006 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 - Is this still true? I (SMF) think not. Remove Appendix C Add sentences to the introduction to explain defining the vocabularies is typically a common activity. Susan will pick up updated use case updates next on 31 Dec 2005 DONE - Date: 3 Oct 2005 - Owner: Susan - Target: 22 Jan 2006 - Closed: 19 Jan 2006 62 Make Section 3 naming consistent with Appendix supplied by Shailendra. - Date: 8 Dec 2005 - Owner: Cecile - Target: 22 Dec 2005 - Closed: 12 Jan 2006 63 Make section 2 consistent with section 3. - Date: 8 Dec 2005 - Owner: Dieter - Target: 22 Dec 2005 - Closed: 12 Jan 2006 64 Complete the object model for INFOD and place on gridforge This is to help with XML generation, to understand what we are talking about in the use cases, to cross check the interfaces in the use cases DONE - by figure 3 in the specification - Date: 8 Dec 2005 - Owner: Stephen and Chris - Target: 22 Dec 2005 - Closed: 27 Apr 2006 65 Cleanup headings in accordance with Steve Fisher' remarks - Date: 8 Dec 2005 - Owner: Dieter - Target: 22 Dec 2005 - Closed: 12 Jan 2006 66 Remove all items that should not be mentioned in the base document e.g., POBoxes, and Disseminators which might go into another document Do global search - Date: 8 Dec 2005 - Owner: Dieter - Target: 22 Dec 2005 - Closed: 12 Jan 2006 67 Merge references for use case and patterns doc - Date: 8 Dec 2005 - Owner: Dieter - Target: 22 Dec 2005 - Closed: 12 Jan 2006 68 Page 4: Define and explain vocabulary on page 4 when it is first mentioned - Date: 8 Dec 2005 - Owner: Dieter - Target: 22 Dec 2005 - Closed: 12 Jan 2006 69 Page 4 typo - last but not least, associations and relationships - Date: 8 Dec 2005 - Owner: Dieter - Target: 22 Dec 2005 - Closed: 12 Jan 2006 70 Identify the requirements that are not satisfied in this specification Keep the whole set of requirements though - Date: 8 Dec 2005 - Owner: Dieter - Target: 22 Dec 2005 - Closed: 12 Jan 2006 71 Remove non-goals - Date: 8 Dec 2005 - Owner: Dieter - Target: 22 Dec 2005 - Closed: 12 Jan 2006 72 Page 7 - Four kinds of objects - all have EPRs : (1) entity, (2) vocabulary, (3) vocabulary instance, (4) association - Date: 8 Dec 2005 - Owner: Dieter - Target: 22 Dec 2005 - Closed: 12 Jan 2006 73 Avoid font smaller than 10 pt - also remove color See figure 3 - Date: 8 Dec 2005 - Owner: Dieter - Target: 22 Dec 2005 - Closed: 12 Jan 2006 74 Page 7 - par 1 - Send Dieter paragraph to clarify: whether vocabulary is compulsory or not - Date: 8 Dec 2005 - Owner: Steve - Target: 22 Dec 2005 - Closed: 12 Jan 2006 75 Remove publication type and home disseminator - Date: 8 Dec 2005 - Owner: Dieter - Target: 22 Dec 2005 - Closed: 12 Jan 2006 76 Review register vocabulary and version issues We will abandon vocabulary versions. DONE - Date: 8 Dec 2005 - Owner: Cecile, Arjun and Dieter - Target: GGF16 - Closed: 27 Apr 2006 77 Remove the word important (see Steve Fisher e-mail) - Date: 8 Dec 2005 - Owner: Dieter - Target: 22 Dec 2005 - Closed: 12 Jan 2006 78 Page 7 - sort out vocabularies - introduce sub-section between 2 and 2.1 (see Stephen Davey e-mail) - Date: 8 Dec 2005 - Owner: Dieter - Target: 22 Dec 2005 - Closed: 12 Jan 2006 79 Delete register vocabulary as it is covered in Section 3 - Date: 8 Dec 2005 - Owner: Dieter - Target: 22 Dec 2005 - Closed: 12 Jan 2006 80 Review 2.1 and 2.1 because a lot of it is covered in Section 3 So section 2 becomes overview - Date: 8 Dec 2005 - Owner: Dieter - Target: 22 Dec 2005 - Closed: 12 Jan 2006 81 Suggestion from Steve Fisher - consider the hybrid XML and BNF notation used in WSN Referered to as Pseudo-schema - Date: 8 Dec 2005 - Owner: Dieter - Target: 22 Dec 2005 - Closed: 12 Jan 2006 82 Clean up section 2 (use prose not bullets) and remove references to names with INFOD_*,, EPR, - Date: 8 Dec 2005 - Owner: Dieter - Target: 22 Dec 2005 - Closed: 12 Jan 2006 83 Remove Pause and ResumePublisher operations from Registry 99 Reconcile the appendix with the calls in the document relating to the message structure DONE - Date: 26 Jan 2006 - Owner: Cecile, Arjun, Shailendra - Target: - Closed: 27 Apr 2006 100 Need to add a consumeMetadata interface Consider use of WSN (OGSA Base profile???!!*) - Yes we will do it this way. DONE - Date: 26 Jan 2006 - Owner: Cecile, Arjun and Dieter - Target: Feb 28 2006 - Closed: 27 Apr 2006 - Date: 8 Dec 2005 - Owner: Cecile - Target: 22 Dec 2005 - Closed: 12 Jan 2006 84 Change getMData to getMetadata or getMetaData - Date: 8 Dec 2005 - Owner: Cecile - Target: 22 Dec 2005 - Closed: 12 Jan 2006 85 Have another go at re-writing the paragraph p18 for the Consumer operation - Date: 8 Dec 2005 - Owner: Cecile - Target: 22 Dec 2005 - Closed: 12 Jan 2006 86 Remove Pause/Resume Consumer - Date: 8 Dec 2005 - Owner: Cecile - Target: 22 Dec 2005 - Closed: 12 Jan 2006 87 Update all create operations with the description below '... is used to create an infod xxx entity in the infod registry' instead of spitting out 'the infod consumer creates... itself'. so removing the 'role' of the person issuing the create operation - Date: 8 Dec 2005 - Owner: Cecile - Target: 22 Dec 2005 - Closed: 12 Jan 2006 88 Investigate the need for the publish interface on publisher and description of publishing We concluded that it was not needed. - Date: 8 Dec 2005 - Owner: Shailendra and Steve F - Target: 19 Jan 2006 - Closed: 26 Jan 2006 89 In 3.2.1 to have the full the full xml from the appendix for create publisher So that other sections can refer to it and only have sub-set of the info In addition this should be compatible with what the WSN spec has done. This may or may not be a further addition. DONE - Date: 8 Dec 2005 - Owner: Arjun - Target: 19 Jan 2006 - Closed: 26 Jan 2006 90 Page 40 - INFOD Entity and another INFOD entity See Stephen Davey's e-mail - Date: 8 Dec 2005 - Owner: Cecile - Target: 22 Dec 2005 - Closed: 12 Jan 2006 91 Implement changes in her reply to Stephen Davey. - Date: 8 Dec 2005 - Owner: Cecile - Target: 22 Dec 2005 - Closed: 12 Jan 2006 92 Revise cars use case in style of NextGrid use case Remove non-base specification items from each use case Eliminate colo(u)r in pictures Use Poseiden UML tool to describe the use case Ensure the use cases element names, parameters and operations match the specification Ensure the figures and table numbers include the section number Correct email address etc. in Car dealer: Figure 12 DONE - Date 15 Dec 2005 - Owner: Dieter - Target: 30 Dec 2005 - Closed: 12 Jan 2006 93 Create version of the patterns section that includes the base apecification items only Ensure headings are appropriate DONE - Date 15 Dec 2005 - Owner: Dieter - Target: 30 Dec 2005 - Closed: 12 Jan 2006 94 Check release 13 of the spec to see that actions which should have been addressed have been and idetnify any new issues DONE - Date: 5 Jan 2006 - Owner: All - Target: 12 Jan 2006 - Closed: 12 Jan 2006 95 Check release 13 of the spec for WS compatibility DONE - Date: 5 Jan 2006 - Owner: Abdeslem - Target: 12 Jan 2006 - Closed: 12 Jan 2006 96 Investigate adding to the spec "description of how the registry informs publishers what subscriptions are" so that we can clarify to whom a publisher should send. - Date: 12 Jan 2006 - Owner: Arjun and Dieter - Target: 19 Jan 2006 - Closed: 26 Jan 2006 97 getMetaData of the spec is too vague More information will be added Consider more specific operations Material has been added to the use cases but still needs to go into the spec Now superceded - Date: 19 Jan 2006 - Owner: Dieter, Ronny - Target: F2F - Closed: 18 May 2006 98 Explain the notification functions of the registry as appropriate in the base specification - Date: 19 Jan 2006 - Owner: Dieter - Target: - Closed: 26 Jan 2006 99 Reconcile the appendix with the calls in the document relating to the message structure DONE - Date: 26 Jan 2006 - Owner: Cecile, Arjun, Shailendra - Target: - Closed: 27 Apr 2006 100 Need to add a consumeMetadata interface Consider use of WSN (OGSA Base profile???!!*) - Yes we will do it this way. DONE - Date: 26 Jan 2006 - Owner: Cecile, Arjun and Dieter - Target: Feb 28 2006 - Closed: 27 Apr 2006 101 Modify interfaces from notes of 11 Feb DONE - Date: 12 Feb 2006 - Owner: Ronny - Target: 18 Mar 2006 - Closed: 27 Apr 2006 102 Redo chapter 2 of spec DONE - Date: 12 Feb 2006 - Owner: Steve - Target: 12 Mar 2006 - Closed: 27 Apr 2006 104 Consider Rational Software Architect (ex-Rose) Susan has distributed instructions: https://forge.gridforum.org/projects/infod-wg/document/Getting_UML_Tools_/en/2 DONE - Date: 12 Feb 2006 - Owner: Chris - Target: 12 Feb 2006 - Closed: 27 Apr 2006 105 Must all "things" in INFOD be web services if we are to use WSA? Note that in WSN the NotificationProducer must be a WS Susan has explained that it is not a problem https://forge.gridforum.org/projects/infod-wg/document/Clients_and_WS-Addressing/en/2 DONE - Date: 12 Feb 2006 - Owner: Susan - Target: 23 Feb 2006 - Closed: 27 Apr 2006 106 Find better name for CreateVocabularyInstance Steve suggests Property Values - but Ronny doesn't like it We have got bored with this - the name will be left - Date: 12 Feb 2006 - Owner: Steve and Stephen and Ronny - Target: F2F - Closed: 18 May 2006 107 Define a simpler message structure WSN addresses this DONE - Date: 12 Feb 2006 - Owner: Arjun and Shailendra - Closed: 27 Apr 2006 110 Provide example of metadata query In Use Cases DONE - Date: 30 Mar 2006 - Owner: Dieter - Target: 6 Apr 2006 - Closed: 27 Apr 2006 111 Provide example of metadata subscription Ronny will write this up in spec Superceded - Date: 30 Mar 2006 - Owner: Dieter, Ronny - Target: F2F - Closed: 18 May 2006 112 Provide example of metadata response In Use Cases DONE - Date: 30 Mar 2006 - Owner: Dieter - Target: 6 Apr 2006 - Closed: 27 Apr 2006 113 Can consume become notify (WSN)?? Also need to check that a notify message can be sent without explicit subscription DONE - Date: 30 Mar 2006 - Owner: Arjun - Target: 6 Apr 2006 - Closed: 27 Apr 2006 115 Remove any reference to vocabulary versions from spec DONE - Date: 27 Apr 2006 - Owner: Ronny (and Steve should check chapter 1) - Target: 11 May 2006 - Closed: 11 May 2006 116 Describe message body for meta-data Superceded - Date: 27 Apr 2006 - Owner: Arjun and Dieter - Target: F2F - Closed: 18 May 2006 117 Remove explicit dependency upon SOAP in chapter 2 our text should not say "... using the SOAP v1.1. Base Fault Spec", but should perhaps say "... using WS-BaseFaults". Then should clearly mark any SOAP stuff as "SOAP Examples". DONE - Date 4 May 2006 - Owner: Ronny - Target: 11 May 2006 - Closed: 11 May 2006 118 Remove 2 optional association fields for property constraints of the association and for policy of the association. DONE - Date 4 May 2006 - Owner: Steve for Chapter 1 and Ronny for Chapter 2 - Target: 11 May 2006 - Closed: 11 May 2006 119 Execution mode "FORCE" to be redefined This should cause any entry in the registry referencing the object to be dropped. This is of course recursive. If we don't do this we allow an inconsistent state to be exposed. I have currently described it incorreclty in chapter 1 as I have only considered the "IF UNUSED" case. DONE - Date 4 May 2006 - Owner: Steve for Chapter 1 and Ronny for Chapter 2 - Target: 11 May 2006 - Closed: 11 May 2006 120 Clarify use of WSN in chapter 1 WSN only to be used for notification type messages DONE - Date 4 May 2006 - Owner: Steve - Target: 11 May 2006 - Closed: 11 May 2006 121 Consider example of constraint field in associations It was decided that they are needed - Date 11 May 2006 - Owner: Dieter - Target: F2F - Closed: 18 May 2006 124 Show (example) how one can define operational constraints for entities through the property vocabulary Forget it! - Date: 16 May 2006 - Owner: - Target: - Closed: 18 May 2006