[infod-wg] Notes from INFOD F2F on 31 May and 1 June 2005

[Susan Malaika]

An INFOD  F2F was held on 31 May and 1 June with the goal of working on 
use cases. Many thanks to Steve Fisher for hosting an excellent meeting. 
The following items have been made available to the meeting participants. 
If you want a copy of any of these items please let me know.
A transcript of the chat session held across the two days 
NextGrid Animation Use Case Charts with revisions during F2F
Revisions and notes in Resource Creation Scenarios document by Cecile 
Introduction to R-GMA (Relational Grid Monitoring Architecture - a source 
of some use cases)

Attached to these notes is a rough document on NextGrid Animation Use Case 
created during the meeting 

The F2F Agenda (31 May and 1 June)
1. Review Cecile's Use Cases or Patterns 
2. Review NextGrid  Animation Use Case (Day 1)
3. Review R-GMA Network Monitoring Use Case (Day 2)

F2F Participants
Stephen Davey, Abdeslem Djaoui, Steve Fisher, Dieter Gawlick, Steve Hicks, 
Chris Kantarjiev, Cecile Madsen, Susan Malaika, John Walk, 
 
Future Calls and  Meetings
Call 9 June: Review template and terminology 
Call 16 June: Review revised use cases (NextGrid Animation, R-GMA Network 
Monitoring)
Call 23 June: Prepare for F2F 
Chicago :25-26 June 2005
Review Specifications and Use Case documents for consistency and for 
action follow-up  from earlier meetings and calls
Review Interaction Diagrams
Review Consumption Service concept
Apply Use Cases to Patterns

Actions from F2F
By June 9: 
Dieter, John, Cecile - Agree and circulate terminology (especially 
publication, publication description, publication pre-processing, 
consumption, artifacts, entities) 
Steve Fisher - Circulate new Use Case Template 
Steve Fisher - Circulate R-GMA Network Monitoring Use Case Notes 
(Overview, Attributes of objects in the registry, Steps, What changes in 
the registry at each step) - similar to NextGrid Animation Notes attached 
below
By June 16: 
Stephen Davey - Complete first draft of Nextgrid Animation Use Case 
Steve Fisher - Complete first draft of R-GMA Network Monitoring Use Case
By June 23:
Cecile - Cleanup Specification 
Chris - Produce Interaction Diagram 
Steve Fisher - Write up consumer service requirement
Steve Fisher and Susan Malaika - Create INFOD patterns based on Cecile's 
document for INFOD F2F at Abingdon -
Abdeslem - Investigate if  Implementing (1) Getdata (2) Consume/Receive 
(3) Subscribe (Create Consumer) on an entity is the same as an R-GMA 
Consumer Service. Investigate how WSN Pull Point relates to R-GMA Consumer 
Service
Dieter, Shailendra and Cecile - Review Consumptions (e.g.,preprocessing of 
messages prior to receipt,  shared consumptions)
Cecile: Add pattern of many publishers publishing into one publication
Cecile and Dieter: Review separation of data retention from data 
publishing
Susan and Abdeslem - WSN Summary Review

More Actions from F2F:
Define late binding and  Determine where late binding is supported
Not assigned yet?
Define Non-events - are they are deadline related?
Steve Fisher and Susan Malaika -  Handle through use case for now
Define INFOD Factoring - Cecile Madsen 
(1)Publication and Subscription with no consumption to be aligned with WSN 
(without broker) ? Base Notification 
        Homogeneous vocabulary ? e.g., XPath
(2) Publication, Subscription, Dissseminators to be aligned with WSN (with 
broker) ? Brokered Notification
                (3) Multiple Disseminators (Brokers)
                (4) Heterogeneous Vocabularies ? Identity Management
                        Is this outside scope of INFOD?
Define relationship with WSN - Abdeslem Djaoui
(1) What?s the difference between a disseminator and a WSN broker? 
publication and WSN topic?  Vocabulary and WSN filter?
(2) Can WSN send message directly to a consumer by name? 
(3) Should Vocabulary Management and Identity Management be part of the 
specification? 
(4) Publications are defined by topics in WSN, how does that differ from 
INFOD mechanisms for controlling publications through vocabularies? 
Review what?s in the specification on vocabularies and give feedback - 
Steve Fisher 
Review what's in the specification about disseminators and give feedback - 
Dieter Gawlick and Shailendra
Do disseminators provide transforms?
What?s special about INFOD disseminators?        e.g., 
        Retention of information
        Querying information
        Auditing and tracking


        These are some remarks noted in Day 1 of F2F (noted as points in 
Cecile's preparatory document on resource creation scenarios)
        Registry content - can subscribe to changes ... 
Artifacts have instances or types in the Registry:
 Subscription; Publication; Consumption; Disseminations 
        There are relationships between artifacts
        Artifacts are Data 

Entities have instances in the Registry (like an LDAP registry): 
Subscriber; Publisher; Consumer; Disseminator; Registration Manager
        There are relationships between entities and artifacts
        Entities are Actors (that have roles)


Subscriptions (filters and/or plugins) are defined by consumers or third 
parties and are applied:
        Before or During Publication
        After Publication (Disseminator) 
        Before Consumption (Consumer)

When a consumer subscribes then it is pulling on future data (rather than 
querying on current data)
Consumptions (filters and/or plugins) are most likely defined by consumers 
and are applied to publications immediately prior to consumption

Publishers, Disseminators and Consumers can all look at subscriptions 
        Publishers to determine what to publish (optional)
        Disseminators to determine whether to disseminate (optional)
        Consumers to determine whether to apply a consumption (or whether 
the subscription is adequate) (optional)

INFOD does not transfer data
        Unless the data is attached to notifications
 
More on Disseminators:
Without Disseminators: 
Publishers have a lot of intelligence (for they interpret subscriptions)
Publishers have to understand the subscription filter language and plugins
Subscriptions must be interpreted by publishers 

With Disseminators:
        The disseminator could interpret subscriptions on behalf of 
unconditional (dumb) publishers 
        Subscriptions and Consumptions can be applied in multiple places 
 
Not every INFOD implementation has to support ?late binding? consumptions 

Some Notes for Case 1 in Cecile's preparatory document 
Case 1 is like a mailing list with consumers being able to possibly update 
their destination (during the day, page mel and after 9pm don't page me)

Don?t add operation 5 to Case 1A (because the publisher would have to 
continue pulling) 
Could add operation 5 to Case 1B ? 
Consumer doing alter/drop consumption (to have the consumer change its 
mind)?
(Already have notify for the registration manager ? which could be used to 
tell the publisher)
What about the subscriber changing its mind?


Some notes from Day 2 in F2F:
R-GMA tuples have timestamps 1. when expire ; 2. when set
R-GMA "Tables"  could be files
R-GMA has 4 query types
Type (1) Query - Latest
Type (2) Query History
Type (3) Continuous - Delta (something new - event publishing)
Type (4) Static Query - Allow to query information not collected by R-GMA 
- may not have timestamp columns
R-GMA has 6 services:
                Schema Service (table defns - reminder the tables may be 
sitting on top of file system)
                Registry Service
                Services for primary, secondary and on demand producers 
                Consumer Service
R-GMA has 2 types of an event store
Type 1: Latest system
Type 2: Historical
Currently R-GMA Registry is for consumers to locate publishers - not for 
publishers to locate consumers
R-GMA Publications
R-GMA CREATE TABLE -> Vocabulary for a collection of publishers to publish 
into
R-GMA DECLARE TABLE -> the way a publisher says I publish into a known 
table
R-GMA DECLARE TABLE is analogous to a Publication Description
Entry Points for Consumers
Registry is the entry point for INFOD
R-GMA consumer service
Is entry point to the R-GMA database
Chooses producers and consume messages for retrieval by applications
In R-GMA - MPublish goes to the consumer service (in contrast with INFOD)


Apologies for errors in these notes
Susan Malaika

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.ogf.org/pipermail/infod-wg/attachments/20050602/318c1da9/attachment.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: NextGrid.usecase.31May2005.doc
Type: application/octet-stream
Size: 69120 bytes
Desc: not available
Url : http://www.ogf.org/pipermail/infod-wg/attachments/20050602/318c1da9/attachment.obj