BEGIN:VCALENDAR VERSION:2.0 PRODID:-//pretalx//talks.osgeo.org//foss4g-2023//UF7J7G BEGIN:VTIMEZONE TZID:CET BEGIN:STANDARD DTSTART:20001029T040000 RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10 TZNAME:CET TZOFFSETFROM:+0200 TZOFFSETTO:+0100 END:STANDARD BEGIN:DAYLIGHT DTSTART:20000326T030000 RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3 TZNAME:CEST TZOFFSETFROM:+0100 TZOFFSETTO:+0200 END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT UID:pretalx-foss4g-2023-ZGYKXH@talks.osgeo.org DTSTART;TZID=CET:20230628T113000 DTEND;TZID=CET:20230628T120000 DESCRIPTION:The Ontology discipline made its way into the Computer Science domain in the\n1990s\, filling a gap in the architecture aspect of a still infant engineering\ndomain. Its most visible impact happened around the i ndustry consortium Object\nManagement Group (OMG)\, leading first to the U nified Modelling Language (UML)\nand later to the Model Driven Architectur e (MDA). MDA became the base\ninfrastructure of data architectures and exc hange mechanisms specified by\ninstitutions such as the Open Geo-spatial C onsortium (OGC) or the European\nCommission (through the INPIRE directive) .\n\nHowever\, a parallel path has been treaded by the World Wide Web Cons ortium\n(W3C). First with the specification of the Resource Description Fr amework (RDF)\,\na new paradigm for data encoding leveraged on the WWW\, a nd later with the Web\nOntology Language (OWL)\, a pragmatic approach to o ntology encoding\, building on\nRDF. This infrastructure developed by the W3C became known as the Semantic Web\,\nand also as Linked Data\, for the innovative paradigm through which it connects\ndisparate data sources and data domains.\n\nThe OGC would eventually approach the semantic web\, spec ifying GeoSPARQL in\n2013\, an ontology and query language for linked geo- spatial data. However\,\ntechnologies supporting this new standard were sl ow in materialising.\n\nMore recently\, the specification by the OGC of a new set of data standards based\non the OpenAPI technology set out a clear path for the convergence of\ngeo-spatial data with the Semantic Web. New software is emerging\, opening\nan entirely new world to geo-spatial data provision\, a clear step forwards in\npractically\, usability and semantic s.\n\nThis address starts by reviewing the core concepts of the Semantic W eb and\nthen reviews state-of-the-art software for the management\, public ation\nand exploration of linked geo-spatial data. This addressed is targe ted at SDI\nprofessionals and data scientists wishing to upgrade the seman tics of the data\nthey create and use. DTSTAMP:20260423T001524Z LOCATION:UBT D / N112 - Second Floor SUMMARY:Geo-Spatial meets Linked Data: open source solutions for semantic s patial data exchange - Luís M. de Sousa URL:https://talks.osgeo.org/foss4g-2023/talk/ZGYKXH/ END:VEVENT BEGIN:VEVENT UID:pretalx-foss4g-2023-D38YER@talks.osgeo.org DTSTART;TZID=CET:20230628T150000 DTEND;TZID=CET:20230628T153000 DESCRIPTION:Motivation: \nSpatial Data Infrastructures (SDI) developed for the exchange of environmental\nhas heretofore been greatly shaped by the s tandards issued by the Open\nGeospatial Consortium (OGC). Based on the Sim ple Object Access Protocol (SOAP)\,\nservices like WMS\, WFS\, WCS\, CSW b ecame digital staples for researchers and\nadministrative bodies alike. \n \nIn 2017 the Spatial Data on the Web Working Group (SDWWG) questioned the overall\napproach of the OGC\, based on the ageing SOAP technology\n[@SDW WG2017]. The main issues identified by the SDWWG can be summarised as:\n\n - Spatial resources are not identified with URIs.\n- Modern API frameworks \, e.g. OpenAPI\, are not being used.\n- Spatial data are still shared in silos\, without links to other resources.\n- Content indexing by search en gines is not facilitated.\n- Catalogue services only provide access to met adata\, not the data.\n- Data difficult to understand by non-domain-expert s.\n\nTo address these issues the SDWWG proposed a five point strategy ins pired on the\nFive Star Scheme [@BernersLee2006]:\n\n- **Linkable**: use s table and discoverable global identifiers.\n- **Parseable**: use standardi sed data meta-models such as CSV\, XML\, RDF\, or JSON.\n- **Understandabl e**: use well-known\, well-documented\, vocabularies/schemas.\n- **Linked* *: link to other resources whenever possible.\n- **Usable**: label data re sources with a licence.\n\nThe work of the SDWWG triggered a transformatio nal shift at the OGC towards\nspecifications based on the OpenAPI. But whi le convenience of use has been the\nfocus\, semantics has been largely unh eeded. A Linked Data agenda has not\nbeen pursued.\n\nHowever\, the OpenAP I opens the door to an informal coupling of OGC services with\nthe Semanti c Web\, considering the possibility of adopting JSON-LD as\nsyntax to OGC API responses. The introduction of a semantic layer to digital\nenvironmen tal data shared through state-of-the-art OGC APIs is becoming a\nreality\, with great benefits to researchers using or sharing data.\n\nThis communi cation lays down a simple SDI set up to serve semantic environmental\ndata through a SensorThings API created with the `glrc` software. A use case is\npresented with soil data services compliant with the GloSIS web ontolo gy.\n\nSensorThings API:\n\nSensorThings API is an OGC standard specifying a unified framework to\ninterconnect Internet of Things resources over th e Web [@liang2016ogc].\nSensorThings API aims to address both the semantic \, as well as syntactic\,\ninteroperability. It follows ReST principles [@ fielding2002principled]\,\npromotes data encoding with JSON\, the OASIS OD ata protocol\n[@chappell2011introducing] and URL conventions. \n\nThe Sens orThings API is underpinned on a domain model aligned with the ISO/OGC\nst andard Observations & Measurements (O&M) [@Cox2011]\, targeted at the\nint erchange of observation data of natural phenomena. O&M puts forth the\ncon cept of `Observation` has an action performed on a `Feature of Interest`\n with the goal of measuring a certain `Property` through a specific `Proced ure`.\nSensorThings API mirrors these concepts with `Observation`\, `Thing `\,\n`ObservedProperty` and `Sensor`. This character makes of SensorThings API a\nvehicle for the interoperability of heterogeneous sources of envir onmental\ndata.\n\n\n`glrc`:\n\n`grlc` (pronounced "garlic") is a lightwei ght server that translates SPARQL\nqueries into Linked Data web APIs [@mer ono2016grlc] compliant with the OpenAPI\nspecification. Its purpose is to enable universal access to Linked\nData sources through modern web-based m echanisms\, dispensing the use of the\nSPARQL query language. While losing the flexibility and federative capacities\nof SPARQL\, web APIs present d evelopers with an approachable interface that can\nbe used for the automat ic generation of source code.\n\n\nA `glrc` API is constructed from a SPAR QL query to which a meta-data section is\nprepended. This section is decla red with a simplified YAML syntax\, within a\nSPARQL comment block\, so th e query remains valid SPARQL. The meta-data provide\nbasic information for the API set up and most importantly\, the SPARQL end-point\non which to a pply the query. The listing shows an example. \n\n```\n#+ endpoint: http:/ /dbpedia.org/sparql\n\nPREFIX dbo: \nPREFIX dbr: \nPREFIX rdfs: \nPREFIX rdf: \n\nSELECT ?band_label { \n ?band rdf:type dbo:Band \;\n dbo:g enre dbr:Hard_Rock \;\n rdfs:label ?band_label .\n} ORDER BY ?ban d_label\n```\n\nA special SPARQL variable formulation is used to map into API parameters. By\nadding an underscore (`_`) between the question mark a nd the variable name\,\n`glrc` is instructed to create a new API parameter . A prefix separated again\nwith an underscore informs `glrc` of the param eter type. The `?band_label`\nvariable in [Listing @lst:1] can be expanded to `?_band_label_iri` to create a\nnew API parameter of the type IRI.\n\n \nUse case: GloSIS: \n\nThe Global Soil Partnership (GSP) is a network of stakeholders in the soil\ndomain established by members of the United Nati ons Food and Agriculture\nOrganisation (FAO). Its broad goals are to raise awareness to the importance of\nsoils and to promote good practices in la nd management towards a sustainable\nagriculture. \n\nAcknowledging diffic ulties in exchanging harmonised soil data as an important\nobstacle to its goals\, the GSP launched in 2019 an international consultancy to\nassess the state-of-the-art and propose a path towards a Global Soil Information\ nSystem (GloSIS) based on a unified exchange. A domain model resulted\, ba sed\non the ISO 28258 standard for soil quality [@SchleidtReznik2020]\, au gmented with\ncode-lists compiled from the FAO Guidelines for Soil Descrip tion [@Jahn2006].\nThis domain model was then transformed to a Web Ontolog y\, relying on the Sensor\,\nObservation\, Sample\, and Actuator ontology (SOSA) [@Janowicz2019]\, and other\nSemantic Web standards such as GeoSPAR QL\, QUTD and SKOS. The GloSIS web ontology\nhas been successfully demonst rated as a vehicle to exchange soil information as\nLinked Data [@GloSIS]. \n\nA prototype API for the GloSIS ontology\, formulated in compliance wi th the\nSensorThings API specification\, will be presented in this communi cation. It\ndemonstrates how the same set of SPARQL queries can be used to query through a\nReST API any end-point available over the internet\, sha ring linked soil data in\naccordance with the GloSIS ontology. Thus provid ing a clear step towards the\nfederated and harmonised system envisioned b y the GSP. DTSTAMP:20260423T001524Z LOCATION:UBT C / N109 - Second Floor SUMMARY:The template for a Semantic SensorThings API with the GloSIS use ca se - Luís M. de Sousa URL:https://talks.osgeo.org/foss4g-2023/talk/D38YER/ END:VEVENT END:VCALENDAR