Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to parse actual GML as gmlLiteral due to xmlns #1299

Closed
SimonBin opened this issue May 12, 2022 · 1 comment · Fixed by #1325
Closed

Unable to parse actual GML as gmlLiteral due to xmlns #1299

SimonBin opened this issue May 12, 2022 · 1 comment · Fixed by #1325

Comments

@SimonBin
Copy link
Contributor

We are currently stumbling upon an issue with consuming GML exported from e.g. WFS

It cannot be used (directly) in Jena because the official GML standard uses a different xmlns than the one Jena searches for, even though the local names of the elements are the same.

I've also opened opengeospatial/ogc-geosparql#330 for clarification

@afs afs added the GeoSPARQL label May 12, 2022
@afs
Copy link
Member

afs commented May 12, 2022

The URL http://www.opengis.net/ont/gml -- NB ont -- redirects with a 302 to http://schemas.opengis.net/gml/3.2.1/gml_32_geometries.rdf which is the RDF definitions.

The standards URL http://www.opengis.net/gml/3.2 redirects to a bunch of XSD references http://schemas.opengis.net/gml/3.2.1/gml.xsd.

So maybe it is intended that the meaning (ontology) is "http://www.opengis.net/ont/gml" but the XSD (syntax) is not ... though data syntax is impacted across minor versions. This seems to be a bit of a "no win" situation for datatypes.

@afs afs closed this as completed in #1325 Jul 26, 2022
afs added a commit that referenced this issue Jul 26, 2022
GH-1299: update GML XML namespace ont/gml => gml/3.2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants