This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/go/projects.infod-wg/discussion.agendas_and_minutes.call_7_july_note_time_change at Sun, 06 Nov 2022 13:24:37 GMT SourceForge : Post

Project Home

Tracker

Documents

Tasks

Source Code

Discussions

File Releases

Wiki

Project Admin
Project: INFOD-WG     Discussion > Agendas and Minutes > call 7 July - note time change! > List of Posts
Forum Topic - call 7 July - note time change!: (2 Items)
View:  as 
 
 
call 7 July - note time change!
Reminder: this is an invitation to join the next INFOD conference call on Thursday, July 7, 2005 at:

    0900 PDT, 1200 EDT, 1600 UTC

        * Telephone numbers:
           US/Canada (toll free):  +1-888-235-8105
          Intl (toll): +1-719-884-8823

        * Passcode - 768430


Agenda:

* review F2F Chicago session, comments
* decide how to proceed with list of infod items (action items, open items, etc.)
* go over action items 2.1 (Dieter) and 2.2 (Abdeslem)
* schedule for infod weekly calls: 9AM PDT ok with everyone for remainder of year ?!

The INFOD team
minutes from 7 July call
Attendees: StevenD, Susan, Dieter, Abdeslem, Vijay, SteveF, Chris, Cecile

Minutes:

- no follow-up needed from F2F in Chicago. Pres and docs on gridforge (thks Susan).
- wsn public draft available soon.
- we reviewed items 2.1 and 2.2 (from list of open items that is being posted on gridforge)

--> Item 2.1: how to notify users of Registry updates

- reviewed proposal sent by Dieter to mailing list on 07/06/05
- agreed to introduce a separate interface 'verify' on publisher service for ex
- this allows to validate subscription expressions (simple and web-service-like option over plug-ins)
- agreed that notifications should be sent to whom is impacted by registry change *and* wishes to be notified
- Dieter and Cecile to describe message format for the notification
- assumption is that same consume operation will be used for data and metadata messages
- this implies that the message structure needs to differentiate between metadata and data message
- this also implies that in the metadata case, the payload structure needs to be described
- agreement to add a confirmation phase after verify step is done
- for example this ensures that specific publishers are acceptable to subscribers

--> Item 2.2: how to spec logical EPRs that consist of list of EPRs or INFOD expressions

- reviewed proposal sent by Abdeslem to mailing list on 07/06/05
- agreement on the proposal
- EPR can be logical so point to any end point (email, ...)
- suggestion to isolate the expression name from the proposed urn for subscription expressions (StevenD)
- suggestion to support expression names that would be shared across subscriptions (Dieter)

To-dos by next INFOD call:

- SteveF to post on gridforge the doc that lists open/action items for infod specs/use-case
- everyone to go over list of items they own and come up with prioritization/plan on how to address them
- Abdeslem and Dieter to update their proposals for 2.1 and 2.2
- Dieter and Cecile to describe INFOD message structure

Next INFOD call:

- agreed upon call time from now on is 8AM PST/PDT (Thursdays)
- meeting notice with call info to be sent by Dieter later


The INFOD Team

 
 


The Open Grid Forum Contact Webmaster | Report a problem | GridForge Help
This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/go/projects.infod-wg/discussion.agendas_and_minutes.call_7_july_note_time_change at Sun, 06 Nov 2022 13:24:37 GMT