Copyright © 2010 Open Geospatial Consortium, Inc.
29
Table 14 – EndpointDeliveryMetadata Properties
Property name Description Value
endpoint Endpoint where events shall be sent to.
Shall be omitted when subscription with pull delivery is proposed so that the service can
fill in the endpoint if it accepts the subscription.
Type
: Endpoint
Default: none Cardinality
: [0..1]
method Code for the method used to send
notifications.
Type
: DeliveryMethod
Default: none Cardinality
: [1]
6.2.1.4.5 Filter Class
Abstract class that represents all types of filter statements.
Note: the filter can be realized for example using XPath expressions, WS-Notification topic expressions, FES filter statements etc.
Note: a filter may be implicit - e.g. if a consumer is subscribed to an Atom feed then the filter to match only events posted on that feed is automatically created.
6.2.1.4.6 Notification Class
Container for messages. Multiple messages that shall be sent at the same time defined by the producer andor via policy may be contained in one notification.
A Notification is a Resource and therefore inherits all properties that a Resource has.
30
Copyright © 2010 Open Geospatial Consortium, Inc.
Table 15 – Notification Properties
Property name Description
Value
message Piece of information that shall be delivered.
Note: the cardinality of this attribute is one to multiple to support batch transmission of messages. This is one
way to decrease the amount of communication channels like HTTP connections that need to be
established between a publisher and consumer. We recognize that some communication protocols can
establish persistent connections so that this kind of mechanism would not be required there. Policies could
be defined that control the maximum time interval or amount of messages that would be used to gather up
messages before sending - this would be a kind of batch transport. Different ways to perform, control and
mange notification delivery can be investigated in the future.
Type
: Any
Default: none Cardinality
: [1..]
6.2.1.4.7 PausableSubscription Class
A
PausableSubscription
is a
Subscription
that can be paused. Pausing a subscription means that events that match the subscription criteria shall not be
delivered to the assigned consumer endpoint while the subscription is paused. This does not affect the delivery of matching events to the optional channel delivery endpoint. In
other words: if an AdHocEventChannel see section 6.2.1.3.1 is associated with a subscription then all events matching the subscriptions filter criteria shall be published on
that channel, regardless of whether the subscription is paused or not.
All events that are received or generated by the producer while a subscription is active e.g. if it has been resumed and that match the filter criteria shall be published to the
existing delivery endpoints.
A PausableSubscription is a Subscription and therefore inherits all properties that a Subscription has.
Table 16 – PausableSubscription Properties
Property name Description
Value
isPaused Indicates whether the subscription is paused
or not.
Type
: Boolean
Default:
false
Cardinality
: [1]