Leading the pervasive adoption of grid computing for research and industry © 2005 Global Grid Forum The information contained herein is subject to change without notice INFOD Interfaces Abdeslem Djaoui, Rutherford Appleton Laboratory - On behalf of INFOD team October, 2005 (GGF15 in Boston)

2 GGF Intellectual Property Policy All statements related to the activities of the GGF and addressed to the GGF are subject to all provisions of Appendix B of GFD-C.1, which grants to the GGF and its participants certain licenses and rights in such statements. Such statements include verbal statements in GGF meetings, as well as written and electronic communications made at any time or place, which are addressed to any GGF working group or portion thereof, Where the GFSG knows of rights, or claimed rights, the GGF secretariat shall attempt to obtain from the claimant of such rights, a written assurance that upon approval by the GFSG of the relevant GGF document(s), any party will be able to obtain the right to implement, use and distribute the technology or works when implementing, using or distributing technology based upon the specific specification(s) under openly specified, reasonable, non-discriminatory terms. The working group or research group proposing the use of the technology with respect to which the proprietary rights are claimed may assist the GGF secretariat in this effort. The results of this procedure shall not affect advancement of document, except that the GFSG may defer approval where a delay may facilitate the obtaining of such assurances. The results will, however, be recorded by the GGF Secretariat, and made available. The GFSG may also direct that a summary of the results be included in any GFD published containing the specification.

3 Overview Base INFOD Interfaces −Base INFOD managers −Consumer Post GGF15

4 INFO Base - PublisherConsumer Registry Vocabularies Publisher Consumer Subscriptions Vocabulary Associations Messages GMA architecture Role of INFODRegistry: −Registrations manager −Mutual filtering between publishers and consumers −Vocabulary manager

5 Base interfaces – modeled on WSN BasePublisherManager −Manages INFOD Publisher entries in an INFOD Registry BaseConsumerManager −Manages INFOD Consumer entries in an INFOD Registry BaseSubscriptionManager −Manages INFOD Subscription entries in an INFOD Registry BaseVocabularyManager −Manages user vocabulary, and user property vocabulary entries in an INFOD Registry BaseAssociationManager −Manages INFOD Association entries in an INFOD Registry BaseRegistrationManager −Common operations for registry entries Consumer −Defines how INFOD messages are consumed by a consumer

6 BasePublisherManager Publisher entity −publishers are the sources of information −Publisher may register with registry Operations −CreatePublisher() used by an INFOD publisher to register itself to an INFOD Registry −AlterPublisher() used by an INFOD publisher to update its metadata information at a given INFOD Registry. −DropPublisher() used by an INFOD publisher to remove its entity definition from an INFOD Registry. −PausePublisher()? −ResumePublisher()?

7 BaseConsumerManager Consumer entity −consumers are the sinks of information −Consumers may register with registry Operations −CreateConsumer() used by an INFOD consumer to register itself to an INFOD Registry. −AlterConsumer() used by an INFOD consumer to update its metadata information at a given INFOD Registry. −DropConsumer() used by an INFOD consumer to remove a consumer entity from an INFOD Registry. −PauseConsumer()? −ResumeConsumer()?

8 BaseSubscriptionManager Subscription entity −subscriptions are used to specify which data have to be disseminated from which publisher to which consumer −Subscription are stored in registry Operations −CreateSubscription() used by an INFOD client, referred to as a subscriber, to create an INFOD subscription in an INFOD Registry −AlterSubscription() used by an INFOD subscriber to update its metadata information at a given INFOD Registry. −DropSubscription() used by an INFOD subscriber to remove a subscription entity from an INFOD Registry. −PauseSubscription()? −ResumeSuscription()?

9 BaseVocabularyManager(1/2) INFOD users may define 2 types of vocabularies −User property vocabularies In the Description attribute of any INFOD entity −allow INFOD entities to be discovered and/or filtered based on these descriptions −User data vocabularies They describe the structure of the data that is available from publishers and is acceptable to consumers In the DataConstraints component of a subscription entity, −allows INFOD subscribers to describe the structure of the published data/data of interest to them.

10 BaseVocabularyManager(2/2) Operations −RegisterUserVocabulary() used by an INFOD publisher or consumer to register a user property vocabulary or a user data vocabulary in an INFOD Registry −AddVersionUserVocabulary() used by an INFOD publisher or consumer to provide a new version encapsulating the necessary changes to an INFOD vocabulary. −UnregisterUserVocabulary() used by an INFOD publisher or consumer to un-register a particular vocabulary from an INFOD Registry −RegisterUserPropertyVocabulary() − −AddVersionUserPropertyVocabulary() −UnregisterUserPropertyVocabulary()

11 BaseAssociationManager Association entities −relations between entities and vocabularies/other entities – vocabulary associations are used to relate vocabularies to entities; e.g., vocabularies to publishers. – entities associations are used to relate entities to each other; e.g., publisher or consumers to their home disseminators Operations −AssociateEntity() used by an INFOD publisher or consumer to create a relationship with another INFOD entity −DisAssociateEntity() used by an INFOD publisher or consumer to drop an entity association from an INFOD registry −AssociateVocabulary() used by an INFOD publisher or consumer to create a relationship between an INFOD entity and a user data vocabulary −DisAssociateVocabulary() used by an INFOD publisher or consumer to drop a vocabulary association from an INFOD registry

12 BaseRegistrationManager Additional interface for querying an INFOD registry (that aggregates that aggregates base INFOD manager interfaces) Operations −GetMData() used by an INFOD entity to query the INFOD Registry. −ResolveEPR()? used by an INFOD entity to map an INFOD Registry logical EPR expression to a set of INFOD physical addresses

13 Consumer Interface Interface for consuming application, user, etc. Operations: −Consume()? An INFOD publisher (or INFOD disseminator, as described in [INFODADV]) uses the Consume operation to send INFOD messages to an INFOD consumer

14 Post GGF15 Finalise what goes in BaseINFOD −GetData interfaces: does it belongs in base or not ? −Is spec too big? Separate Vocabulary management from registration and match making functionality? What can be done on time scale for a BaseINFOD spec WSN and WS-Eventing compatibility −Consume versus WSN Notify()? −Composability Advanced scenarios −disseminators, propagations −interfaces/operations for non-base scenarios