® sponsored by agenda for wfs/fes swg meeting 91st ogc technical committee geneva, suisse...

®

Sponsored by

Agenda for WFS/FES SWG MeetingAgenda for WFS/FES SWG Meeting

91st OGC Technical Committee

Geneva, Suisse

Panagiotis (Peter) A. Vretanos

11 June 2014

Copyright © 2014 Open Geospatial ConsortiumCopyright © 2014 Open Geospatial Consortium

OGC®

AgendaAgenda

• Status of draft WFS 2.X and FES 2.X documents (PAV)• WFS 2.0 CITE status update (PAV)• UKIAP Plugfest presentation (Bart de Lathouwer)• OWS-10 Service Integration presentation (PAV)

Copyright © 2014 Open Geospatial Consortium

®

Sponsored by

Status for documents Status for documents WFS 2.x, FES 2.xWFS 2.x, FES 2.x


Geneva, Suisse


11 June 2014


OGC®

As a reminder ...As a reminder ...

• The WFS/FES SWG subdivided all change requests into corrigendum fixes and changes requiring a new x.y (rather than x.y.z) document version

• The corrigendum fixes have been completed and accepted by the SWG voting members– A document and schema bundle has been set to the TC chair– The documents are WFS 1.1.1, WFS 2.0.2 and FES 2.0.2

• The remaining set of change requests will be addressed in new versions of the WFS and FES standards– Currently targeted as 2.X but may become 3.0– Will be decided as we review the drafts

• The SWG still accepting late-posted CRs but there is a process …


OGC®

Document statusDocument status

• For the x.y versions (2.X or maybe 3.0) …• All change requests have been reviewed and either

accepted or rejected• Accepted change requests have are being applied to the

documents to produce review drafts of WFS 2.X and FES 2.X

• The SWG will begin reviewing these drafts shortly – next week hopefully!

• Anticipated time frame for completion by the SWG is late Sept. into Oct.– … but I have been way off before!


OGC®

Changes to 09-025r1Changes to 09-025r1


Doc No. Description Source

11-117 Add service id field to service identification section Panagiotis (Peter) A. Vretanos

11-004 Add resolution parameters to GetFeatureRequest to support visualization clients


11-040 The numberReturned parameter should be able to have the value Panagiotis (Peter) A. Vretanos

11-080 A REST binding for WFS 2.0 Panagiotis (Peter) A. Vretanos

11-087 Create new feature type capability for WFS (see 10-105 too) Panagiotis (Peter) A. Vretanos

11-099 Consider revising clause 7.6.4.1 to not make "local resolve" mandatory for all confromance classes.


11-129 Abstract test suite seems to imply that a "Simple WFS" must implement remote resolve


11-130 Local resolve should not be required for the Simple WFS conformance class.


11-152 Allow use of http URIs to identify CRS Simon Cox

11-177 Implemenation of required valueOf() function will reduce query/filter efficiency.


OGC®

Changes to 09-025r1Changes to 09-025r1



12-149 Allow DescribeFeatureType to reference an existing schema rather than generate an explicit schema document


12-150 Decouple the query model from the presenation model Panagiotis (Peter) A. Vretanos

13-022 Support batch modifications (as opposed to Transactions) Panagiotis (Peter) A. Vretanos 13-034 WFS Add support for unit of measure conversions Josh Vote

13-035 Allow client to control which features in a join query are presented in a response


13-061 Do not make GML a "mandatory" output format. Panagiotis (Peter) A. Vretanos

13-062 Add support for asynchronous execution of operations Panagiotis (Peter) A. Vretanos

13-064 Corrections and simplifications in the Basic WFS conformance class Clemens Portele

13-110 Invalid MIME types for GML output format Pedro Goncalves

XX-XXX Extend resultType to allow of feature id's to be returned. Panagiotis (Peter) A. Vretanos

14-045 Offer an Optional StoredQuery in WFS 2.0 for Supporting Filter 1.1 Requests

Gobe Hobana (OWS-10)

OGC®

Changes applied to 09-026r1Changes applied to 09-026r1



11-057 DWithing corrigendum document David Burggraf

11-068 Change title of AnyInteracts temporal operator to TIntersects Debbie Wilson

11-141 Consistent handling of operators in Filter capabilities document Panagiotis (Peter) A. Vretanos

12-012 The matchAction parameter should exist on more than the comparison ops.


12-038 Broaden definition of fes:AbstractProjectionClause Jeroen Dries

12-136 Circle reference in Filter.xsd Magnus Karge

