Proposal for Modular Design/Organization

[charlesvardeman]

After looking through the design for W3C/OGC sosa and the geolink patterns, I think it might make sense to break the patterns up a bit. We would have a core part (sUAS-voc) like sosa that is modeled after a schema.org vocabulary and no logics and a (sUAS-ont or whatever we call it) that has the extended logics. I also am thinking that the core vocabulary would be general enough that any type of drone mission (non-scientific) would be able to use it. And then have a module that extends Payload into a scientific platform that would have the additional features needed for sensors and observations.

[Garybc]

I follow part of this.
Some Qs. Do we know that Schema.org has enough of the vocabulary?
Why not use, also, some vocabulary from IoT work as I suggested in an email? That would help with the payload and scientific platform.
Is there a trajectory pattern in this proposed approach?

[charlesvardeman]

So, the only parts of Schema.org we would probably use is schema:domainIncludes and schema:rangeIncludes which are annotation properties as domain and range . Everything else would be defined in our vocabulary with the logical formulation in a different "module". To see what I mean, look at sosa.ttl where sosa defines the vocabularies and ssn.ttl where the extended logics are defined.