Geocoding Vocabulary

[situx]

Closes #444

This pull request collects URIs and classes for Geocoding Systems which should be registered at the OGC Naming Authority.

The URIs defined in this vocabulary should eventually after review by OGC be used in GeoCode Literals.

[nicholascar]

Can this vocabulary be:

• proposed not as a class hierarchy but a SKOS ConceptScheme
  • like other GeoSPARQL support vocabs with appropriate metadata
  • with Concepts dual classed as rdfs:Datatype objects also
  • using GeoCode as the parent with others all skos:narrower
• in longturtle RDF format
  • for better Git tracking
  • to remove Protege cruft
  • use https://tools.dev.kurrawong.ai/convert
• use schema:citation instead of rdfs:isDefinedBy as the targets are non-RDF nodes
• provide at least a single-line description for each one
• using Register Ontology Status Codes for the ConceptScheme and each Concept
  • so they are ready for management of additions, deprecations etc. Link here: https://linked.data.gov.au/def/reg-statuses. Examples of use at the ConceptScheme level here: https://vocabulary.gswa.kurrawong.ai/v/vocab. All things can be marked as stable.

I'm listing all these points to see if you all agree to them but I'm not suggesting you (@situx) have to do them all yourself! You've already done the main work here, so I'm happy to do many of these, if you agree to them

[situx]

Hi Nick,

I agree with all of your points. I only have a question concerning the SKOS decision:

• What would be the benefit in defining it as as SKOS concept hierarchy? The ability to define it also as rdf:Datatype? Or does it integrate better with OGC Rainbow? I am asking since we also did not define the Simple Features vocab as SKOS and we would also not define the CRS ontology as such.

[VladimirAlexiev]

Don't use "slash and hash" in the URL. Use only slash (better than hash because this is a big collection of resources)

[VladimirAlexiev]

if it has no members that are skos:Concept and point to it using skos:inScheme,
then it's not a ConceptScheme