Intoduce WGS-84 DefinedNamespace

[kvjrhall]

WGS84 (html, rdf) is a small vocabulary that is commonly used in documents from dbpedia, geonames, and others. The vocabulary hasn't changed since 2006, suggesting that ongoing maintenance effort for the namespace should be minimal.

[kvjrhall]

There do seem to be some gotchas here. Example seen so far:

1. dbpedia and others will commonly use geo prefix for this vocabulary, which we currently use for GeoSPARQL. I'll use wgs84 as the prefix for this vocab.
2. dbpedia uses a term geometry from this namespace that is not part of the specification. I've included it in the vocabulary class and documented the non standard nature of it as well as why it's there.

[nicholascar]

Fee free to contribute a DefinedNamespace of the WGS-84 content if you like. You can add it to the files in https://github.com/RDFLib/rdflib/tree/master/rdflib/namespace.

There is no RDF prefix given within a DefinedNamespace class, so it doesn't matter what people use when you create that. Also, we are about to remove the larger set of prefixes bound to graphs here, https://github.com/RDFLib/rdflib/blob/master/rdflib/namespace/__init__.py#L350-L376, since this is problematic for some users.

Also, note that on prefic.cc the prefix pos is registered for WGS-84 and that's what's used in the WGS-84-> GeoSPARQL 1.1 mapping available https://opengeospatial.github.io/ogc-geosparql/geosparql11/spec.html#_e_2_wgs84_geo_positioning_an_rdf_vocabulary_pos.

So you don't really have to worry much about geo v. wgs84 v. pos in RDFLib itself as you don't have to declare it for a new DefinedNamespace but I'd recommend going with pos when you want to use a prefix generally since, in the future, we may better link up RDFLib with prefix.cc.

[kvjrhall]

Thank you for carrying this across the finish line for me. I got pulled into other pressing issues and revisiting the PR slipped my mind.

…

On Mon, Feb 21, 2022, 5:19 AM Nicholas Car ***@***.***> wrote: Closed #1709 <#1709> via #1710 <#1710>. — Reply to this email directly, view it on GitHub <#1709 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APDOKNOWIKXEDSYOJLBCZXDU4IGS5ANCNFSM5N5RNNDQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>