Elaborate on Building Permit example

[anitagraser]

The building permit example in section 2.2.3 provides a good motivation / introduction to the challenge of preserving decisions based distributed GIS but the remainder of the Guidelines don't elaborate on how a good solution could look like.

@GregorZavrsnik Assuming this would be an IP without data (as explained in the GEO_11 Rationale), how should "the structure of data references in an application producing geospatial information products" look like?

[anitagraser]

For example, Spatial Data on the Web Best Practices W3C Group Draft Note 19 September 2023 recommends:

Best Practice 1: Use globally unique persistent HTTP URIs for Spatial Things - Use stable HTTP URIs to identify Spatial Things, re-using commonly used URIs where they exist and it is appropriate to do so.

[anitagraser]

https://www.inspire.gv.at/assistenzstelle/registry.html discusses persistent identifiers from Inspire registry perspective:

Persistenz Mit dieser Funktionalität soll eine Dauerhaftigkeit eines Zuganges von digitalen Objekten logisch (Versionierung) gewährleistet werden. Dieser Zugang erfolgt über Identifikatoren, die dann als PID (persistent identifier) gekennzeichnet werden. Uniform Resource Name (URN), Persistent Uniform Resource Locator (PURL) oder Digital Object Identifier (DOI) zeigen einen Ausschnitt an webbasierten PID’s.

--> Consider using the term PID (persistent identifier) in the guidelines

[anitagraser]

Steven P. Morris (2011) "Preservation of Geospatial Data: the Connection with Open Standards Development" In: M. Jobst (eds) Preservation in Digital Cartography. p.142.

Persistent identifier schemes support long-term access to data and
enable stable linkages between datasets, schemas, services, and
metadata. The OGC has already developed a URN (Uniform Resource
Name) namespace that is utilized for naming persistent resources
published by the OGC (Reed 2008), as well as Definition Identifiers to
be used within that namespace (Whiteside 2009), although there has
been some shift in sentiment towards favoring URIs (Uniform Resource
Identifiers) that are directly addressable over URNs which require
creation and maintenance of a name resolution service.

[anitagraser]

Identified challenges:

• GeoIP packages MUST contain geospatial data (GEO_1). Therefore this contradicts the idea of an IP that only references geospatial data in some other IP. -- This needs to be resolved.
• We should prepare a draft IP structure (similar to Figure 8 - Example of an Information Package folder structure) for an IP without geodata and discuss it with the DILCIS board since this issue will also appear in other (non-geo) domains.
• We should recommend a persistent identifier schema for use in the geospatial IPs, based on the latest conclusions in relevant communities, including OGC, Inspire, ..
• We want to look into how spatial databases handle versioning; and any applicable standards beyond ESRI's implementation -- so we can know how to refer to this versioned data from our IP.
• Concerning learning / transfer of know-how from other groups outside Europe: In the US (e.g. NARA) accept any format they can get (e.g. GeoPackage), they don't enforce specific file formats. We currently don't know how they handle IPs that only reference data in other IPs.