12-173 Make first operand of binary spatial operators optional and change it to fes:expression

Timo Thomas

13-006 Support for Semantics in OGC Filters Gobe Hobona

13-010 Add advanced text searching operators PropertyMatches and PropertyContains


OGC®

Comments from the roomComments from the room

• There was some concern raised about the fact that the next version of the WFS standard might be 3.0– Peter: the working version number up to this point in the SWG has

been 2.X– Peter: <with emphasis> the working next version is 2.X and it will

probably remain that way; Peter only raised the “3.0” version because of the number of changes that have been applied to the document; the SWG will need to make a determination; personal opinion is that we are not at a 3.0 version yet

– Peter: the biggest change in the document is the REST binding; this does not add any NEW functionality; it just offers a different way of executing the current capabilities of WFS 2.0 and so this does not rise to the level of a 3.0


OGC®

Comments from the room…Comments from the room…

• Why a new version of WFS so soon? … some of us are just now starting to implement WFS 2.0– Peter: Well, the current version has been out for 5 years so I am not

sure that this is “soon”– Peter: There is a rather large volume of CR’s already; waiting any

longer only adds to the pile which make the process of upgrading the documents even harder

– Peter: Some of the changes are rather large – eg REST binding – so that provides even more impetus to deal with them now rather than wait for even more big changes to roll in


OGC®

Comments from the room …Comments from the room …

• OK, so what version should people standardize on?– Peter: There is always lag between the latest version and the one

being most used out in the wild– Peter: Many factors go into making a decision about which version

to settle on – not the least of which is the availability of CITE tests; if this is important then settle on version 2.0

– Dave: what about if we want the REST binding for 2.0?– Peter: That is what the REST CR is about – adding a REST binding

to 2.0; that is not the only change being applied and so the document number is most likely going to 2.X; it is not the REST binding that is driving the version number change as much as the other CRs that are requesting functional modifications


OGC®


• What about backward compatibility?– Peter: The corrigendum documents should be 100% compatible– Peter: The SWG has tried to be as careful as possible with the 2.X

version to be as backward compatible as possible.– Ben: Some of the CR’s are requested behaviour changes and small

functional additions that may not be backward compatible (Peter agreed)

– Peter: So far, all the WFS and FES examples from V2.0 validate with the changes made to WFS/FES 2.X

– Peter: Also, this is why we have version negotiation so that clients and servers can negotiate a compatible version


OGC®


• Some questions about the modularity of the specification– Peter: the WFS/FES standards are modular in the sense that

requirements are grouped into conformance classed and there are corresponding tests

– Peter: there is only one mandatory conformance class – Simple WFS. The remaining classes are optional

– Peter: The specification is not modular in the sense that extensions are in separate documents

– Simon: There is no requirement that a modular specification be presented as separate documents!


®

Sponsored by

WFS 2.0 Conformance Test SuiteWFS 2.0 Conformance Test Suite

90th OGC Technical Committee

Washington, DC

Richard Martel, Galdos Inc.(presented by Panagiotis (Peter) A. Vretanos)

11 June 2014Copyright © 2014 Open Geospatial ConsortiumCopyright © 2014 Open Geospatial Consortium

OGC®

General statusGeneral status

© 2014 Open Geospatial Consortium, Inc. 15

• Welcome page for WFS test suite is here.• Current release is 2.0-r15 (r16 is imminent)• Now hosted at GitHub• Implemented conformance classes:

– Simple WFS– Basic WFS– Transactional WFS– Locking WFS– Plus tests imported from the GML 3.2 test suite covering:

• All GML application schemas

• GML application schemas defining features and feature collections

• Please report issues using the GitHub issue tracker

OGC®

Sources of test requirementsSources of test requirements


OGC®

PrerequisitesPrerequisites

• The test suite is schema-aware in the sense that the SUT does not need to support any particular app schema or to be loaded with specific test data

• However, some prerequisites must be satisfied:– The GML application schema meets the requirements of the GML

conformance class "GML application schemas defining features and feature collections" (ISO 19136, A.1.4).

– Data are available for at least one feature type advertised in the capabilities document.

– The service capabilities description contains all required elements in accord with the "Simple WFS" conformance class.


OGC®

Test executionTest execution

• TEAMengine v4: official OGC test harness (now hosted at GitHub)

• Java web application deployed in Apache Tomcat 7.0– Provides a form-based interface (for registered users)– Provides a REST API for simple programmatic test execution

• Eclipse IDE (developers)• Latest test suite releases are made available at the OGC

