Boolean Result for Filter Statement
9.1.3 Resolve Content Given By Reference
The GML model allow values of feature properties to be given by a reference a URL in an xlink:href property rather than inline of the XML instance. The idea is that a system that receives such an XML instance would automatically resolve the reference to get the value and insert it into the inline content. An Event Service should automatically retrieve event properties given by reference if they are queried in the filter statements of a subscription. This can happen on demand. Problems can occur if the value cannot be resolved e.g. if wrong connection timeouts have been chosen or if the value itself is complex and has properties given by reference. Such deep reference structures can slow down an Event Service. The effects and possible performance issues of using event properties given by reference in event filtering should be investigated in more detail. When using xlink references encoded according to the GML specification, data providers that create event instances should be aware that applications receiving the events may not preserve the namespace-prefix binding for the XPath expression used in the reference. Consider the following example: xlink:href=http:www.aixm.aeroschema5.1dnotamexample elementdnotam:Event[gml:identifier=aPreviousId] It shows an xlink with a URI reference that the GML standard OGC 07-036 calls an element scheme based XPointer . The absolute URI http:www.aixm.aeroschema5.1dnotamexample is followed by the fragment identifier and then the XPointer. Although this behavior is not recommended by the W3C, an application that receives an event e.g. an XML router application could change the prefixes in the attributes and elements of an XML instance but not in the content of them. In the above example, the dnotam and gml prefix would then no longer bind to the correct namespaces. A service could no longer resolve the correct element from the given URI. Therefore, it is more safe to use an xpointer scheme based XPointer see OGC 07-036 – the example would then look like this: xlink:href=http:www.aixm.aeroschema5.1dnotamexample xmlnsdnotam=http:www.aixm.aeroschema5.1dnotam xmlnsgml= http:www.opengis.netgml3.2 xpointerdnotam:Event[gml:identifier=aPreviousId] Here, the namespace-prefix binding is preserved in the reference itself.9.1.4 Reference System Transformation
When a filter statement is created to be used in subscriptions, it often includes filter operand values. In simple applications, the reference system of these operands e.g. aParts
» OWS-7 Event Architecture Engineering Report
» Scope OWS-7 Event Architecture Engineering Report
» Document contributor contact points
» Revision history OWS-7 Event Architecture Engineering Report
» Future work OWS-7 Event Architecture Engineering Report
» Foreword OWS-7 Event Architecture Engineering Report
» Abbreviated terms OWS-7 Event Architecture Engineering Report
» Resource Class ResourceWithLifetime Class
» ResourceManager Interface ResourceTermination Interface
» AdHocEventChannel Class AggregationChannel Class
» EventChannel Class EventChannelRelationship Class
» EventMetadata Class EventingInformation Class
» Endpoint Class EndpointDeliveryMetadata Class
» Filter Class Notification Class
» PausableSubscription Class Producer Package
» Producer Class Publication Class
» Registration Class Broker Package
» Resources Lifecycle Management Behavior Model
» Managing Subscriptions Behavior Model
» Handling a Pausable Subscription
» Demand Based Publishing Behavior Model
» Introduction Event Channels OWS-7 Event Architecture Engineering Report
» Publish Subscribe Requirements OWS-7 Event Architecture Engineering Report
» Introduction Realization of Publish Subscribe
» Requirements Mapping for WS-Notification
» Summary Realization of Publish Subscribe
» Introduction Event Metadata Example
» The Event Service Discovery Model The Event Service Discovery extension package
» Scenario 1: Find a Service providing Sensor Data that supports Comparison Filters
» Step 2: Scenario 2: Find a Service providing Aviation Data in a specified Area
» Sample Event Service objects Discovery challenges:
» Denial of service Security threats and vulnerabilities
» Message replay Security threats and vulnerabilities
» Message modification Security threats and vulnerabilities
» Spoof of identity Security threats and vulnerabilities
» Intermediary network devices Security threats and vulnerabilities
» Trojan horse type of attacks
» Authorization or access control
» Data confidentiality Security measures
» Data integrity Security measures
» Communication security Security measures
» Mapping security measures to threats
» Threat Mitigation in WS- Environment
» Threat Mitigation in RESTful Environment
» Reliability OWS-7 Event Architecture Engineering Report
» Boolean Result for Filter Statement
» Event Wrapper Potential Pitfalls
» Resolve Content Given By Reference
» Reference System Transformation Potential Pitfalls
» Filter Encoding XPath Filter Processing Languages
» Event Pattern Markup Language
» Spatial Filtering via Bounding Box
» Spatial Filtering of Events Using Dynamic Filter Properties
» Discovery of filter functionality
» Specifying events OWS-7 Event Architecture Engineering Report
» Geosynchronization OWS-7 Event Architecture Engineering Report
» Dynamic Sensor Tracking and Notification Aviation
» Introduction OGC service specifications related to the Event Architecture
» Foreign standards and specifications related to the Event Architecture
» SWE Common AIXM Information models
» Introduction Document object model
» Spatially enabled Common Alert Protocol
» Code lists Common Alert Protocol
» Resource references Other features Interoperability
» Geosynchronization Common Alert Protocol
» Filtering CAP messages Common Alert Protocol
» EDXL-DE Common Alert Protocol
» WXXM Resource Requirements Package
» Consumer Requirements Package Publish Subscribe Requirements Package
» Registrar Requirements Package Information models
» Brokered Publish Subscribe Requirements Package Registering Broker Requirements Package
» Aggregation Channel Requirements Package
» Ad Hoc Channel Requirements Package
» Pausable Provider Requirements Package Demand Based Publication Requirements Package
» CSW-ebRIM Extension Package for Event Service Discovery
» Additional Sample Queries for Event Service Discovery
» XML Schema for Event Metadata
Show more