INFOD Unresolved Issues ======================= This is a list of open issues. Each issue has a serial number, once it is resolved it is moved to a companion document of resolved issues ============================================================================== ============================================================================== 2 What are components of the manifest section of the infod data (and metadata) message? this is the message that is sent to the consume or notifyupdate operations. Once that is described, scenarios like rgma can decide whether they can use that format to publish and essentially support the PO Box at the publisher site A document has been circulated - Date: 1 Jul 2005 - Owner: Shailendra - Target date: 28 Jul 2005 5 Do we need consumptions as well as subscriptions? http://www-unix.gridforum.org/mail_archive/infod-wg/2005/06/msg00020.html http://www-unix.gridforum.org/mail_archive/infod-wg/2005/06/msg00021.html http://www-unix.gridforum.org/mail_archive/infod-wg/2005/06/msg00026.html http://www-unix.gridforum.org/mail_archive/infod-wg/2005/06/msg00028.html So far it appears not - Date: 1 Jul 2005 - Owner: Dieter, Cecile - Target date: None 7 How are registry object updates broadcast to interested infod player for ex, how new subscriptions are found by publishers - describe how notifying/finding appropriate consumers for metadata messages - specs don't do it now (notifyUpdate interface half spec'ed) and we didn't discuss at F2F (Animation scenario feedback) A duplicate issue: due to the dynamic nature of publications, publishers, etc., a subscription may need to include information about how to notify consumers of changes to the subscription dependencies (additional publishers, removal of publishers that occur over time, etc.). http://www-unix.gridforum.org/mail_archive/infod-wg/2005/03/msg00029.html What is the interaction between parameters of subscription - their dependencies? Subscription parameters are infod object components that may interact with each other (what happens if data filter exists but not association, or if both exist, or none...) - Describing interaction will help readers understand these components better and simplify section 3 as at least one is required but not clear what non-provided parm means (means all as in '*' or means NULL...). These are the interactions between the INFOD registry and the INFOD objects: * The objects request modifications through the create/alter/dropINFODResource interface In response to such a request the INFOD registry will identify with publishers are publishing or are able to publish the requested information and limit the selection using any criteria that is part of the publisher and consumer specification. * If the INFOD registry is unable to verify the expression related to the data it will request verification by at least one publisher using a web services interface. * If requested the subscriber will be notified - using the consumption interface - to select publishers and subscribers of interest. * If requested the publisher will be notified - using the consumption interface - about the changes: new/changed/dropped subscriptions and new/changed/dropped subscribers. Note: * If the publisher (or subscriber) has not implemented the consumption interface the information will be made available using the POBOX. That is associated to an INFOD registry. This is in the current draft but it may not be too easy to read - Date: 1 Jul 2005 - Owner: Cecile, Dieter - describe options - propose parms - summarize pbm - discuss scalability - target date: 1 Sep 2005 8 How does registry handles EPRs, especially when logical EPRs for expressions? logicalEPRs don't current support expressions - define how to do so - indirection Shailendra will contact Abdeslem and Cecile if necessary - Date: 1 Jul 2005 - Owner: Abdeslem, Shailendra - describe options - summarize pbm - also, quick description of what an EPR is - Target date: 1 Sep 2005 ResolveEPR is in spec 15 Which (if any) components support transformations? Are they supported by consumptions? consumption  has different  use-cases:    replication,  fan-out with same subscription and different consumer    transforms, different channel    options for a given consumer, (followup at http://www-unix.gridforum.org/mail_archive/infod-wg/2005/06/msg00017.html) - Date: 1 Jul 2005 - Owner: Shailendra and Dieter - Target date: 31 Aug 2005 16 How do we deal with retention periods? Separation of data retention from data publishing - Date: 1 Jul 2005 - Owner: Dieter - Target date: 31 Aug 2005 17 How do the propagation interface(s) differ from the consume interfaces and what is stored in the registry? - Date: 1 Jul 2005 - Owner: Shailendra, Cecile - Target date: 4 Aug 2005 18 Should we be looking at other rule specifications and consolidate/align with them? E.g. This applies to transform definitions. Specs need to document approach taken. Also we are oriented towards putting things in multiple queues right now. But the consumer may not want to be able to see those queues, especially cross-VO. So we need a mechanism for replaying past events without the producer understanding the ID structure of the consumer. The consumer just wants to get the information; it shouldn't have to know what the underlying structure was. - Date: 1 Jul 2005 - Owner: Shailendra - Target date: 22 Should we add a workflow Use Case - Date: 1 Jul 2005 - Owner: Dieter - target date: GGF15 23 How does INFOD relate to OREP? OREP includes in its charter replication specifications so positioning is necessary between OREP (file only ?) and INFOD. - Date: 1 Jul 2005 - Owner: Cecile - target date: 15 Sep 2005 (talk to Ann - follow-up with David Martin - may close OREP) 24 How do security issues apear in the spec? One specific aspect is how registry decides who can delete the publication_types and other objects? - Date: 1 Jul 2005 - Owner: Vijay and Dieter - target date: 15 Sep 2005 25 Can INFOD implement R-GMA semantics? - Date: 1 Jul 2005 - Owners: Steve F - target date: After next draft Not yet because of lack of POBOX 27 What's special about INFOD disseminators? * Retention of information * Querying information * Auditing and tracking - Date: 1 Jul 2005 - Owners: Abdeslem - Target date: after current rewrite (4. Aug 2005) 29