Remove sosa:Host retain sosa:Platform

[dr-shorthair]

Added note to explain that sosa:Platform is the SOSA implementation of OMS Host.

Closes #56

[rob-metalinkage]

I think this reflects the discussion and moves us forward to a review step.

[rob-metalinkage]

I did ask to see if @alexrobin could be added to the repository and review candidates.

[sgrellet]

on ssn/integrated/sosa.ttl

line 202 "An environmental monitoring facility.". I wonder if that would make sense to refer to EU INSPIRE directive (2007/2/EC) theme 'Environmental Monitoring Facilities' (INSPIRE:EF) or create more confusion.
Indeed, the OMS:Host is modelled having in mind the work we did on INSPIRE:EF with @kathi (and we should convince JRC to update that dataspecs)

line 338 sosa:Observer a rdfs:Class , owl:Class ;
will we discuss the sosa:Sensor VS OMS:Observer in another issue and PR ?

[alexrobin]

Thanks Simon. Looks good to me

[dr-shorthair]

@sgrellet asked

line 338 sosa:Observer a rdfs:Class , owl:Class ;
will we discuss the sosa:Sensor VS OMS:Observer in another issue and PR ?

See #100

[dr-shorthair]

@sgrellet asked

line 202 "An environmental monitoring facility.". I wonder if that would make sense to refer to EU INSPIRE directive (2007/2/EC) theme 'Environmental Monitoring Facilities' (INSPIRE:EF) or create more confusion.

If sosa:Platform is functionally equivalent to EMF then that could be mentioned in the documentation or annotation. Perhaps this could be added as a dcterms:source reference?

For the time being I have added a skos:scopeNote.

Also see #57 for some ideas about how to document alignment to OMS.

[sgrellet]

If sosa:Platform is functionally equivalent to EMF then that could be mentioned in the documentation or annotation. Perhaps this could be added as a dcterms:source reference?

I'll add this as a dcterms:source. This will help using SOSA while maintaining compliancy with EU specs