Talk:SSN core moduls

This proposal makes a lot of sense from the perspective of making a vocabulary readily available, yet allowing more sophisticated usages.

Some comments:

1) use of # URIs is problematic with modularisation - as it forces every client to deal with the artefacts of modularity - to locate all the resources needed. Use of / URIs - especially for the core concepts, does not preclude bundling axioms in a single resource, but does allow content-negotiation and other server side processing. From the perspective of an end user, its extremely valuable to be able to have a view that provides the set of properties and axioms that relate to a FeatureType. Would need a naming convention or means of discovery of the vertical modules to specify what is to be included.

2) AFAICT this does not preclude using SKOS to describe instances of the classes defined, which then allows use in the rdf-qb coded properties.

3) It would be good to sketch out early the import proposed set of modules needed to get back to the original SSN scope, and highlight any changes

4) Moving forward each module should have description regarding the expressivity they introduce.