SqlSpec for SQL 200 6.3 serial key or number

Sorry if I lured you into the mood of having a sip of a wonderful cocktail made with rum and you realized that the RUM I’m talking about is not the rum you are craving. But, be assured that Elastic RUM is equally wonderful! Let’s take a sip! I do want to warn you that it will take a bit of time to go through the amount of detail I will cover in this blog!

What is RUM?

Elastic real user monitoring captures user interactions with the web browser and provides a detailed view of the “real user experience” of your web applications from a performance perspective. Elastic’s RUM Agent is a JavaScript Agent, which means it supports any JavaScript-based application. RUM can provide valuable insight into your applications. Some of the common benefits of RUM include:

• RUM performance data can help you identify bottlenecks and discover how site performance issues affect your visitors’ experience
• User agent information captured by RUM enables you to identify the browsers, devices, and platforms most used by your customers so that you can make informed optimizations to your application
• Together with location information, individual user performance data from RUM helps you understand regional performance of your website worldwide
• RUM provides insight and measurement for your application’s service level agreements (SLA)

Getting started with RUM using Elastic APM

In this blog, I will take you through the complete process of instrumenting a simple web application made of a React frontend and a Spring Boot backend, step by step. You will see how easy it is to use the RUM agent. As a bonus, you will also see how Elastic APM ties the frontend and the backend performance information together with a holistic, distributed trace view. Please see my previous blog for an overview of Elastic APM and distributed tracing if you are interested in knowing more details.

To use Elastic APM real user monitoring, you have to have the Elastic Stack with APM server installed. You can of course download and install the latest Elastic Stack with APM server locally on your computer. However, the easiest approach would be creating an Elastic Cloud trial account and have your cluster ready in a few minutes. APM is enabled for the default I/O Optimized template. From now on, I’ll assume you have a cluster ready to go.

Sample application

The application we are going to instrument is a simple car database application made of a React frontend and a Spring Boot backend that provides API access to an in-memory car database. The application is purposely kept simple. The idea is to show you detailed instrumentation steps starting from zero so that you can instrument your own applications following the same steps.

Create a directory called anywhere on your laptop. Then clone both the frontend and the backend application into that directory.

git clone https://github.com/adamquan/carfront.git git clone https://github.com/adamquan/cardatabase.git

As you can see, the application is extremely simple. There are only a couple of components in the React frontend and a few classes in the backend Spring Boot application. Build and run the application following the instructions in GitHub for both the frontend and backend. You should see something like this. You can browse, filter cars, and perform CRUD options on them.

Amazed by how much information is captured by the RUM agent by default? Pay special attention to the markers like , , and . Mouse over the black dots to see the names. They provide you with great details about content retrieval and browser rendering of these contents. Also pay attention to all the performance data about resource loading from the browser. By just initializing your RUM agent, without any custom instrumentation, you get all these detailed performance metrics, out of the box! When there is a performance issue, these metrics enable you to easily decide whether the issue is due to slow backend services, a slow network, or simply a slow client browser. That is very impressive!

For those of you who need a refresher, here is a quick explanation of the web performance metrics. Do keep in mind that for modern web application frameworks like React, these metrics might only represent the “static” part of the web page, due to the async nature of React. For example, dynamic contents might still be loading after domInteractive, as you will see later.

• timeToFirstByte is the amount of time a browser waits to receive the first piece of information from the web server after requesting it. It represents a combination of network and server-side processing speed.
• domInteractive is the time immediately before the user agent sets the current document readiness to “interactive,” which means the browser has finished parsing all of the HTML and DOM construction is complete.
• domComplete is the time immediately before the user agent sets the current document readiness to “complete,” which means the page and all of its subresources like images have finished downloading and are ready. The loading spinner has stopped spinning.
• firstContentfulPaint is the time the browser renders the first bit of content from the DOM. This is an important milestone for users because it provides feedback that the page is actually loading.

Flexible custom instrumentation

The RUM agent provides detailed instrumentation for your browser interaction out of the box, as you just saw. You can also perform custom instrumentations when needed. For example, because the React application is a single-page-application and deleting a car will not trigger a “page load,” RUM does not by default capture the performance data of deleting a car. We can use custom transactions for something like that.

With our current release (APM Real User Monitoring JavaScript Agent 4.x), users have to manually create transactions for AJAX calls and Single-Page-Application (SPA) calls that do not trigger a page load. In some frameworks, like JSF, you have very little control over the JavaScript. So, manually creating transactions for button clicks which initiate AJAX requests is not viable. Even if the developer has direct control over the AJAX requests, instrumenting a big application would be a lot of effort. We are planning to enhance the RUM agent so that it will automatically create a transaction for these requests in case there is not an active one currently. This would make the auto-instrumentation cover a lot more of the application without developers having to programmatically add tracing logic to their applications.

The "New Car" button in our frontend application allows you to add a new car to the database. We will instrument the code to capture the performance of adding a new car. Open the file in the components directory. You will see the following code:

// Add new car addCar(car) { var transaction = apm.startTransaction("Add Car", "Car"); var httpSpan = transaction.startSpan('Add Car', 'Car') apm.addTags(car); fetch(SERVER_URL + 'api/cars', { method: 'POST', headers: { 'Content-Type': 'application/json', }, body: JSON.stringify(car) }) .then(res => this.fetchCars()) .catch(err => console.error(err)) httpSpan.end() transaction.end(); }

The code basically created a new transaction and a new span called “Add Car” of “Car” type. Then, it tagged the transaction with the car to provide contextual information. The transaction and span ended at the end of the method.

Add a new car from the application web UI. Click on the APM UI in Kibana. You should see an “Add Car” transaction listed. Make sure you select “Car” in the “Filter by type” dropdown. By default, it displays “page-load” transactions.

Click on the “Tags” tab. You will see the tags we added. Tags and logs add valuable contextual information to your APM traces.

See the big picture with distributed tracing

As a bonus point, we are going to also instrument our backend Spring Boot application so that you have a complete view of the overall transaction from the web browser all the way to the backend database, all in one view. Elastic APM distributed tracing enables you to do so.

Configuring distributed tracing in RUM agents

Distributed tracing is enabled by default in the RUM agent. However, it only includes requests made to the same origin. In order to include cross-origin requests you must set the configuration option. You will also have to set the CORS policy in the backend application, as we will discuss in the next section.

For our application, the frontend is served from http://localhost:3000. To include requests made to http://localhost:8080, we need to add the configuration to our React application. This is done inside . The code is already there. Simply uncommenting the line will do.

var apm = initApm({ ... distributedTracingOrigins: ['http://localhost:8080'] })

This effectively tells the agent to add the distributed tracing HTTP header () to requests made to http://localhost:8080.

To use the default instrumentation out of the box on the server side, you need to download the Java agent and start your application with it. Here is how I configured my Eclipse project to run the backend Spring Boot application. You will have to configure this using your own APM URL and APM token.

-javaagent:/Users/aquan/Downloads/elastic-apm-agent-1.4.0.jar -Delastic.apm.service_name=cardatabase -Delastic.apm.application_packages=com.packt.cardatabase -Delastic.apm.server_urls=https://aba7c3d90b0b4820b05b0a9df44c096d.apm.us-central1.gcp.cloud.es.io:443 -Delastic.apm.secret_token=jeUWQhFtU9e5Jv836F

