GeoSPARQL Standards Working Group Meeting Minutes

Meeting Details

Meeting Date: 10/01/2024

Meeting Time: 2000 UTC

Meeting Location: GoToMeeting

Attendees

Attendee	Moniker
Matthew Perry	MP
Timo Homburg	TH
Nicholas Car	NC

Note Takers

• JA

Action Items From Last Meetings

| Done? | Item | Responsible | Due Date | | —- | —- | —- | — |

Discussion Items

Time	Item	Who	Notes
2014	Intro	JA	Call for Patents None known Roll Call Attendees recorded in minutes Attendees confirmed vocally
2015	Run through actions	All	TH: Fix [#463](https://github.com/opengeospatial/ogc-geosparql/issues/463) TH: PR 470 ready for review NC: Thought he already fixed it [fixed] Merged PR [#470](https://github.com/opengeospatial/ogc-geosparql/issues/470) TH: Complete work on GeoSPARQL 1.1 Function URIs do not resolve in vocprez · Issue [#264](https://github.com/opengeospatial/NamingAuthority/issues/264) Unresolved issue with namespaces: Need one for parameters, Need one for outputs PR [#469](https://github.com/opengeospatial/ogc-geosparql/pull/469) TH: Will add a namespace for parameters and add a namespace for outputs PREFIX geofo: NC: a bit too much RDF if everything is a vocabulary (required for vocprez rendering). Good to define everything in the data but we don’t necessarily need to render everything. Tell Gobe to only render functions vocab - don’t worry about sub elements. NC: Respond to [#451](https://github.com/opengeospatial/ogc-geosparql/issues/451): Closed JA: Chat to NC about [#249](https://github.com/opengeospatial/ogc-geosparql/issues/249) NC: They should show us what JSON serialization they want so that we can evaluate it. They want a pure RDF serialization without a microformat for geometry NC to respond to the issue. Misc topics: NC: Continuous Integration is building static vocabs and OGC NA is also rendering them - we should let OGC NA render them instead of us. NC will create a diagram and OGC NA will render artifacts OGC NA wants confirmation that they have rendered all the things TH: would still be good to render development versions of vocabs. NC: Could have published 1.1 spec document but all the other assets are preventing the release. Much longer checklist for release now. NC: Issue [#430](https://github.com/opengeospatial/ogc-geosparql/issues/430): Consider qualified geometries Should GeoSPARQL introduce the properties for qualification? TH: issue was that the proposal was too general NC: thinks it’s not general enough
	Run through PRs	All	Run through PRs: [#466](https://github.com/opengeospatial/ogc-geosparql/pull/466) TH to fix small errors from review [#469](https://github.com/opengeospatial/ogc-geosparql/pull/469) TH to add outputs namespace Do we need to update SHACL? Waiting for Paul to take a look [#488](https://github.com/opengeospatial/ogc-geosparql/pull/488), [#489](https://github.com/opengeospatial/ogc-geosparql/pull/489), [#485](https://github.com/opengeospatial/ogc-geosparql/pull/485), [#487](https://github.com/opengeospatial/ogc-geosparql/pull/487): Example links wrong in ontology file (wrong annex), [#486](https://github.com/opengeospatial/ogc-geosparql/pull/486): Consistent capitalization
	Run through issues	All	[#494](https://github.com/opengeospatial/ogc-geosparql/issues/494) Should use wording suggestion in issue [#492](https://github.com/opengeospatial/ogc-geosparql/issues/492) Some typos [#490](https://github.com/opengeospatial/ogc-geosparql/issues/490) Need to make suggested corrections [#474](https://github.com/opengeospatial/ogc-geosparql/issues/474)NC: disagree that we should use turtle prefixes instead of SPARQL style.
2134			MEETING ENDS

Action Items

#	Item	Responsible	Due Date
1	Investigate reduced rendering of vocabs, etc. now that OGC-NA is doing it.	NC	Next Meeting
2	Respond to Issue #430 and write up ways to qualify a geometry, then we can see if proposed schemes cover them	NC	Next Meeting
3	Ask Scott about remaining items for publishing	NC	Next Meeting