[infod-wg] nextgrid seq. diagram 1 -answers to a few questions about the specs

[Cecile Madsen]

Answers to a few points raised by Stephen about the specs.
The first two are known open issues:

1.2  Notify of new subscription?  [How is the publisher informed of new
subscriptions in the Registry?]
      - it is currently missing from the specs. A proposal was to add a
subscription flag
        that would provide implicit notification to dependent publishers
(finding dependent publications
        and from there the publishers).

3     DPublish(event message?, consumer?) [What parameters are included in
the DPublish interface?]
      - also currently missing from the specs. The specs do describe an
infod message as consisting
        of a header, manifest and payload (section 2) so the DPublish
message will follow that structure.
        Which attributes actually belong to the header, manifest for a
DPublish message hasn't been
                  reviewed yet. Part of the flexibility is to allow the
manifest to be rich enough to be queried along
        the message lifespan (from publishing to eventual consumption: the
manifest will include infod-like
        attributes whereas the header will include message-like attributes
(length, etc.)).
      - the DPublish is an operation against a disseminator. So not for
consumers. Consumers receive
        data messages (as opposed to meta data messages) through the
consume/receive operation
        of the consumer interface. So a publisher will have to
differentiate between publishing messages
        to a disseminator vs a consumer interface.

4     Consume/Receive(InfoD Message?)  [What is the actual name of this
interface?
       Is the message a parameter somehow included in this interface?]
      - the interface is called the consumer interface, which has only one
operation: consume/receive.
        The messages supported by any infod consumer interface will have
the same infod message
        format mentioned above (header, manifest and payload components).
      - so to compare with wsn, the manifest component will include - but
not be limited to - the
        publication type ('Topic') and publisher reference
('ProducerReference') and the payload component is
        equivalent to the 'Message' component of the wsn Notify message.

Cecile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.ogf.org/pipermail/infod-wg/attachments/20050622/d85d8ad9/attachment.html