For readers who are really paying attention to the timeline visualization above, you might be wondering why the “Car List” page-load transaction ends at 193 ms, which is the domInteractive time, while data is still being served from the backend. Great question! This is due to the fact that the fetch calls are async by default. The browser “thinks” it finished parsing all the HTML and DOM construction is complete at 193 ms because it loaded all the “static” HTML contents served from the web server. On the other hand, React is still loading data from the backend server asynchronously.

Cross-origin resource sharing (CORS)

The RUM agent is only one piece of the puzzle in a distributed trace. In order to use distributed tracing, we need to properly configure other components too. One of the things that you will normally have to configure is cross-origin resource sharing, the “notorious” CORS! This is because the frontend and the backend services are typically deployed separately. With the same-origin policy, your frontend requests from a different origin to the backend will fail without properly configured CORS. Basically, CORS is a way for the server side to check if requests coming in from a different origin are allowed. To read more about cross-origin requests and why this process is necessary, please see the MDN page on Cross-Origin Resource Sharing.

What does that mean for us? It means two things:

1. We must set the configuration option, as we have done.
2. With that configuration, the RUM agent also sends an HTTP OPTIONS request before the real HTTP request to make sure all the headers and HTTP methods are supported and the origin is allowed. Specifically, http://localhost:8080 will receive an OPTIONS request with the following headers:
   
   Access-Control-Request-Headers: elastic-apm-traceparent Access-Control-Request-Method: [request-method] Origin: [request-origin] And APM server should respond to it with these headers and a 200 status code:
   
   Access-Control-Allow-Headers: elastic-apm-traceparent Access-Control-Allow-Methods: [allowed-methods] Access-Control-Allow-Origin: [request-origin]

The class in our Spring Boot application does exactly that. There are different ways of configuring Spring Boot to do this, but here we are using a filter based approach. It’s configuring our server-side Spring Boot application to allow requests from any origin with any HTTP headers and any HTTP methods. You may not want to be this open with your production applications.

@Configuration public class MyCorsConfiguration { @Bean public FilterRegistrationBean<CorsFilter> corsFilter() { UrlBasedCorsConfigurationSource source = new UrlBasedCorsConfigurationSource(); CorsConfiguration config = new CorsConfiguration(); config.setAllowCredentials(true); config.addAllowedOrigin("*"); config.addAllowedHeader("*"); config.addAllowedMethod("*"); source.registerCorsConfiguration("/**", config); FilterRegistrationBean<CorsFilter> bean = new FilterRegistrationBean<CorsFilter>(new CorsFilter(source)); bean.setOrder(0); return bean; } }

Let’s close the blog with one more powerful feature of the RUM agent: source maps. Source maps make debugging errors with your application much easier by telling you exactly where the error happened in your original source code, instead of the cryptic minified code.

Easy debugging with source maps

It is a common practice to minify JavaScript bundles for production deployment, for performance reasons. However, debugging minified code is inherently difficult. The screenshot below shows an error message captured by the RUM agent for a production build. As you can see, the exception stack trace does not make much sense, because it’s minified code. All the error lines show javascript files like , and it always points to “line 1” because of the way minification was done. Wouldn’t it be nice if you could see exactly your source code as you developed it here?

Summary

Hopefully this blog made it clear that instrumenting your applications with Elastic RUM is simple and easy, yet extremely powerful. Together with other APM agents for backend services, RUM gives you a holistic view of application performance from an end user perspective through distributed tracing.

Once again, to get started with Elastic APM, you can download Elastic APM server to run it locally, or create an Elastic Cloud trial account and have a cluster ready in a few minutes.

As always, reach out on the Elastic APM forum if you want to open up a discussion or have any questions. Happy RUMing!

https://www.elastic.co/blog/performing-real-user-monitoring-rum-with-elastic-apm