beta testing facility located here:– http://cite.opengeospatial.org/te2/


OGC®

Call for contributions …Call for contributions …

• What’s not tested:– Inheritance, Remote resolve, Response paging, Standard joins,

Spatial joins, Temporal joins, Feature versions, Manage stored queries

• CITE team is looking for people interested in contributing reference implementations– Especially appreciated: a transactional WFS with locking

• Either deployed as a public service or a ready-to-run VM

– Contact Luis Bermudez or Richard Martel if you are interested


OGC®


• How imminent is r16– Peter: don’t know for sure; Richard or Luis can answer that;

however, for it to be included in the slides is must be soon

• Based on the fact that a transactional server with locking is being requested does that mean that anyone offer that will get a refund?– Peter: don’t know; I think that is a TC chair question– Simon: that questions is out of scope here


®

Sponsored by

UKIAP OS Plugfest FeedbackUKIAP OS Plugfest Feedback


Geneva, Suisse

<Name(s) of presenters>

<day> June 2014


OGC®

AgendaAgenda

• UKIAP• Results


OGC®

© 2014 Open Geospatial Consortium

UKIAP 2013UKIAP 2013

• Joint Open Geospatial Consortium (OGC) - Ordnance Survey (OS) event, sponsored by Ordnance Survey

• Purpose of the Plugfest:– ensure that different products & services, based on

OGC standards, interoperate together as intended in a heterogeneous environment (in the UK).

– attain an ‘installed base maturity’ in the market by providing a reliable procedure for assuring that OGC specification-based solutions work together.

OGC®



• Tailored for the UK market• Understand basic level of interoperability

in the UK market• 2 sprints

OGC®



• Benefits to participants:– Multi-vendor Interoperability– Build confidence in OGC specifications– Build confidence in your implementation– Reinforce market claims with action– No blame environment

OGC®

UKIAP 2013 TimelineUKIAP 2013 Timeline

– Pre-response clarification teleconference: 25 Sep ’13– Responses to call for participation: 2 October 2013– Pre-sprint clarification teleconference: 3rd December

2013 (open to registered participants)– Sprint 1: 9th December 2013

• Location: Ordnance Survey headquarters

– Sprint 2: 3rd March 2014• Location: Ordnance Survey headquarters


OGC®

UKIAP 2013 Sprint 1UKIAP 2013 Sprint 1

• Sprint 1 included participants from:

Astun Technology

British Geological Survey

Cadcorp

Envitia

Helyx

Intergraph

Magellium

Met Office

Pyxis

Esri UK

Snowflake Software


OGC®

UKIAP 2013 Sprint 2UKIAP 2013 Sprint 2

• Sprint 2 included participants from:Astun Technology

British Geological Survey

Cadcorp

Envitia

Helyx

Intergraph

Met Office

Pyxis

Esri UK

Snowflake Software

LinkNode

Dstl

OS


OGC®


• Deliverables:– Sprint1:

• Obfuscated Engineering Report (ER)– internal usage (OGC SWG)

– Sprint2: • Public Engineering Report

• Public Best practice / Recommendations Report– Lesson's learnt

– Guidance document for policy / decision making


OGC®

TestplanTestplan


Similar to Sprint1

More detail

Degrees of freedom

OGC®

Agenda for todayAgenda for today


8:30 Coffee

9:00 Introduction (Bart & Peter)

9:15 GML

11:00 WMS

12:00 -12:30 – Lunch

12:30 WMTS

15:00 Snack

15:15 WFS

17:00 Pizza

17:30 Results presentation / discussion

OGC®

ParticipantsParticipants


OGC®

WFSWFS

• 4 services• 10 clients

• Draft outcomes– Service protected

• API Key

• URL refurer

– Schema validation errors– GML SF L0 was displayed fine– Issue mapping ComplexFeatureType to SimpleFeatureType – Complex schema, vanilla client can not interpret the richness

• But do not crash


OGC®


• Bart: The problems encountered with WFS were not because of the standard but rather the implementations and specifically XML validation issues.

• Peter: Confirmed that the same problems were encountered in the Christchurch Plugfest; in that case post-processing sed/awk/perl scripts were used to correct the errors


®

Sponsored by

OWS10 – Service IntegrationOWS10 – Service Integration(including WFS)(including WFS)

NOT PRESENTED DUE TO LACK OF TIMENOT PRESENTED DUE TO LACK OF TIME


Geneva, Suisse


11 June 2014


OGC®

AgendaAgenda

• The session ran out of time before getting to this presentation; included here for reference.

• Introduction• Use cases

