In the former case, this would mean that the different possible encodings of an instance of geosparql:Geometry (GML, WKT, GeoJSON, etc.) should always use the same CRS.
The BPs may need to be updated based on what will be the final approach adopted in GeoSPARQL 1.1.
One of the topics under discussion in current work on the new version of GeoSPARQL is whether class
geosparql:Geometryshould or not be bound to only one CRS - see https://github.com/opengeospatial/ogc-geosparql/issues/131In the former case, this would mean that the different possible encodings of an instance of
geosparql:Geometry(GML, WKT, GeoJSON, etc.) should always use the same CRS.The BPs may need to be updated based on what will be the final approach adopted in GeoSPARQL 1.1.