Document Title (click to download)VersionDocument #EditorDate[WMS SWG] resourceType is not extendable in WMTS  1 15-015 Joan Maso 2015-03-12The WMTS simple profile is defining new types of resourceType such as: "simpleProfileTile" and "simpleProfileCRS84Tile" but they to not validate with the current WMTS schemas.Enhanced Text Placement 1 14-117 Randoplph Gladish 2015-03-12KML has been selected as a common overlay standard across multiple systems, as a means to convey overlay graphics and symbology to coalition partners and foreign governments. Originating systems using both Freehand Graphics and MILSTD 2525 encode and display graphical symbology that is not rendered correctly in KML. Text rendering and placement in KML 2.2 is insufficient to support representation of MILSTD 2525 A/B/C/D and NATO APP 6C textual modifiers that require multiple, disconnected text to be rendered at specific locations relative to corresponding line rendering. Freehand graphics are drawn with labels located in specific positions relative to graphic overlay. The placement of multiple text regions in the above symbology standards, and within communities of interest has very specific meaning to experienced consumers of this symbology, relative to accompanying geometry. Non-optimal yet acceptable workarounds exist for text rendered within a point symbol rendering using raster encoded text, but no acceptable workarounds exist for symbols known as â��tactical graphicsâ��. Tactical graphics, as illustrated in MILSTD 2525C, Appendix B, Table B-IV, contain one or more control points with straight or curved lines or polygons drawn in specific patterns relative to the control points, with various text embedded within the tactical graphic at specific locations to convey additional information (known as text modifiers or amplifying text). Representative symbols that illustrate the text placement needs of MILSTD 2525 are provided below. This list is not exhaustive, but provides examples of text placement and proximity to symbol geometry. Text Placement exemplars from MILSTD 2525C Table B-IV include the following representative Symbol Identifiers: TACGRP.TSK.BLK TACGRP.TSK.FIX TACGRP.TSK.FLWASS TACGRP.TSK.RIP TACGRP.C2GM.GNL.LNE.BNDS TACGRP.C2GM.GNL.LNE.LOC TACGRP.C2GM.GNL.LNE.PHELNE TACGRP.C2GM.GNL.LNE.LITLNE[GML SWG] Change for Accessing SensorML 2.0 elements from GML 3.3 1 15-013 sjaak derksen 2015-03-12Currently, binding files are required to enable code Java code generation. The need for such binding file arises from the fact that some elements within GML only differ in the way they use capitals. Examples include: * elipsoid and Elipsoid (datums.xsd) * cartisianCS and CartesianCS (coordinateReferenceSystems.xsd)[WMS SWG] wmtsGetCapabilities_response.xsd  1 15-006 ï¿¼Krzysztof Fink-Finowi 2015-03-12 should read: Alternate Encoding of KML using EXI 1 14-118 Randoplph Gladish 2015-03-12XML is an inefficient text encoding standard (relative to traditional binary encoding). An alternative encoding of KML content is desirable to conserve storage space and transmission bandwidth, particularly as mobile delivery and display becomes increasingly common, and to leverage deferred resource loading strategies available in KML. KMZ provides a mechanism to address inefficient encoding formats such as KML and COLLADA, but places additional processing resource burdens on systems to decompress and manage content into temporary files. Addition of an efficient, native binary encoding will better support bandwidth and resource constrained computing environments that can leverage deferred resource loading. Issues with KMZ compressed KML: â�¢ Expansion of KMZ requires decompression algorithms on the receiving system or server. â�� Relative paths must be resolved to correct web URL â�� Expansion of KMZ components requires file handling that may be difficult or resource intensive for some systems. â�¢ Compressed KML must be fully expanded to access individual DOM elements within embedded KML/XML files, even though not all elements are required for visualization. EXi is binary equivalent form of XML encoding that has been defined by W3C as a more space and transmission efficient binary variation of XML. EXi offers advantages over compressed (KMZ). Due to the highly repetitive nature of KML content, EXi offers significant encoding and transmission efficiency without the drawbacks of compressed XML. See supporting documentation below).[KML SWG] SVG Rendering Support 1 14-120 Randoplph Gladish 2015-03-12KML rendering of 2D line and area geometries is limited to a relatively simple set of style properties. KML does not support complex line decoration styles, which is often used to convey meaning beyond color and line width. Extensions to support dashed line styles and fill pattern styles have been proposed for KML 2.4, but are ultimately inadequate to address complex rendering decorations present in symbolized linear and areal placemarks. Demarcation lines, weather fronts and other domains attribute special meaning using complex line decorations. Extended geometry styling support would allow KML to more compactly encode presentation without adding unnecessary spatial geometry to reproduce repetitive styling patterns such as railroad tracks or weather fronts. Existing standards, such as Scalable Vector Graphics (SVG)and OGC Symbology Encoding (SE), or portions thereof, could be used to extend the styling capabilities of KML. Instead of icons limited to PNG files, SVG or SE could be rendered at a prescribed scale and orientation.[OWS Common SWG] Recommend implicitly the use of the HTTP header Link defined in RFC 5899 1 14-098 Francisco J. Lopez-Pellicer 2014-09-18Linking is at the core of the Web. OGC should provide a solution for data linking valid for REST-based services, but, at the same time, backward compatible with KVP and SOAP services. The use of the HTTP header Link defined in RFC 5899 is a transparent solution for embedding links in HTTP response headers that is transparent at the application level and thus backward compatible. In addition, the support of RFC 5899 by search engines such as Google for indexing the preferred version of a resource offers an opportunity for easing the discoverability of OWS services (KVP, SOAP, REST) in search engines.[WFS/FES SWG] Consistency in the returned collection class 1 14-097 Gobe Hobona 2014-09-18The WFS-G BP specifies that the top level container should be an iso19112:SI_Collection element but then gives an example that uses a wfs:FeatureCollection element.[Semantics] RFC 5899 as alternative for a unique annotation element in OGC core schemas in some scenarios 1 14-090 rancisco J. Lopez-Pellicer 2014-09-15RFC 5899 offers a standard and harmonised way to annotate semantically resources in some scenarios without requiring the modification of existing OGC core schemas because it operates at the protocol level. RFC 5899 enables two cases for the implementation of semantic annotations in exchanged messages: annotations in entity headers (Link headers) and annotation in entity bodies (several ways). The main difference is that Link headers are annotations about the whole resource that the exchanged message is about (e.g. WFS Service metadata, data model encoded in XML schema, resultset encoded in the format predefined by a data schema). The best practices document describes semantic annotations in entity bodies but does not deal with annotations in entity headers. Changes should address how and when should be added these annotations at the protocol level (KVP, XML, REST and SOAP).[NetCDF SWF] Unresolvable PURLs in NetCDF Primer 1 14-071 Chris Calloway 2014-08-07http://www.opengeospatial.org/standards/netcdf lists documents for OGC network Common Data Form (netCDF) standards suite. One of them is http://portal.opengeospatial.org/files/?artifact_id=43733 , CF-netCDF Core and Extensions Primer, OGC document 10-091r3. On the title page, the document is listed at http://www.opengis.net/doc/IS/netcdf/Primer/1.0 . That PURL is broken. In section 7.1.2 of the document, the document is listed at http://www.opengis.net/doc/primer/cf- netcdf/1.0 . That PURL is also broken.[WMS1.4 SWG] DescribeLayerResponse should report feature type names by layer names 1 14-076 Reinhard Erstling 2014-08-0705-078r4 in section 8.3 reads: "For each named layer, the description should indicate the WFS/WCS (by a URL prefix) and the feature/coverage types." Though the DescribeLayer request permits to specify a list of layers and though the DescribeLayerResponse provides for a "LayerDesciption" element, which can occur more than once in the response, there is no element available in the "LayerDescription" which could carry the layer name.[Geopackage SWG] Change WKT for SRS citation from 01-009 to 12-063 1 14-078 Paul Daisey 2014-08-07The WKT representation of coordinate reference systems as defined in ISO 19125-1:2004 and OGC specification 01-009 is inconsistent with the terminology and technical provisions of ISO 19111:2007 and OGC Abstract Specification topic 2 (08-015r2), âô€€ô€€Geographic information âô€€ô€€ Spatial referencing by coordinatesâô€€ô€€.[CityGML SWG] Integration of the horizontal and vertical geometric references in the metadata of LOD1 and LOD2, and adoption of INSPIRE references 1 14-075 Filip Biljecki 2014-08-07The geometry of individual buildings in LOD1 and LOD2 may be represented in a multitude of valid forms within the same LOD. For instance, the top of a LOD1 building may represent the highest point of walls or the height of the eaves. Both in LOD1 and LOD2 the footprint may represent the vertical projection of the roof edges to the ground or the actual footprint on the ground. This is strongly influenced by the acquisition technique. Because different references may cause drastic differences when used for spatial analysis, the knowledge of the geometric references is important. However, CityGML does not enable the storage of such information in the metadata.WMS1.4 SWG] Filtering Layer Capability 1 14-059 Pedro Goncalves 2014-08-07Currently the WMS getCapabilities always returns the full capability of the server (all the layers). The proposed change will allow the creation of a GetCapabilities request that return only a given sub-set of the layers.[WMS1.4 SWG] WMS Change request - Add optional resolution parameter 1 14-072 Arnulf Christl 2014-08-07The current WMS specification is limited to a 72dpi resolution and can therefore not be used as source for digital printouts. Adding a rsolution parameter would allow to request more pixel per feature allowing for much higher quality in printed material.[OWSContextSWG] Extensible Support for Annotations in OWS Context 1 14-054 Gobe Hobona 2014-08-07The BIIF profile of CGM (BPCGM) is used as the annotation model for digital imagery in military standards such as STANAG 4545, (U.S.) MIL-STD-2500, and (U.S.) MIL-STD-2301A. That is, BPCGM is the annotation model used by the widely supported NITF imagery format.[WMS1.4 SWG] Associations between resources 1 14-053 Gobe Hobona 2014-08-07The conceptual model does not explicitly provide a \'has-a\' association between Resources. Such associations could be useful for building hierarchical resources (e.g. parent-child layers in WMS). Providing such an association could provide logical groupings of resources, thereby improving usability.[WMS1.4 SWG] Styling GetFeatureInfo responses 1 14-060 Gobe Hobona 2014-08-07Although the standard allows for GetFeatureInfo to return responses in different encodings, it however relies on a separate service such as WPS or a client application to transform the responses (e.g. for different HTML styling). The main use case for this proposed capability is provision of shared situational awareness in a multi-agency/multi-WMS environment.[CityGML SWG] Develop a mechanism for parameterized implicit geometries. 1 14-047 Steve Smyth 2014-04-23There are two primary reasons for extending or replacing the existing facility for implicit geometries in CityGML: 1. More flexibility in creating standard furniture and installations can extend the range of geometries that can be incorporated in models by reference, rather than via a copy of the geometry. Using references can greatly reduce the size of models. In version 2.0 entities like road signs, trees, and balustrades can only be transformed by scaling, rotation, and translation. More flexible transformations will enhance compactness. 2. Procedural definition of geometries is one of the most general methods for defining transformations of inputs to produce arbitrarily complex geometries. Procedural methods can express extruded footprint volume and CSG representations used by related approaches to modelling the built environment. Procedurally-defined implicit geometries may provide a mechanism for better interoperability with IFC. Procedural methods offer the possibility of both compactness and enhanced interoperability.[WFS/FES SWG] Offer an Optional StoredQuery in WFS 2.0 for Supporting Filter 1.1 Requests 1 14-045 Gobe Hobona 2014-04-23Currently the Filter 2.0 standard prevents WFS 2.0 from being backwards compatible with WFS 1.1. There is however a significant number of WFS 1.1 server and client implementations that cannot be ignored.[WMS1.4 SWG] Change data type for minTileRow etc. 1 14-046 Martin Kofahl 2014-04-23WMTS GetCapabilities document does not validate with XSD schema derived from the specification, Table 12 Parts of TileMatrixLimits data structure.[OWS Common 2.0] Remove requirement that the Operations Metadata section define a minimum of 2 operations 1 14-026 Panagiotis (Peter) A. Vretanos 2014-03-07OGC 06-121r9 did not anticipate that an OGC service could be defined with only the GetCapabilities operation. However, in the OWS-10 service integration thread a service, called a Web Integration Service, has been defined that only has one operation -- the GetCapabilities operation. This operation generates a standard OGC capabilities document and the content section contains a list of other related OGC services. See the OWS-10 Service Integration Engineering report (OGC 14-013) for more details.[order-eo1.0 swg] Include missing pages in the standard 1 14-025 Ricardo Silva 2014-03-07Pages 65 and 66 are missing from the published standard. These pages should contain table 7.11- CommonOrderSpecification description. The table is listed in the index, but cannot be found in the document body.[WMS1.4 SWG] Mandatory SERVICE parameter in GetMap and GetFeatureInfo requests 1 14-010 Hell Benjamin 2014-03-07The change would improve consistency between WMS, WMTS, WCS, WPS and WFS standards. Furthermore, it would make it easier on a web server level to rewrite service request URLs in order to use various servers to respond to different services.[order-eo1.0 swg] Add missing xs type to lastUpdateEnd element 1 14-024 Ricardo Silva 2014-03-07The body of the standard's text defines GetStatus operation with two elements that should be ISO 8601 dates (see Table 14-2): 1. filteringCriteria/lastUpdate 2. filteringCriteria/lastUpdateEnd However, in the accompanying XML Schema Document (oseo.xsd) only the first element is specified as having an xs:dateTime, while the other has no type definition (see lines 421, 413 of the oseo.xsd file)[CAT3.0 SWG] Inconsistent Manager interface definition- harvestRecords vs harvestResource 1 14-019 Kevin Gupton 2014-03-07The Manager component of a Catalogue Service is defined inconsistently. Section 7.2.1 defines Manager has having operations transaction() and harvestRecords. This term is repeated in Table 50 and in section 1.12.1. However, other sections use the term "harvestResource"- see 7.2.6.1, 7.2.6.3, Figure 15, and Tables 39, 40, 41.[WaterML2.0 SWG] Add a Composite Time Series Encoding to WaterML 2.0: Part 1 1 13-124 Jack Lindsey 2013-11-13WaterML 2.0: Part 1 provides an encoding for simple time series (i.e. a single variable recorded for each data point). While this is ideal for several use cases, it does not support the exchange of datasets containing multivariate time series (i.e. multiple variables recorded for each data point), usually referred to as composite or compound time series. However, this was found to be the most common use case for environmental monitoring groups at Environment Canada, namely air quality, water quantity, water quality, and biodiversity. This currently has to be accommodated by the use of very generic record-field structures in SWE Common Data Model.[CityGML SWG] Dynamic Properties; Improved Support for Simulations 1 13-127 Thomas H. Kolbe 2013-11-13On the one hand CityGML is a very useful and important source of information for different types of simulations, and on the other hand the results of simulations can be fed back to the original CityGML data for thematic enrichment and data fusion. However, in most simulations time plays an important role, i.e. dynamic / time-varying feature properties (spatial and thematic, e.g. electrical energy demand or production potential for a building along the course of the day / week / year), which are not yet supported in CityGML. In order to allow for tighter coupling of semantic 3D city models and simulations we suggest the following changes.[WaterML2.0 SWG] Rebrand WaterML 2.0: Part 1 as TimeSeriesML 1 13-123 Jack Lindsey 2013-11-13To repackage WaterML 2.0: Part 1 as TimeSeriesML and place its stewardship and further evolution under the guidance of a broader-based working group. Other than some of the examples, there is nothing hydrology-specific in the Part 1 specification. Rather it complements O&M and SWE Common Data Model to provide a very functional advance in OGC support for the management and distribution of time series data across multiple domains. This would further the fundamental objective of O&M to foster data exchange, comparison, and integration across disciplines and technical communities. Specifically, this is the objective of the Environment Canada Common Observation and Measurement Profile currently under development, involving data from the air quality, water quantity, water quality, biodiversity, and meteorology domains.[WFS/FES SWG] Invalid MIME types for GML output format  1 13-110 Pedro Goncalves 2013-10-22On this document we use as an example an invalid MIME type "text/xml; subtype=gml/3.2" This MIME type is invalid because the only optional parameter on text/xml is "charset" and that media type parameters cannot have "/" without quotes http://www.ietf.org/rfc/rfc2045.txthttp://tools.ietf.org/html/rfc3023#page-7 It seems that the subtype parameter name originates from a quick reading of the bnf notation that states type "/" subtype *[";" parameter] parameter := attribute "=" value so we are using the name subtype twice here these examples gave origin to different interpretations and we now start see the usage of this nonexistent subtype parameter to express the notion of profiles e.g. text/xml; subType=gml/3.1.1/profiles/gmlsf/1.0.0/0[GML DWG] Allow a GML instance document to declare adherence to a particular Simple Feature profile level 1 13-104 Peter Parslow 2013-10-16At present, only a GML application schema can declare adherence to the Simple Feature profile (to a specific level). A data set (instance document) could adhere to the profile, whilst conforming to an application schema that does not declare adherence. For example, the application schema may allow a full range of geometry types, but a specific data set only uses simple geometries. Or the application schema may allow the full range of property encodings, but a given instance may have all properties in line. (And adhere to all the other rules, like not using gml:metaDataProperty) If an instance document can declare an SF level, it may be easier for software to load that document, even if it would not be able to load all documents that conform to the schema. At present, this could be achieved (by some instance publishers) by creating a new application schema that declares SF adherence & then imports the original application schema: implicitly (?) constraining the original schema.[SF SWG] Change in BNF Productions for WKT 1 13-109 Dominik Egger 2013-10-16The specification for [GML 3.3 SWG] Addition of profile parameter to GML MIME type 1 13-105 Pedro Goncalves 2013-10-16The current usage of GML MIME types show that users/applications have the need to express the profile they are supporting For example, it is quite normal to see WFS output format to announce values like : text/xml; subType=gml/3.1.1/profiles/gmlsf/1.0.0/0 to express the support of simple features. This usage of the text/xml is invalid and breaks MIME type formatting rules so we need to support this directly on the GML MIME type Currently, in the GML MIME type we can only express the version like: application/gml+xml; version=3.1 (note: only the major and the first minor version number are supported) but it is not possible to express the profile.[CityGML SWG] Add Metadata to CityGML 1 13-097 Gerhard Gröger 2013-10-16CityGML currently lacks a standardized specification of metadata. Metadata are crucial to assess the suitability of CityGML data sets for specific applications, and to interpret spatial data. The CR 13-029 (Meta data for city model) is restricted to metadata for a whole dataset. But also metadata at the level of a single feature or even a single attribute or geometry value is required. Hence, this change request complements/generalizes CR 13-029.[CItyGML SWG] Revision of the CityGML LOD-concept 1 13-089 Joachim Benner 2013-10-16Though the CityGML LOD concept is frequently used, it has a number of severe shortcomings: 1.) Geometry/semantics: The LOD only determines a geometrical modelling style and a certain degree of geometrical correspondence between model and real object, but says nothing about the actual semantic modelling depth. 2.) Interior/exterior: The interior components of buildings or tunnels can only be modelled in one LOD, representing a geometrical model with highest accuracy (LOD4). Furthermore, a representation of interior components is only possible when simultaneously the exterior components a represented with highest geometrical resolution. These requirements hamper the usage of CityGML in many application areas like emergency responses or indoor routing (CR 215/OGC 12-044). 3.) LOD-definitions: The CityGML LODs are only defined for the Building module, but the terms LOD0 âô€€ô€€ LOD4 are used in all other thematic areas mostly without further explanation. Some examples: what is the âô€€ô€€geometrical LODâô€€ô€€ of a Land Use classification, which objects are modelled with a LOD 4 (interior) representation for a SolitaryVegetationObject or WaterBody? 4.) Completeness: The concept of a LOD0 representation (point, line, 2D or 2.5D surface geometry) is very general and useful in all thematic areas, but actually available in only some of them.[CityGML SWG] Integration of utility networks into CityGML 1 13-091 Thomas Becker 2013-10-16Currently CityGML lack a rich information model for multiple and different underground structures such as gas, power, freshwater, and wastewater utility networks. Complex analyses or simulations such as collision detection (e.g. excavator vs. pipe), determination of explosion impact determination of damaged objects), and simulations predicting, for example, the spread of water in a flood scenario above and below the ground require the 3D topographic representation and description of the components of the utility network of a city. Due to the fact that the different types of infrastructure of the city lie above and in between each other the embedding into the 3D space plays an important role. Furthermore, 3D visual inspection helps in getting a better understanding of the spatial relations of the networks relative to each other. Network analyses such as the calculation of slope or slope change becomes possible. Thus, it is conceivable that a 3-dimensional description of the city as well as a suitable 3D description of the underlying utility network has to be realized. The 3D objects of the network must be integrated into the 3D space of the city and thus they can be queried in the context of a disaster management.[CityGML SWG] add Material definition to Boundary Surfaces 1 13-096 Volker Coors 2013-10-16In simulation applications such as noise and energy demand, a detailed defintion of the used material of boundary surfaces such as Wall-, Roof-, and GrounsSurface is needed. As many applications will benefit from a standard set of attributes defining the used material of a Boundary Surface, I suggested to integrate it into the CityGML 3.0 rather than an ADE.[SWECommon SWG] DataChoice Cardinality 1 13-069 David Stuebe 2013-08-13There is no need to require a cardinality of two or more (2*) on the elements of a DataChoice field. It places an unnecessary constraint on the data model which requires a different structure for degenerate cases of a single item or the use of a dummy item to meet the requirements.[SensorWeb DWG] Add FES friendly encoding to Range data types 1 13-075 Eric Boisvert 2013-08-13Certain GeoSciML use cases require filtering on the lower ofr upper value of a QuantityRange (eg, select geologic units where proportion of sandstone > 50 %). Proportions are encoded with swe:QuantityRange and therefore the filter expression must identify the first or second term of a value encoded using a swe:RealPair (eg. , we need to filter in on the first element of the list) Unfortunately , FES (Filter Encoding Standard) does not provide a mechanism to âô€€ô€€parseâô€€ô€€ the content of a RealPair nor does minimum XPath (OGC 09-026r1, clause 7.4.4) hasve a syntax to identify a specific element. The only solution within the current specification is to implement a server side function or an extended XPath support, neither being practical or likely. We therefore need a range encoding that is within reach of a FES expression[WMS 1.4 SWG] Errors in UML diagrams (TileMatrixSetLink) 1 13-077 Robert Coup 2013-08-13UML diagrams don't reflect schemas[OAB] Proposed rewrite of The Specification Model --- A standard for modular specifications. 1 13-063 Adrian Custer 2013-07-05The original document cannot be used as written. The injunctions are vague, the tests unclear.[WFS 2.0] Add support for asynchronous execution of operations 1 13-062 Panagiotis (Peter) A. Vretanos 2013-07-05In order to support long-running requests that can cause timeouts in a synchronous web environment.[WFS/FES SWG] Corrections and simplifications in the Basic WFS conformance class 1 13-064 Clemens Portele 2013-07-05[OLS 1.3 SWG] Remove smart character from XLS.xsd. 1 13-060 Erin Dogan 2013-07-05The XLS.xsd contains a smart character that does not map to UTF-8 which is the encoding the .xsd specifies. This causes an exception when trying to read and map the schema.[OWS Common 2.0] Add support for very large capabilties document 1 13-059 Panagiotis (Peter) A. Vretanos 2013-07-05Services that offer thousands/millions (or more) items in the content section make it cumbersome and inefficient to download and manipulate capabilities documents. This is especially true for services such as SOS that may offer hundreds of thousands of content section items.[WFS 2.0] Do not make GML a "mandatory" output format. 1 13-061 Panagiotis (Peter) A. Vretanos 2013-07-05One of the key issues that emerged from Geoservices API process was that there is a significant community desire to use JSON for data delivery. Now we know that this would be a relatively trivial addition to WFS. But it would still leave WFS with the mandatory-GML requirement, which scares off potential implementers particularly on the client side. I wonder if there is a way we could relax that, so that a conformant WFS might only offer JSON? As a precedent, I don't think there is a mandatory format (media-type) in WMS or WCS 2.0.KMZ not clearly described in the KML Standard 1 13-040 Jason Mathews 2013-06-03OGC KML standard defines KMZ in the introduction (refers to it in several sections) but doesn't go into detail and define the structure of KMZ file structure in the body of the standard.[SOS SWG] Correct encoding rule 1 13-030 Clemens Portele 2013-05-03Remove the incorrect statement that âô€€ô€€all elements are substitutable for gml:AbstractValue (and thus transitively for gml:AbstractObject) so that they can be used directly by GML application schemasâô€€ô€€. The current Annex C "UML to XML Schema Encoding Rules" is incomplete. The SWE Common encoding rule in 12-093 section 7.2 might be used to provide a complete encoding rule.[KML SWG] Discrepency between kml:north/south element description and associated type/default value 1 13-037 Jason Mathews 2013-05-03OGC specification has a discrepancy between kml:north/south element description and associated type/default value such that the default value is not in the valid range and violates the valid range for latitude values. [WFS 2.0] Allow client to control which features in a join query are presented in a response 1 13-035 Panagiotis (Peter) A. Vretanos 2013-05-03At the moment a join query always returns tuples of feature types satisfying the join predicate. The problem with this is that in many cases the client only wants one (or a subset) of the feature types being queried. For example, the query "Find all roads that cross Algonquin Park" is a join query but the client only really wants the roads.[SOS SWG] Table formatting issue caused 'extra' numbered Requirement? 1 13-038 Wendy Adams 2013-05-03Improved readability (and elimination of \'unintentionally\' created numbered requirement?).[SF SWG] SpatialRefSysURI 1 13-027 Paul Daisey 2013-05-0309-048r3_Name_type_specification__definitions__part_1__basic_name specifies use of URI/URN to designate spatial reference systems. Future update of SF/SQL spec should reference / align with this document.[KML SWG] Coordinates by reference to other object 1 13-033 Alan Hughes 2013-05-03Improve consistency between points and and real world objects that are defined by reference to points.[WFS/FES] WFS Add support for unit of measure conversions 1 13-034 Josh Vote 2013-05-03The current WFS standard has no support for unit of measure conversions. Driving usecases: * Get me everything that matches my filter where the literal has units of my choosing * Get some features and portray their properties in a unit of measure of my choosing[CityGML SWG] Enforce LOD1 and LOD2 buildings to be Solid 1 13-028 Marcel Reuvers 2013-05-03All the surfaces of a LOD1 and a LOD2 building should form one or more closed volumes together, represented by the GML type Solid, even if CityGML permits buildings to be modelled with the Multisurface type. This is because a solid is the only way a building can be represented as a volume. A LOD1 building (Building or BuildingPart) can only be represented with a solid. A LOD2 building can be represented by a mixture of a solid and other geometry types such as a multisurface for a roof overhang and a curve for an antenna.[FES 2.0] Add advanced text searching operators PropertyMatches and PropertyContains 1 13-010 Panagiotis (Peter) A. Vretanos 2013-05-03OWS-9 tested advanced text searching operators that support fuzzy searching and searching by search terms.[WFS/FES] Working on to Implement WFS 2.0 but could not find test data for 2.0, why??? 1 13-007 Volkan Kepoglu 2013-05-03Dear Sirs, I am working on to implement Web Feature Service (WFS) version 2.0 to our IMS products but I could not find test data for WFS version 2.0. For version 1.1, test data is exists, but not for version 2.0. And there is no any compliant that taken WFS 2.0 certificate, why is it so??? I am really sorry for this email that may not be the right place to ask this question, but i also could not find any other place. please advice me to learn the procedure. with my best regards[GeoSPARQL SWG] Corrections of example data and queries 1 13-019 Richard Mietz 2013-05-03Errors in example data and queries might lead to wrong implementations.Support batch modifications (as opposed to Transactions) 1 13-022 Panagiotis (Peter) A. Vretanos 2013-05-03Right now the WFS support transactions or atomic units of work. That means that if 100,000 feature inserts are posted to the WFS then either the entire 100,000 features are successfully inserted or the entire transactions fails and everything is rolled back. There is a requirement to support batch operations which are similar to transactions but have a slightly different semantic. Namely the unit of work does not need to be atomic. So, using the 100,000 feature insert examples again, the WFS would process as many of the inserts as is can and at the end report which one succeeded and which ones failed. Another aspect of the semantic difference between a transaction and a batch is that in a batch operations the server can choose to execute the encapsulated actions is whatever order it wants. This is not the case for transactions; the actions must be executed in the order in which they are presented to the server.{CityGML SWG] Meta Data for City Model 1 13-029 Karl-Heinz Häfele 2013-05-03At the moment there is no general agreed set of meta data to identify the source, the actual creation time, the defined CityGML profile etc. of a city model available[CityGML SWG] Allow LOD0 footprints that will be determined by the connection of the terrain and the building 1 13-025 Marcel Reuvers 2013-05-03Buildings at LOD0 in CityGML can be represented in two ways; a footprint and a roof edge (in general). Both the LOD0 representation of a building footprint and a roof edge have to be a âô€€ô€€horizontal surfaceâô€€ô€€ pursuant with CityGML specifications. If a footprint is in reality situated on a slope then the lowest value has to be used (as specified in CityGML). It is also stated that the base in LOD2 must be congruent with the LOD footprint. Although modelling a horizontal surface with footprints has many advantages, this approach also has disadvantages, particularly with buildings where the footprint is not horizontal in reality. These drawbacks have been raised by the OGC CityGML work group and are currently being discussed. They are: a. Buildings on a slope (dike, dune) cannot be modelled as such. The sloping footprint has to be approximated by a horizontal surface b. In order to make sure that in these situations building footprints intersect the terrain, there will almost always need to be vertical surfaces bridging the gap between footprint and terrainâô€€ô€€s edge. This is at least when working with high resolution as is most often the case in the Netherlands (for example the AHN2). These vertical surfaces are not present in reality and moreover a lot of software cannot work with them. c. Two BuildingParts on a slope which touch each other in a vertex cannot be modelled in a topologically correct fashion. The footprints are modelled with a vertical interval that doesnâô€€ô€€t exist in real life. In this situation one can choose to put both footprints at the same height. But what should be done with a terrace house on a slope? Neither the artificial differentiations in height nor putting all footprints at the same elevation are true to reality.{GML 3.3 SWG] Values of GML properties 1 13-020 Clemens Portele 2013-05-03The current text in GML 3.2.1, section 21.2.7 states: "If the value of the property is expected to be represented inline, the type of the property element shall support this, either by having XML Schema simple content of the appropriate simple type or by containing the GML object that is the value of the property inline (see 21.2.6)." This requirement is too restrictive and not inline with the original intention, the text in Clause 7 and current practice. The quoted text limits the values of a GML property to GML objects (i.e. "XML elements of a type derived from AbstractGMLType") and prohibits that a GML property may have a value that is an XML element from some other XML grammar. However, sub-clauses 7.1.1 and 7.2.3 were written with the intention that property values are not restricted to GML objects as expressed in the patterns specified in 7.2.3. Conclusion: The statement in 21.2.7 is an error needs to be changed in a corrigendum.[WFS/FES] Circle reference in Filter.xsd 1 12-136 Magnus Karge 2013-04-08Generating SOAP/WSDL using ServiceModel Metadata Utility tool (svcutil) we get an error message which indicates that there is a circle reference in Filter.xsd in Filter Encoding 2.0.[WFS FES SWG] Support for Semantics in OGC Filters 1 13-006 Gobe Hobona 2013-01-02It is proposed that the Filter specification should include a PropertyIsSemanticallyRelatedTo comparison operator that accepts a propertyname, resourceidentifier and zero or more semanticrelationships.[GeoAPI 3.0 SWG] Replace JSR-275 dependency by org.unitsofmeasure 1 13-008 Martin Desruisseaux 2013-01-02The JSR-275 (Java Specification Request) effort terminated without success just before GeoAPI 3.0.0 release. The javax.measure packages do not officially exist. We waited two years to see if a new JSR would appear, but the situation is still uncertain. On the other side, the org.unitsofmeasure alternative is now part of Eclipse ecosystem and have at least 3 implementations.[GeoAPI 3.0 SWG] Replace uses of java.util.Date by ISO 19108 TM_CalDate and TM_ClockTime 1 13-004 Martin Desruisseaux 2013-01-02All the following methods, which currently return java.util.Date, would need their return type to be changed. All those method contains a Javadoc warning about this anticipated change. CalendarDate Metadata.getDateStamp(); DateAndTime Requirement.getExpiryDate(); DateAndTime RequestedDate.getRequestedDateOfCollection(); DateAndTime RequestedDate.getLatestAcceptableDate(); DateAndTime Event.getTime(); CalendarDate Citation.getEditionDate(); CalendarDate CitationDate.getDate(); DateAndTime StandardOrderProcess.getPlannedAvailableDateTime(); DateAndTime Usage.getUsageDate(); DateAndTime ProcessStep.getDate(); CalendarDate MaintenanceInformation.getDateOfNextUpdate(); DateAndTime Element.getDates(); CalendarDate Datum.getRealizationEpoch(); DateAndTime TemporalDatum.getOrigin();[SLDSE 1.2 SWG] Support non GML 3.1 features in sld:InlineFeature 1 12-169 Jeroen Dries 2013-01-02Remove the hard dependency on GML 3.1. This can be done by using xsd:any which enables the inclusion of any feature type, even if they are not GML at all.[WFS FES SWG] Make first operand of binary spatial operators optional and change it to fes:expression 1 12-173 Timo Thomas 2013-01-02The first operand of binary spatial operators is not optional for unknown reasons. This does not harmonize with BBOX, DWithin and Beyond operations and contradicts figure 6 on page 23. Standard requests could be be more compact if the element was optional. The first operand is a fes:ValueReference. This does not harmonize with BBOX, DWithin and Beyond where the first operand is of type fes:expression.[SLDSE 1.2 SWG] Replace ogc:filter with fes:AbstractQueryExpression in sld:FeatureTypeConstraint 1 12-170 Jeroen Dries 2013-01-02Replace ogc:filter with fes:AbstractQueryExpression. This requires an upgrade from filter 1.1 to 2.0.[WFS 2.0] Allow DescribeFeatureType to reference an existing schema rather than generate an explicit schema document 1 12-149 Panagiotis (Peter) A. Vretanos 2012-12-19Allow DescribeFeatureType to reference or redirect to a schema rather than generate a schema document. This can be done using an HTTP 3XX code. [WFS 2.0] Decouple the query model from the presenation model 1 12-150 Panagiotis (Peter) A. Vretanos 2012-12-19Proposal #1: The current StoredQuery syntax limit the parameters comparaison to equality (=) Adapted from an example you provided us in 2009 - I could not find an example of StoredQuery in 09-025r1 (definitively need one) This should also be valid age245.3[WCS SWG] Type change for wcs:Dimension  1  12-140  Nathan Potter  2012-12-19 Change the type of wcs:Dimension to URI.[WCS SWG] Subset in KVP requests allows to specify crs, but POST requests are not allowed to  1  12-167  Andrea Aime  2012-12-19 Have the CRS be handled the same way in both KVP and POST requests.[WFS/FES] A Semantic Maturity Model for Web Feature Services  1  12-131  Stephen Desmond  2012-10-31 WFS developers have a choice between four approaches to choosing or > developing a GML schema. There are cost and benefit trade-offs for each one. > 1. âô€€ô€€Entry Levelâô€€ô€€, using the Simple Features Profile. > 2. Using a locally developed one-off schema and middleware. > 3. Using a Community, but localised one-off schema. > 4. Using a Standardized schema such as CityGML[WMS 1.4 SWG] Flag to indicate changes in WMS during use  1  12-125  Mats Olsson  2012-10-10 When a WMS server is updated with new data or a new layer structure, the client can only learn this by requesting a new Capabilities document by a polling mechanism, which creates a performance overhead. If a custom http-header with an updatesequence number it added to the WMS GetMap reply it can be used to identify when the server have changed the service, and the client can handle it in an appropriate way.[OWS Common] Define XML and JSON schema for a web linking structure based on RFC 5988  1  12-121  Panagiotis (Peter) A. Vretanos  2012-10-09 As OGC transitions from RPC-based web services to REST-based web services data linking become more critical as data linking is an important REST concept. As a result, OGC needs to define a standard schema in XML and JSON for a linking elements. Examples of existing linking elements are the "link" element in HTML and ATOM or JSON-LD in JSON.[GML 3.3] Clause A.1.1.5 includes non-mandatory constraints  1  12-120  Richard Martell  2012-10-09 ATC A.1.1.5 ("Support for the GML model and syntax") appears in cl. A.1.1: Test cases for mandatory conformance requirements. However, it includes non-mandatory constraints since the lexical conventions are just recommendations.[SLDSE 1.2 SWG] Add parameters to get GetLegendGraphics appearance to work for more than one layer.  1  12-116  Mats Olsson  2012-09-25 Having a separate legend for each layer in a WMS client quickly becomes unmanageable. There is a need to create a single client legend that provides an overview of all the features that can appear in the map.[WMS 1.4 SWG] WMS capabilities property that recommends if layers should be initially active or inactive  1  12-115  Mats Olsson  2012-09-25 There is no good way for a WMS client to set a reasonable initial state when using WMS services with many layers or layers that hides information in layers below. With a boolean initial state attribute on each layer the client could setup layers in a user-friendly way where the most important information is visible from the start and the server load and client response time is reduced by having information that cannot be combined anyway switched off.[WFS-FES SWG] WFS Add support for unit of measure conversions  1  12-114  Joshua Vote  2012-09-25 The current WFS standard has no support for unit of measure conversions. Driving usecases: * Get me everything that matches my filter where the literal has units of my choosing * Get some features and portray their properties in a unit of measure of my choosingGML Harmonization with SF, SQL/MM and ISO TC211  1  12-106r1  Paul Scarponcini  2012-09-12 FES 2.0: Make ValueReference in the BinarySpatialOperatorType optional  1  12-090  Panagiotis (Peter) A. Vretanos  2012-09-07 Currently the ValueReference is optional for the BBOX property. The meaning is that the spatial operator should be applied to all spatial properties of the feature. The advantage is that the client can query with a BBOX without necessarily knowing the name of the spatial property(ies). Why is a similar approach not taken with all the other spatial operators?gml:id attribute on LinearRing  1  12-092  Linda van den Brink  2012-09-07 CityGML 1.0 and 2.0 are based on GML 3.1.1. We want to base the next version of CityGML on GML 3.2. However, in GML 3.1.1 the linear ring can have gml:id (http://www.schemacentral.com/sc/niem21/e-gml_LinearRing.html ) . In CityGML we use this gml:id to establish a link between texture coordinates (in the appearance) and the linear ring where this texture should be applied. In GML 3.2.1 the linear ring is not allowed to have a gml:id. So the texture cannot be applied to a linear ring. Earlier discussion on this topic on the GML SWG mailing list made clear that according to ISO19107 rings are boundaries and boundaries are GM_Objects. (In the model for GM_Object, the boundary operator returns a GM_Boundary, which is a subtype of GM_Complex, which is a subtype of GM_Object. Ergo, any type which is used to represent the boundary of any geometry (always a subtype of GM_Object) must be instance of GM_Object by inheritance (through GM_Complex)). In GML 3.2 however, LinearRing is not a subtype of GM_Object and thus not a geometry and lacking the gml:id attribute. This is a bug in GML 3.2. Incorrect Example of URN in document in Table E.4  1  12-107  James Sibbald  2012-09-07 The information contained in Table E.4, namely the urn of the CRS of the Definition of Well-known scale set GoogleMapsCompatible, is incorrect and if used as an exemplar for coding could cause problems with use of WMTS. [OpenSearch] values for the relation parameter are insufficient  1  12-086  Panagiotis (Peter) A. Vretanos  2012-09-07 The current list of operators that are valid values for the "relation" parameter are overlap, contains and disjoint. This list is incomplete and there is not reference describing exactly what "overlap", "contains" and "disjoint" mean.Support Keyword URI in Capabilities  1  12-085  Frederic Houbie  2012-09-07 Trying to add semantic annotation to XML Capabilities, it is not possible to represent the URI of keywordsClarify Time type(s)  1  12-078  Peter Parslow  2012-09-07 Section 7.2 states a dependence on ISO 19103, explicitly including the statement that ISO 19103 Time & DateTime are used directly. However, at 7.2.9, the specification defines its own Time class (in the Simple Components package). Similarly, the timePositionType is "A minor variation on gml:TimePositionUnion" (annotation in XSD) - is the benefit of this non-standard approach worth while? This has lead to confusion when using the class: when is it useful/ necessary / appropriate to use the SWE Time class, and when is the ISO Time class more relevant? [OpenSearch] symetrical handling of spatial and temporal parameters  1  12-087  Panagiotis (Peter) A. Vretanos  2012-09-07 Spatial parameter in the standard include both convenience spatial operators (i.e. bbox, lat, lon, radius) and generalized spatial operators (i.e. geometry, relation). The parameters for temporal operators are not similarly symmetric.WFS: Add support for unit of measure conversions  1  12-015r3  Josh Vote  2012-06-06 The current WFS standard has no support for unit of measure conversions. Driving usecases: * Get me everything that matches my filter where the literal has units of my choosing * Get some features and portray their properties in a unit of measure of my choosingOpenLS GeocodingResponse Polygon/LineString enhancement  1  12-071  Oaten Lewis  2012-05-31 Permit use of GML LineString and Polygon instead of only Point in GeocodeResponse and ReverseGeocodeResponse.SOS Changes to support Video  1  12-072  Robert Cass  2012-05-31 SOS interface changes to support videoCityGML: Storeys and LODs for BIM interiors  1  12-044  Cliff Behrens  2012-05-16 1) The concept of \"storeys\" or \"floors\" needs to be supported to enable emergency responses, e.g., E911, and other applications, e.g., indoor routing. Note, that the delineation of floors can happen in at least two ways. One notion derives from the topology of a CityModel, e.g., the number of rows of windows in a BIM. A second notion is realized as a name assigned to a feature collection, e.g., \"Floor 2.\" Note that this distinction is important since the name of a floor may not accurately reflect its topological position. As an example, in the US many buildings have 13 or more physical storeys; yet, the 13th floor is not a named option in an elevator, due to long-standing superstitions. The name is particularly important for providing natural language routing to mobile clients. 2) Related to the above, more levels of detail are required for modeling building interiors. At the moment only one CityGML level of detail (LOD4) pertains to building interiors, and its high-resolution captures all features including floors, walls, ceilings, furniture, etc., while five LODs exist for modeling building exteriors. This amount of detail in a BIM seems overkill for many indoor applications. A low-resolution interior LOD analogous to a building\'s footprint in LOD0, might be a tile of a floor\'s perimeter. The next higher-resolution LOD of a building\'s interior might be a 2D floorplan, or \"milk carton\" model. At the next higher level of resolution, the model of an interior LOD might resemble the block model of a cityscape in LOD1, and so on. These lower interior LODs are important to those applications, e.g., indoor navigation and routing, that only require floorplans or a \"mazeway\" view. Moreover, since CityGML models of building interiors will most likely be produced by CAD tools, it is important that a simpler, less-costly entry level be provided to CAD data producers. Otherwise, the availability of CityGML models of building interiors is likely to be delayed.CAT-APIS2.0: Support Keyword URI in queryable  1  12-045  Frederic Houbie  2012-05-16 ISO 19115 gmx extensions allows substitution of Character String with Anchor element, which supports href attribute to represent a link. Using this in Md_Keywords allow representation of Keywords URI which is important for Semantic discoveryWPS Allow multiple process output parameters with same identifier  1  12-048  Matthias Lendholt  2012-05-16 a) For process chaining the same constraints should apply for input and output parameters. b) Currently collections of complex output types must be wrapped into a list-like complex type (container) which complicates the schema handling.Broaden definition of fes:AbstractProjectionClause  1  12-038  Jeroen Dries  2012-03-23 The current definition of an AbstractProjectionClause is very narrow, which limits the usefulness of AbstractAdhocQueryExpressionType as an extension point for custom queries.Polygon fill styles  1  12-037  Marie-Lise Vautier  2012-03-23 DGIWG S15 project investigated the use of KML for the military community. One topic was to use KML to portray command and control data according to the MIL-STD-2525B common warfighting symbology. A number of styling requirements were identified as a result, including enhancement to polygon fill styles. The solution proposed for these fill styles was implemented in one Canadian forces system using OpenLayers.Various line styles  1  12-036  Marie-Lise Vautier  2012-03-23 DGIWG S15 project investigated the use of KML for the military community. One topic was to use KML to portray command and control data according to the MIL-STD-2525B common warfighting symbology. A number of styling requirements were identified as a result, including support for different line styles ("dot", "dashdot", "longdash", "longdashdot" and "solid"). The solution proposed for these line styles was implemented in one Canadian forces system using OpenLayers.KML: Dashed line style  2  12-035  Marie-Lise Vautier  2012-03-21 DGIWG S15 project investigated the use of KML for the military community. One topic was to use KML to portray command and control data according to the MIL-STD-2525B common warfighting symbology. A number of styling requirements were identified as a result, with support for a dashed line style being one of the most critical. The solution proposed for dashed lines in this CR was implemented in one Canadian forces system using OpenLayers.KML: Dashed line style  1  12-035  Marie-Lise Vautier  2012-03-21 DGIWG S15 project investigated the use of KML for the military community. One topic was to use KML to portray command and control data according to the MIL-STD-2525B common warfighting symbology. A number of styling requirements were identified as a result, with support for a dashed line style being one of the most critical. The solution proposed for dashed lines in this CR was implemented in one Canadian forces system using OpenLayers.Correct requirements classes and dependencies  1  12-024  Simon Cox  2012-03-20 The structure of GMLCOV requirements are inconsistent with OGC Policy. * the set of requirements included in each class is not explicit * dependencies are associated with a requirement whereas they should be between requirements-classesFix name of (non-abstract) XML type  1  12-025  Simon Cox  2012-03-20 The GMLCOV schema has a definition for a type called "AbstractDiscreteCoverageType" which is not specified as abstract=true. Furthermore, this type is used unchanged as the content-model of a set of concrete element declarations. This is confusing and inconsistent with other OGC XML SchemasEditorial rewrite of The Specification Model -- A Standard for Modular specifications  1  12-017r2  Adrian Custer  2012-02-21 Reexamine the goal of the document, for a better title, better organized introductory text, and more systematic organization of the content. Review the language of the normative text to fix the language and order. Fix errata.Editorial rewrite of The Specification Model -- A Standard for Modular specifications  3  12-017  Adrian Custer  2012-02-16 The standard, while exceedingly useful, is poorly structured and written.Editorial rewrite of The Specification Model -- A Standard for Modular specifications  1  12-017  Adrian Custer  2012-02-16 The standard, while exceedingly useful, is poorly structured and written.CapabilitiesBaseType vs. OWSServiceMetadata  1  12-014  Stephan Meißl  2012-02-13 Remove "OWSServiceMetadata" and instead explain usage of "CapabilitiesBaseType".[FES] The matchAction parameter should exist on more than the comparison ops.  1  12-012  Panagiotis (Peter) A. Vretanos  2012-02-13 Review and update other non-comparison operators to see if the 1 matchAction parameter may be applied to them (e.g. propertyIsBetween).KML 2.3 - Addition of Google extensions to the KML Standard  1  11-176  Sean Askay  2011-12-14 Addition of new KML features supported in Google Earth to the KML Standard.