– Cataloging use cases– Client use cases

• Design considerations• Web Integration Service• GetAssociations operation• Common set of identifiers• CSW-ebRIM package for service integrations• Service identification


OGC®

IntroductionIntroduction

• OGC services currently exist in isolation– There is no mechanism that allows the client of a set of OGC web

services to discover the associations or linkages between the resources served by these services.

• The idea for this work item is to define the additional components for better integration among OGC services

• Service integration must happen at a couple of levels:– Directly between clients and services

• e.g. A client should be able to directly interrogate a service about the associations that it is aware of

– Using a catalogue• e.g. A catalogue harvests the capabilities document of a service plus all

the associations the service is aware of and makes all that information discoverable via the CSW query API


OGC®

Cataloguing use casesCataloguing use cases

• Service identification– Need a reliable way to identify a service instance

• Service auto-discovery– Need the ability to discover the set of OGC services available at an

endpoint

• Service harvesting– A catalogue can harvest an OGC web service, the data it offers and

also all associated OGC and non-OGC resources

• Rich discovery– Ability to find a resource in a catalogue and then follow the chain of

associated resources– e.g. WFS feature type WMS layer that renders that data as a map

WMTS layer that has a tiled version


OGC®

OWS Context use casesOWS Context use cases

• An OWS Context document conveys a list of resources• It passes the context of a given application:

– Spatial area– Time range– Set of services and their configuration

• Each resource can have different representations and access points (e.g. WMS, WFS …)– Need a common way of establishing relations or associations

between resources


OGC®

Client use casesClient use cases

• Efficient navigation– Given a map layer, find a WMTS layer that might be used instead

• Rendering use case– Given a WFS feature type or WCS coverage, find a WMS/WMTS

layer that renders that same data as a map

• Cascading use case– Let a client decide to bypass the cascading service and access the

source service directly

• Data download– Allow a client to interactively create a map and then, by interrogating

the services used to render the map be able to download the underlying source data for the map


OGC®

Design considerationsDesign considerations

• Evolutionary refinement– Substantial resource expended by OGC and members to define and

implement the current suite of services– Thus, a primary requirement is that the solution work within the

context of existing OGC Web Services– To the extent possible solutions should reuse existing structures (e.g.

capabilities document)

• Auto-discovery– Automated discovery of OGC services at a specified endpoint– 1st attempt was OGC 11-079 using RSS auto-discovery; ignored!

• Auto-description– OGC services are already partially self-describing (i.e. capabilities)– Need to enhance this self-describing capability to include known

associations


OGC®

Design considerationsDesign considerations

• Common set of identifiers for service types, offerings, association types, etc.

• Catalogue harvesting– Extended and automate harvesting of all this information – Extended harvesting provides necessary information for richer

discovery of linked OGC and non-OGC resources • (i.e. big step towards the whole linked data thing!)


OGC®

Service identificationService identification

• For the purpose of catalogue harvesting it would be very useful to have a reliable, unique service identifier for each service instance– This allows the catalogue to determine that two services are in fact

the same service even if they are arrived at through different paths

• The proposal is to modify the ServiceIdentification section in OWS common to include a “ServiceId” element whose value is a UUID


<ServiceIdentification> <Title>OGC Member WFS</Title> <Abstract>Web Feature Service ...</Abstract> <Keywords> … </Keywords> <ServiceType>WFS</ServiceType> <ServiceId>urn:uuid:8294d348-1500-4c99-8935-78faf729709e<ServiceId> <ServiceTypeVersion>2.0.0</ServiceTypeVersion> <Fees>NONE</Fees> <AccessConstraints>NONE</AccessConstraints></ServiceIdentification>

OGC®

Service auto-discoveryService auto-discovery

• Introduce the Web Integration Service (WIS)• An aggregation service that provide a list OGC web service

available at an endpoint • The WIS implements a single operation – GetCapabilities• The response to this operation is a standard OGC

capabilities document with a new content section• A new “Service” element is defined that describes one

offered service– The “Service” element contains the GetCapabilities baseURL of the

service and a standard OWS common ServiceIdentification section describing the service

• Example: "http://www.provider.com/wis?service=WIS&request=GetCapabilities"


OGC®

Service auto-descriptionService auto-description

• Already have GetCapabilities … need more!• Each OGC service has internal association knowledge

– e.g. a WMS knows if the source data of a layer it offers is a SHAPE file, or a WFS feature type, or another WMS (i.e. cascading), of if there is a WMTS layers that renders the same information, etc.

