Broker Class Broker Package

Copyright © 2010 Open Geospatial Consortium, Inc. 37 Table 24 – Broker Properties Property name Description Value registration A broker manages registrations. Type : Registration Default: none Cardinality : [0..]

6.2.1.5.2 Registration Class

Metadata on a registration which is a resource with lifetime and thus may be terminated at any time. Table 25 – Registration Properties Property name Description Value deliveryTo The consumer endpoint of the broker where new notifications for this registration shall be sent to. The delivery endpoint shall be omitted when a registration is proposed to an Event Service. If the service accepts the registration, it shall fill in the endpoint. Type : Endpoint Default: none Cardinality : [0..1] publisherEndpoin t Endpoint of the entity that publishes events - not necessarily identical to the event source entity that generated the event. This property is required in a proposed Registration which requests demand based publication behavior. The endpoint then has to reference a Producer . Type : Endpoint Default: none Cardinality : [0..1] eventMetadata Metadata on the events that are going to be published as part of this registration. May be omitted in case that this information is not available. Note: whether the association is directed or not depends on whether a client should be able to see in a publication who is the publisher responsible for it. Type : Publication Default: none Cardinality : [0..1] 38 Copyright © 2010 Open Geospatial Consortium, Inc.

6.2.1.5.3 Registrar Interface

Defines operations to register for sending notifications to the implementing entity and to get existing registrations. Table 26 – Registrar Operations Method Notes getRegistrations Retrieves all currently existing registrations. register Creates a registration. Upon success, the new registration is returned - otherwise an exception.

6.2.2 Behavior Model

The following subsections document a selection of the behavior that is expected from an OGC publish subscribe service. The model mostly covers important aspects. This work can and should be continued in the future to define the desired behavior in more detail.

6.2.2.1 Resources Lifecycle Management

As described in section 6.2.1.2, a resource may have a lifetime. If it has, then it can be explicitly terminated. It may also be terminated automatically once the scheduled termination time has expired. The following diagram shows the interactions and events involved in terminating a resource. This lifecycle management applies to all resources with lifetime, for example subscriptions and registrations.