OSGeo and OGC Collaboration
This is a modal window.
The media could not be loaded, either because the server or network failed or because the format is not supported.
Formal Metadata
| Title |
| |
| Subtitle |
| |
| Alternative Title |
| |
| Title of Series | ||
| Number of Parts | 295 | |
| Author | ||
| Contributors | ||
| License | CC Attribution 3.0 Germany: You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor. | |
| Identifiers | 10.5446/43444 (DOI) | |
| Publisher | ||
| Release Date | ||
| Language |
Content Metadata
| Subject Area | ||
| Genre | ||
| Abstract |
| |
| Keywords |
00:00
EmailCollaborationismOpen sourceComputer programmingNoise (electronics)Open source
00:28
WhiteboardMultiplication signProjective planeGeometryClosed setGoodness of fitOpen source
01:16
EmailCollaborationismOpen sourceSharewareTime evolutionTable (information)Content (media)GoogolScripting languageJava appletService (economics)ArchitectureService-oriented architectureCollaborationismProjective planePresentation of a groupTerm (mathematics)SharewareMultiplication signQuicksortBit rateOpen sourceXMLUML
02:16
Focus (optics)Service (economics)BitWeb serviceQuicksortHardware description languagePoint (geometry)EvoluteDatabaseBuildingService-oriented architectureSoftware design patternOcean currentState of matterComputer architectureLecture/Conference
03:19
Time evolutionGoogolScripting languageJava appletService (economics)ArchitectureService-oriented architectureCodierung <Programmierung>Parameter (computer programming)Dependent and independent variablesError messageDisintegrationSoftware developerKey (cryptography)Search engine (computing)Service (economics)Markup languageQuicksortRevision controlLatent heatMobile appProcess (computing)Web-DesignerWeb 2.0MereologySoftware developerMultiplication signLevel (video gaming)Game theoryShared memoryGroup actionReal-time operating systemMappingPresentation of a groupProjective planeTesselationLibrary catalog19 (number)MathematicsJava appletScripting languageFormal languageGoogolData conversionOffice suiteComputer animation
05:55
HypermediaContent (media)Heat transferType theorySoftware developerScripting languageJava appletPositional notationObject (grammar)Social classService (economics)State of matterRepresentation (politics)Codierung <Programmierung>Client (computing)Point (geometry)Formal languageDependent and independent variablesParameter (computer programming)Code generationSoftware testingWeb 2.0Web-DesignerLevel (video gaming)Latent heatDisk read-and-write headRight angleWeb applicationParameter (computer programming)Error messageFocus (optics)IdentifiabilityOperator (mathematics)Web servicePoint (geometry)Water vaporQuicksortFigurate numberRepresentation (politics)Online helpOpen setCodeRepresentational state transferLecture/ConferenceComputer animation
07:21
File formatModul <Datentyp>Extension (kinesiology)Core dumpProcess (computing)BitEvent horizonCollaborationismOpen setWeb-DesignerWaveImplementationGoodness of fitFile formatProfil (magazine)Poisson-KlammerWeb 2.0Software developerGeometryPoint (geometry)Latent heatExtension (kinesiology)Right angleInformationCASE <Informatik>IdentifiabilityCore dumpWave packetResultantSpacetimeElement (mathematics)Lecture/ConferenceComputer animation
10:29
Row (database)MappingProcess (computing)Service (economics)Library catalogVotingTesselationSlide ruleComputer animation
11:00
Video trackingCollaborationismProbability density functionHyperlinkAdditionOpen sourceWeb 2.0Revision controlPerspective (visual)Open setCollaborationismBitImplementationOnline chatComputer animation
11:34
CollaborationismImplementationCollaborationismBitGeometryRevision controlLatent heatCASE <Informatik>Projective planeImplementationWhiteboardPoint (geometry)Library catalogDigital electronicsLecture/ConferenceComputer animation
12:36
CollaborationismImplementationLibrary catalogSource codeImplementationOrder (biology)Multiplication signOpen sourceCASE <Informatik>Goodness of fitServer (computing)Level (video gaming)Reading (process)Software testingBitSoftwarePoint (geometry)Point cloudVotingLimit (category theory)WebsiteState of matterComputer animation
14:41
CollaborationismImplementationProcess (computing)SoftwareSoftware testingProjective planePattern languageProcess (computing)ImplementationFamilyGeometryMultiplication signFeedbackWebsiteOpen sourceLimit (category theory)Software developerSoftware testingSoftwareLevel (video gaming)WhiteboardCollaborationismBitSharewareLattice (order)Spring (hydrology)MereologyComputer programmingQuicksortTime zoneGreen's functionPRINCE2SequelPoint (geometry)Procedural programmingOrder (biology)Lecture/ConferenceComputer animation
18:04
Projective planeMultiplication signProcess (computing)GeometrySoftware developerMereologyImplementationRadical (chemistry)Lecture/Conference
19:05
ImplementationServer (computing)ParsingFile formatClient (computing)Product (business)Software testingProjective planeClient (computing)File formatGeometryServer (computing)WebsiteImplementationDegree (graph theory)Electronic mailing listLevel (video gaming)Computer clusterPresentation of a groupLimit (category theory)Computer animation
21:07
SharewarePresentation of a groupGeometryRight angleLecture/Conference
21:38
TouchscreenView (database)Web browserObject-oriented programmingLecture/ConferenceComputer animation
22:07
View (database)Special unitary groupSharewareLatent heatProjective planeComputer animation
22:38
Revision controlClient (computing)Server (computing)SharewareLink (knot theory)Configuration spaceInstance (computer science)LaceMKS system of unitsUniform resource locatorService (economics)Power (physics)View (database)Social classTerm (mathematics)EmailInternet service provider19 (number)Wechselseitige InformationAddress spaceProcess (computing)Public domainMenu (computing)InformationMaxima and minimaScale (map)Convex hullHill differential equationRankingInformationSet (mathematics)Table (information)Instance (computer science)Client (computing)Server (computing)NumberRepresentation (politics)Electronic mailing listMetadataVapor barrierLanding pageMultiplication signGoodness of fitAbstractionCodeVirtual machineWeb pagePoint (geometry)GeometrySearch engine (computing)Dependent and independent variablesDifferent (Kate Ryan album)Term (mathematics)QuicksortIdentifiabilityWeb-DesignerAttribute grammarLatent heatLine (geometry)Zoom lensLevel (video gaming)Numbering schemeSound effectReading (process)Social classSign (mathematics)GoogolPresentation of a groupComputer animation
26:44
PRINCE2Software testingMultiplication signBitArithmetic meanWeb pageData structureSlide ruleGeometryLecture/ConferenceMeeting/Interview
28:10
Host Identity ProtocolSign (mathematics)Process (computing)Revision controlDatabase transactionState of matterExtension (kinesiology)Core dumpSoftware developerGroup actionWeb pageLibrary catalogLatent heatMereologySoftwareOrder (biology)Coma BerenicesMultiplication signExpected valueNumberComputer animation
31:16
Physical systemProjective planeMultiplication signCoordinate systemPoint (geometry)Block (periodic table)Term (mathematics)Film editingLatent heatMoment (mathematics)Extension (kinesiology)Logic gateCore dump1 (number)Office suiteRevision controlMereologyPerspective (visual)Server (computing)Set (mathematics)Endliche ModelltheorieGoodness of fitQuicksortChemical equationInternet service providerProcess (computing)Software developerOcean currentClosed setInformationLecture/Conference
Transcript: English(auto-generated)
00:07
Good, okay So we had a general introduction from myself about OTC programs and the MOU between OTC and OSG. Oh Stefan was just talking about OTC's innovation program and how this helped, you know how this works with the open source
00:28
Community and now we have Angela's and Tom to look from the standard side On OTC standards the open standards and what is in for the OSG community and and how they collaborated
00:49
All right good So hello everyone, I'm Angela's and Tom is with me we are both representing OSG Oh as board members and at the same time we are both OTC members and
01:06
We are participating in in several OSG Oh projects So we are going to talk today about how we collaborate as always OSG Oh projects how we do collaboration with
01:21
OTC but we are also going to talk about how the foundation is collaborating with with OTC in general so we are this is our this is short overview of our Presentation we are going to talk about how the OTC evolved in terms of API's and
01:42
We are going to describe how how is the current activity on the OTC API front? Then we are going to talk about the collaboration between OTC and OSG Oh And if we have time at the end, we will give you a short demo a short demo of what?
02:00
What our projects can do so, please Tom Take over Thank You angels so if anybody needs to recover from last night and Wake up again. Just come here and have this light shining on you and
02:21
He'll wake up At any rate, thank you very much I'm going to walk through a little bit of the OGC API evolution Which is showing my age, but basically Looking back looking back at the at the OGs At the history of OGC API's for better or for worse
02:42
we saw that I'm gonna walk through the 90s and 2000s and sort of current state So in the 90s there were there was a lot of focus around Building these API's around the sort of Korba or XML RPC design pattern Soap and web services description language was was was was prominent at that point and the whole concept of service-oriented
03:07
Architecture was was huge. We wanted to have Services and and API's for absolutely absolutely everything. There was a strong concept of having a database in the back and
03:21
Of course you all most of you shouldn't all know that the web map service standard was version 1 from 1999 was the at the forefront of the of the initial efforts in OGC along with geography markup language Then in the in the to set in the 2000s the concept of web to sort of proliferated
03:42
Where we started to see? You know a lot a lot of JavaScript Ajax Google Maps came came out and that sort of changed the whole game Where we had slippy maps and tiles and you know that this conference has seen its share of the presentations and work and projects around these concepts
04:03
At the same time in OGC we kept pushing along with with evolving with web feature service web coverage service processing and and catalog so There was I think
04:20
those those Specifications have served us very well over the last 10 or 20 years at the same time it's important to sort of look where where where things are at and and and Have an obvious honest conversation, and I think a lot of that has happened in the recent in the in the recent activity so some technical considerations around the way OGC api's were were developed is
04:46
XML was was very is very prominent key value pairs when doing requests GML so geography markup language, which is this huge specification very difficult to implement in full
05:03
Various things around overloading the actual HTTP specification with very specific things Exhaustive specifications and requirements, so it was a lot. It was a lot of you either implement this entire standard, or you don't And I've wasted many a Friday night implementing a standard to to the end so
05:23
The other the other challenges were search engines how many times have we had discussions around how do we find data? On via Google or via some other or Yahoo or some other search engine and Making it easy to to for web developers, so I'll give you an example It's part of the weather service. We developed a mobile app
05:44
well, I didn't but the web developers did and and my group runs the WMS that does all the real-time radar data So one of the developers came up to me and asked for for the WMS spec And how do they interact with this web map service, so they're still scratching their heads, but it was released
06:01
But it was very difficult to implement and and comprehend that specification for a web developer so fast forward Help is on the way So these days we have a concept of rest a representational state transfer
06:22
more more sort of focus on HTTP verbs Really using the status codes as opposed to Sending error messages with everything as HTTP 200 Using URIs the concept of identifiers is getting stronger and stronger Obviously JSON is
06:41
the lingua franca of sort of exchange especially for what for web applications much more compact and and performant Open API and swagger is is all the rage these days So open eyes open API is basically YAML or JSON representation of how you define a
07:05
web service endpoint and its operations and so on its parameters and swagger is Really neat tooling that implements open API. So web developers can Quickly open an API figure out. What are the all the operations that the what are all the
07:21
Requests that the API supports what parameters can I give and so on right in a web application without reading the spec So a little bit. I know Athena mentioned a little bit about activities in OGC with regards to recent events around open API and collaboration with w3c, but I'm also
07:43
I'm gonna walk through a little bit of it here So if you haven't read the w3c spatial data on the web best practices is probably a good idea on your flight or train home To to take a look at it. It's a recommendation and it has a lot of information on recommendations on describing
08:01
You know geospatial data formats concept of identifiers accessing geospatial data licensing and problem proven provenance I'm from Canada. So I'm prone to saying province for provenance and the idea of being webby So a spec is is is really valuable if it's of the web
08:21
So it's web friendly and it's web developer friendly So some of the some of the things that we're seeing coming out of OGC with regards to standards development is again things being webby developer friendly lightweight specifications and This one right here removing a CD removing the use of HTTP is a tunnel
08:45
this one took me a while to figure out but I'm here now and and and I'm telling you that this is a An easier way to go especially when you're sending it to showing it to a web developer who may not have You know geospatial knowledge per se so really getting closer to the HTTP
09:03
specification and that we're not inventing a layer on top of it and The specifications are also different Evolving where now we have the concept of a core specification and with a bunch of extensions. So The really easy use cases of you know lat long points and getting it in geo JSON
09:24
That is essentially a core specification of for example the the new WFS Spec as opposed to you know, anything more elaborate a Little bit of a timeline. So again the w3c recommendation. There was an OGC API white paper
09:42
And and then in 2018 and 2019 the rubber started to hit the road There was a WFS 3 hackathon There was also a weather on the web API hackathon and there was the OGC API happen hackathon in London. So We're starting to see a little bit more hands-on In an open fashion from from OGC
10:03
Which has resulted in a lot of good work with regards to supporting the new wave of implementations Here's a sneak peek at What I guess the initial new profile of the standards are going to be called so the standards are actually the names of the standards are actually on the
10:23
left hand side and everything in brackets is what it used to be called or what some of us have always been used to so Again, so old OGC API common so all the specs will implement a common layer. Whoops Then we have OGC API features
10:42
coverages maps and tiles as well as Processing and then we have a catalog service a new catalog service, which is records That's still up for debate as to what we're going to call it It might be called catalog as you've seen in previous slides or it might be called records We'll see or cast your vote and let us know what you think a
11:02
Little bit about github activity. So OGC is a thing I mentioned is Starting to use github more and more especially in an open fashion So the standards are actually written in ASCII doc now and they're they're they're exported and released as HTML So in addition to the PDFs or other versions of the documents now, you can get them on the web
11:21
You can actually hyperlink to them Different parts and send them to all your friends There's also a getter chat. So there's a lot of collaboration around the spec So this is really positive to see especially from from open an open source implementation perspective And I'll pass it over to Angeles to talk a little bit about the OS geo collaboration
11:44
Thank you, Tom so as Tom described things are changing in OGC, but also in OS geo and We are trying to figure out how to work together more and more every day So I think I also talked about the MOU that we have and that is also going to
12:05
Go through some revision at some point from the board and OGC So I'm going to talk a bit more technical and what happened to some use cases some some of our projects that are actually heavily involved in in the
12:21
in the also, you know is you and in OGC specification standards implementation so Tom in 2011 started the Pisces W project which Why the project was was all about being Able to to make a catalog with very few requirements and very few resources. So
12:46
The need was to have a very lightweight catalog and Pisces W from day one wanted to be Passing the site tests. So The effort was to be able to provide a compliance server from day one
13:03
And so this this happened very fast and I joined Tom in the process and while we we managed to reach compliance in 2013, so If you know the CSW spec is is a bit is a huge document and it has many many
13:22
aspects so then around 2014 We managed to not only pass all the tests But we managed to also become a reference implementation because at that point OGC started requesting reference implementations and as you know
13:41
Open-source software is the best way to do this because you have the source code people can learn how to how to implement a standard if they can get the source code and that led to 2016 where OGC actually was developing the CSW 3
14:00
Standard and while being in a draft stage We also started implementing CSW 3 in parallel and by the time that the the the standard Reads to the voting stage. We had already implemented it completely. So We were the first reference implementations for
14:22
Reference implementation for CSW 3 and at the same time OGC Wanted to have reference implementations in order to finalize the standard So it's a win-win situation in this case and a very good use for open-source software and this now evolved even even more because
14:43
Today we have a new project which Also follows the same the same pattern that OGC now Uses to develop the the new standard. So today we have already Been working on the pyjio API project, which is now an OS geo community project
15:05
it's in the early days and It is following the implementation of OGC API and Specifically the features and the processing So as the the standard gets finalized
15:21
We are also implementing at the same time and we are also at the stage that we pass the side tests so when it is finalized it the reference implementation will be there and We are developing alongside with all alongside OGC We are going to hackathons and we are hoping that also we can do this on the on the cold springs in the OS geo
15:46
cold springs, so it's it's it's a very very nice time for OS geo and OGC that we can collaborate closer on the development of standards we will have a sort demo by geo API in a while and
16:05
Also, we have another aspect we have team engine which is a software for testing the standards so this is developed by OGC and two years ago As part of the mo you between OS geo and OGC Team team engine applied to our incubation program. So
16:25
Team engine is is going through the incubation procedure, which means that it's being Tested for you know being open source having Living up to the standards of a high high quality open source project and
16:42
That that is still in the process team engine hasn't graduated yet, but it's it's in the process and also by including team engine in our in our Family of projects. We are also helping our other projects to implement compliance or software because working
17:02
Along with team engine was a very successful story for Pisces W. We were able to provide feedback on the site test test the team engine team while implementing a reference of limitation so we help validate site and
17:21
And when the standard is finalized site is validating every every every other project So a little bit more about OS geo and OGC Collaboration we have the we had the the memorandum of understanding signed in 2008
17:42
We are coordinated And we do that on the board level. We have we have Bruce who is Who is the the point of contact on on the OS geo part? For for OGC and we have meetings with OGC members and
18:02
In the in the board meeting this the previous weekend. We had the long session with with Scott. So we are now trying to to work closer together and Part of the of the MOU was to have reference implementations from OS geo
18:23
And I think we are we are doing a very good very good job in this in this aspect. Also OGC provided six member slots individual member slots for our OS geo Developers and that means that if if a member of OS geo Or a project wants to join OGC
18:42
Can can actually take one of these slots and participate and have access to the documentation. Well today the Standards move to github so they are easier to get in the in the previous times it was Somebody had to be an OGC member to see a draft standard because before it was it was finalized
19:04
So that helped also a lot to have this kind of access to documentation So I'm now going to talk about OGC compliance and how this relates to the OS geo project. So as Athena explained earlier a project can implement an OGC standard and that means it can pass the
19:26
standard tests Even without paying for being certified. So currently What we did last night We went to the OS geo site and we took all the projects and we looked if they are implementing
19:41
an OGC standard and actually we found that 21 out of our Graduated OS geo projects implement at least one OGC standard and that includes servers clients format parsers Anything All right, so we have 21 projects implementing out of these projects five OS geo projects are
20:07
Certified so they are OGC compliant and one OS geo community project. So we have degree which is Compliant with 16 standards all of them reference implementations We have QGIS which is compliant with one standard and this one standard is a reference implementation
20:26
We have GDAL, which is compliant with three standards then we have map server which is compliant with one and Pi CSW compliant with four and also reference implementation and we have the community project with which is ISDS OS
20:42
Which is compliant with one standard now in this list We did not add pi geo API and and the reason is that the standard is not final yet All right, so it's not there and and yeah and geo server, which is it is
21:01
Implementing but I think it it didn't it doesn't pass the side tests currently. So hmm. We need to get them to work all right, so That is about it about the presentation and now we would like to run a short demonstration of pi geo API So you get a feeling on of how this all works and how we are moving along the the OGC
21:26
API features Maybe you want to ask a question before that or we you want to run the demo right away. I Don't know
21:47
So Thank You Angeles, so I'm just gonna switch over to the browser
22:01
Oops Which has been closed
22:29
So I'm just gonna do a demo of the pi JP pi geo API project Which would which will demonstrate the evolving OGC API features?
22:41
Specification from from OGC, I know you're all excited So, yeah, so this is this is a new this is a WFS Believe it or not and the idea is In in in line with the w3c
23:01
recommendation and the the evolving evolving opening OGC API standards Things like JSON and HTML are now first-class to make them again more webby So you remember the concept that we talked about more webby and lower barrier and all of that This is sort of here. We are I think this term actually means that both
23:24
Humans and machines can read the same thing and it's okay for both of them So here we have the landing page of our of our OGC API features instance and you can see various metadata that you would get from a present-day get capabilities response and
23:45
What I'll do is I'll I'll show you some examples here. So we're gonna drill down and see all the different Feature collections that are available in this OGC API features instance so we can see here are all the feature collections that are available
24:01
plus some you know title and abstract kind of metadata and Let's click on one at any point in time. Let me just back up at any point in time Obviously Angeles mentioned being able to be read by machine readable or humans This is here's the machine representation of what we see on the web page
24:20
So this is JSON as you all are probably aware Now let's list out all the collections and we can see a number of collections and let's look at large lakes So here's some sort of high-level information about that specific feature collection and Now we can start to browse the feature collection. So again, this is a this is a new WFS or OGC API features
24:45
So here we can see an HTML representation With a with a table with all the attributes and we can see the geometry all mapped out and hey We can even interact with the map at the same time so
25:01
I'll zoom in to Lake Ontario because I'm from close to there and I'm going home soon. So Here we are. So here we can see if we wanted to click and open that feature There's the actual feature and as you can see here, this is all this is all linked Or this provides the sort of identifier or the URI
25:22
So the other thing around the the specs is that they're designed to be Search engine friendly so you can do a Google data set search with an OGC API instance now because of the way they're designed and using things like schema org and so on so there's an example of What a specific feature looks like and again
25:43
You can get that back in JSON. So really low barrier really easy to You know implement either clients or or servers. I'll give you some examples at the initial WFS 3 hackathon We put pi geo API together and I think three days and I'll give you another example
26:01
In one of our in OWS live which is a Python OGC client implementing WFS 3 took 60% less code than implementing WFS 1 or 2 so Take heart. This is really low barrier and really easy to implement for web developers for GIS people
26:21
and we're really extending the reach here as you can see so I Guess to close that off. I think I would say As cliff cough caught men of OGC once said interoperability doesn't happen by accident so there's a lot of good work being done at OGC and the the the relationship between OGC and OS geo is
26:41
Natural healthy and evolving and I think this is an exciting time to be involved Thank you Thanks, Tom Angeles Angeles are there any questions? Yeah, and Just to remind you if you go down now, you have to queue up a very long time
27:05
So but better stay here and have some quick discussions Thank you. I have a comment and a question again first of all the comment congratulations for all the work being done both at OGC and With the community pi geo API can share a personal experience here
27:23
I deployed it following it on github and it took me roughly 10 minutes to deploy and to connect to my data structure and to have All my data available in this easy to use manner. So well done guys keep on doing that then the question relates a little bit to the slide that you Tom showed to where we had the
27:44
new way the new naming convention of the of the There the sensor things API I was just wondering because I think we have been using it at JRC a lot and we were really happy with it
28:01
It was I think the first one that is following closer the W3c way of doing things. I was wondering is there need to rework somehow the OGC Sensor things API And is it going to share this common way of handling things with the rest?
28:21
Exactly, this is this is how it will work initially WFS 3 started as as a draft by the community And then we realized that we need to have a commons specification for common things so actually the first WFS
28:44
Hackathon Worked on on WFS and the second one worked mainly on defining What are the common the common things that need to be in the standards? So right now the common specification is also being is now being drafted and
29:02
We already know that all there have been Working groups that are being formed for example me and Tom are in the catalog Group and catalog is not a thing right now because it's it hasn't been officially started
29:20
But we have been working on that. So I'm I'm sure that the SOS People are already thinking how to Get the common specification and add Their stuff on top of the common specification the same way We are now going to work on pi CSW for which is going to be the next version
29:43
Which is going to be based on the Commons and WFS work. So we are at the state where everything can change we we don't have final standards yet and We do have stable software to show even at these states, but of course it will get better and once one more thing
30:05
it is easier now for the developers, but For example, we don't have transactions yet in WFS and that will be an extension of the standard So typically in the past all GC standards had the whole package in the core today
30:24
The the core is going to be lightweight. So for example only HTML and JSON for WFS 3 But then if you want DML you can implement it. Nobody will stop you from doing that and For transactions you will be able to do an extension
30:41
So all the little nice things and features will come as extensions and they will be handled also as a part of the standard So we are trying to get more To get things in smaller pieces and it's a better ways to organize in order or also to help developers You know, it's difficult to implement 300 page
31:02
specification at once At least our experience of that Good other questions Do we really think that having a simple course back and then lots and lots of extensions that may or may not get implemented by
31:32
Anybody is the way to improve interoperability. I can just see a lot of people coming up and say why don't you support this? Why didn't you support that extension? What about the version 2 of that extension?
31:51
Yeah, I don't know. I guess there's a balance somewhere between core and extensions and Implementing a spec, you know a hundred percent The way the way it is now, I guess that part of that remains to range to be seen and
32:06
This is where the idea of information communities start to start to evolve So for example where I come from the met from the met community We will rally and build and sort of adhere to a specific set of extensions
32:22
Top WFS 3 or sorry OGC API features or or processes or coverages or whatever That's one approach
32:41
apologies if it was already said but based on your Experience from current process and let's say from the movement because I'm just feeling something big is coming Could you guess when this core of the core part of this OGC API will be
33:02
somehow formalized and stable Just also asking from the perspective of data provider who is at this moment about to initiate the big project to support Inspire legal requirements whilst hearing that there is coming new strong standard which may
33:23
Significantly impact the way how the data will be made available for the mainstream developer community, which From which we are hearing the request guys make this as their stuff easier and more usable So just I'm asking when do you think this OGC core will be stable then?
33:43
to be able to better communicate with dot say inspire legal people and to see What this how we will have to communicate to the stakeholders. Thanks a lot That that that's a good question
34:01
I I guess I I don't I don't know the answer to that question fully. I'm certainly not gonna say anything here, but There is some coordination that is to be done as I understand it between OGC and ISO with regards to making things an associated ISO standard so that ISO has as I understand it its own processes and
34:22
and and and its own timelines, so I'm not really aware of any formal dates. I've heard of WFS Coming out very soon in terms of the the initial the initial cut of the of the specification. The other ones are being Rapidly evolved and developed and you can see them all on github out in the open as well. So
34:46
Yes, but it is coming I mean one day you will open QGIS and you will be able to connect to a feature server a covered server. So this is This is the this is the trajectory that we're going on in terms of when obviously WFS 3 is the first out of the gate
35:03
And the other ones are being worked on. I don't know if anybody else from the team here has any further comments on timing No, no, I I don't know about the timeline, but that is a good point So we are you know, because that's all you and the communities looking into that
35:21
I took a note and that is probably a good topic also for a block for Scott Simmons But as Tom already mentioned so we have also very close coordination with ISO TC 2 1 1 and So, you know We are coordinating that with them, but I cannot I do not know the the timelines
35:49
Good So last chance for the last question of the session One two three nuns I will think I want to thank the my my co-presenters the the audience