• The trick is to get the service to externalize this internal knowledge via a new operation called GetAssociations

• A client can invoke this request to discover all the associations that a server knows about

• Example: "http://www.someprovider.com/wms?service=WMS&version=1.3.0&request=GetAssociations&outputFormat=text/xml"


OGC®

Common set of identifiersCommon set of identifiers


Service HTTP-URI

WIS http://www.opengis.net/def/objectType/0/wis

WFS http://www.opengis.net/def/objectType/ogc/0/wfs

WMS http://www.opengis.net/def/objectType/ogc/0/wms

WMTS http://www.opengis.net/def/objectType/ogc/0/wmts

WPS http://www.opengis.net/def/objectType/ogc/0/wps

WCS http://www.opengis.net/def/objectType/ogc/0/wcs

CSW http://www.opengis.net/def/objectType/ogc/0/csw

WRS http://www.opengis.net/def/objectType/ogc/0/wrs

GSS http://www.opengis.net/def/objectType/ogc/0/gss

Service type identifiersService type identifiers

OGC®



Service HTTP-URI

WFS Feature Type http://www.opengis.net/def/objectType/ogc/0/wfs/featureType

WMS Theme http://www.opengis.net/def/objectType/ogc/0/wms/theme

WMS Layers http://www.opengis.net/def/objectType/ogc/0/wms/layer

WMTS Theme http://www.opengis,net/def/objectType/ogc/0/wmts/theme

WMTS Layer http://www.opengis.net/def/objectType/ogc/0/wmts/layer

WPS Process http://www.opengis.net/def/objectType/ogc/0/wps/process

WCS Theme http://www.opengis.net/def/objectType/ogc/0/wcs/theme

WCS Coverage http://www.opengis.net/def/objectType/ogc/0/wcs/coverage

Description http://www.opengis.net/def/objectType/ogc/0/description

Dublin Core http://www.opengis.net/def/objectType/dublincore/metadata

Symb. Enc. Doc. http://www.opengis.net/def/objectType/dublincore/symbologyEncodingDocument

Content identifiersContent identifiers

OGC®



Service HTTP-URI

Renders http://www.opengis.net/def/associationType/ogc/0/renders

TiledBy http://www.opengis.net/def/associationType/ogc/0/tiledBy

ParentOf http://www.opengis.net/def/associationType/ogc/0/parentOf

Cascades http://www.opengis.net/def/associationType/ogc/0/cascades

CreatedBy http://www.opengis.net/def/associationType/ogc/0/createdBy

Symbolizes http://www.opengis.net/def/associationType/ogc/0/symbolizes

Association type identifiersAssociation type identifiers

OGC®

Automated catalogue harvestingAutomated catalogue harvesting


• Catalogues already harvest OGC Catalogues already harvest OGC capabilities documents … need morecapabilities documents … need more

• Catalogues should be able to automatically Catalogues should be able to automatically harvest associations between registered harvest associations between registered OGC and non-OGC resourcesOGC and non-OGC resources

• An ebRIM package for service integration is An ebRIM package for service integration is defined to support automated catalogue defined to support automated catalogue harvestingharvesting

OGC®

CSW-ebRIM pkg for service integrationCSW-ebRIM pkg for service integration

• A new ebRIM package is defined to support representation of linked resources & discovery within CSW-ebRIM

• The package includes the following definitions– Object types: WFS Feature Type, WMS Layer, WMS Theme, WMTS

Layer, WMTS Theme, Dataset Description, Symbology Encoding Document, SLD, Unknown

– Harvestable resources: wcs, wfs, wms, wmts, FGDC, ISO19139, ANZLIC, XML Schema, Symbology Encoding, ebRIM Classification Scheme

– Association types: Renders, TiledBy, ParentOf, Cascades, CreatedBy, Symbolizes,

– Slot names: baseURL, crs, hasRepositoryItem, keyword, oututFormat, resourceType, reverseAssociationTitle, spatialPropertyName, where, title, url


OGC®

CSW-ebRIM pkg for service integrationCSW-ebRIM pkg for service integration

• These definitions can be used in conjunction with the GetAssociations request to harvest an OGC resource and all its linked resources into the catalogue

• This makes these resources discoverable via the CSW query API– CSW API now includes the OpenSearch API

• The ER also describes how to map OGC capabilities documents and GetAssociations responses into the ebRIM model


OGC®

Engineering reportEngineering report

• OWS-10 Service Integration engineering report is publically available here.


® sponsored by agenda for wfs/fes swg meeting 91st ogc technical committee geneva, suisse...

Documents